EllipticElliptic
2.1Projects & tasks

Linear-style tasks your agents and your team run on one board, in real time.

Projects, tasks, sub-tasks, and the planning layers above them. Every task carries a stable identifier, so a meeting, a comment, or an agent can point straight at it.

Start freeRead the docs
app.elliptic.com/q3-platform
Q3 PlatformQ3Active
BoardList
Filter
Backlog3
Q3-58

Draft the Q3 platform launch announcement

content
Q3-61

Audit onboarding email cadence

growth
2
Q3-64

Spike: realtime presence on the board

In Progress3
Q3-42

Wire transcript import from Folio

meetingsbackend
Jun 143/54
Q3-47

BYOK key rotation flow

security
Jun 161/4
Q3-50

Activity feed pagination

1
In Review2
Q3-39

AI meeting summary prompt v2

ai
6
Q3-44

Roles and permissions matrix

platform
5/5
Done3
Q3-31

Project key generator

2
Q3-35

Notes autosave and history

notes
Q3-28

Board column drag reorder

DEMO-42Stable task identifiers
3List, Board, and Table views
0Global endpoints, every row org-scoped
2.2How it works

One board your agents can run. Stable identity, real views, and a query language underneath.

Here is what each part looks like in practice.

2.2.1The board

Backlog to done, moving as fast as the agents and the team behind it.

Drag tasks across statuses on a Kanban board, or switch to a dense List or a spreadsheet-style Table over the same data. Set priority and assignees, group by label, and every change lands for everyone the moment it happens.

  • List, Board, and Table views over one model
  • Statuses from backlog to in-progress, in-review, and done
  • Sub-tasks, labels, priorities, and assignees in sync
app.elliptic.com/q3-platform
Q3 PlatformQ3Active
BoardList
Filter
Backlog3
Q3-58

Draft the Q3 platform launch announcement

content
Q3-61

Audit onboarding email cadence

growth
2
Q3-64

Spike: realtime presence on the board

In Progress3
Q3-42

Wire transcript import from Folio

meetingsbackend
Jun 143/54
Q3-47

BYOK key rotation flow

security
Jun 161/4
Q3-50

Activity feed pagination

1
In Review2
Q3-39

AI meeting summary prompt v2

ai
6
Q3-44

Roles and permissions matrix

platform
5/5
Done3
Q3-31

Project key generator

2
Q3-35

Notes autosave and history

notes
Q3-28

Board column drag reorder

FIG 2.1
2.2.2Stable identity

Every task has a name everything points at. DEMO-42 today, DEMO-42 forever.

Each project owns a key, and every task gets the next number from a per-organization counter, claimed under a row lock so two tasks can never collide. A meeting, a comment, a webhook, or an agent can reference DEMO-42 and always resolve the same work.

  • Stable, human-readable identifiers per project
  • Allocated with SELECT FOR UPDATE, so numbers never clash
  • Referenced from meetings, comments, and agents alike
task.json
{
  "identifier": "DEMO-42",
  "title":      "Ship the 1.0 rewrite",
  "status":     "in_progress",
  "priority":   "high",
  "assignee":   "ada@acme.com",
  "labels":     ["launch", "p0"],
  "estimate":   "5"
}

// the number is claimed atomically, per org:
//   SELECT last_number FROM project_counters
//     WHERE project_id = $1 FOR UPDATE;
FIG 2.2
2.3Capabilities

Everything a tracker needs, and nothing an agent has to be told twice.

Three views, one model

List, Board (Kanban), and Table render the same tasks. Switch without losing your place.

Sub-tasks and dependencies

Break work down, roll progress up, and block a task on the ones it waits for.

Labels and priorities

Tag work with colored labels and order by priority, both filterable in PQL.

Workflow statuses

Define statuses per team across categories from backlog to done, and gate which transitions are allowed.

Epics and relations

Group work under an epic, and relate items that block, duplicate, or depend on each other.

Saved views and custom fields

Save a slice of the board for yourself, your team, or the org, and add the fields you track.

2.4For agents

Agents operate the board over MCP. The same tasks, the same statuses, scoped to one org.

An agent connects once over OAuth and gets the whole task surface as callable tools. It creates work, moves it, and closes it out, and your team sees every change live.

company-brain MCP
# an agent creates and moves real work
create_task(project="DEMO", title="Ship the 1.0 rewrite",
            priority="high", labels=["launch"])
# -> { "identifier": "DEMO-42", "status": "backlog" }

transition_task_status(task="DEMO-42", status="in_progress")
add_comment(task="DEMO-42", body="Tag pushed, CI is green.")
transition_task_status(task="DEMO-42", status="done")

Built for the way your agents and team work. Available today.

Start freeTalk to us