The fwdcentaur mark: a blue centaur striding to the right, a white arrow pointing forward on its flank

fwdcentaur

A shared, fine-grained graph of the work, the code it touches, and the messages between the people and coding agents doing it. A daemon on your own machine keeps it; agents use it through the fwd command, and people through the same command, a page in the browser, or a VS Code extension.

What it is for

People and coding agents lose the thread between them. The reasons for a task evaporate between planning and implementation, and again when an agent's context is compacted. A comment on a line of code has nowhere durable to live except a pull-request comment, which goes stale on the next push. And no one can see which person or agent is working on what, with what intention.

fwdcentaur keeps that thread in one graph per project: what is to be done and why, the comments people leave on particular lines of code, and the questions and answers that pass between people and agents. It routes each comment and question to the person or agent it concerns, while they are still at work, and to no one else. The graph is also each agent's memory across compaction: an agent reads it again rather than reconstructing the work from its transcript.

What it does

The Tasks page for the scope Agent identity and roles: seven tasks, each with its status, readiness, priority, scope, assignee and when it was last updated. Three are in progress, held by the implementer agents impl-dormant and impl-identity-refusals; four are open and ready.
The page's Tasks list for one scope, Agent identity and roles, of the graph that fwdcentaur's own development runs in: three tasks are in progress, each held by an implementer agent under a name of its own, and four are open and ready to start.

What the graph holds

What the graph holds Entity diagram. A task, with what is to be done, why and when it is done, its status, assignee and labels, is at the centre: it depends on, is a subtask of or was discovered from other tasks, is worked in a scope, and cites decisions. A highlight, lines of a file that follow the code as it changes, is a step of a task. A message is about a task or on a highlight, and replies to other messages in a thread. Principals, people and agents with a role, are a task's assignee, make everything, and each has an inbox. depends on · subtask of · discovered from worked in cites step of about on replies to Scope intention · branches status Task what · why · done when status · assignee · labels Decision D12 · ruling · why status Highlight file · lines text as seen follows the code Message text · author asks whom, if anyone resolved Principal a person, or an agent with a user of its own and a role: lead, triage, implementer or reviewer a task has at most one assignee; everything records who made it; each has an inbox What the graph holds Entity diagram. A task, with what is to be done, why and when it is done, its status, assignee and labels, is at the centre: it depends on, is a subtask of or was discovered from other tasks, is worked in a scope, and cites decisions. A highlight, lines of a file that follow the code as it changes, is a step of a task. A message is about a task or on a highlight, and replies to other messages in a thread. Principals, people and agents with a role, are a task's assignee, make everything, and each has an inbox. depends on · subtask of · discovered from worked in cites step of about on replies to Task what · why · done when status · assignee · labels Scope intention branches status Decision D12 · ruling why · status Highlight file · lines text as seen follows the code Message text · author asks whom, if anyone resolved Principal a person, or an agent with a user of its own and a role: lead, triage, implementer or reviewer a task has at most one assignee everything records who made it; each has an inbox
A task at the centre of the graph: the scope it is worked in, the other tasks it depends on, is part of or came from, the decisions it cites, the highlights that are its steps and the messages about it. A principal, a person or an agent, made each of them.
Tasks
What is to be done, why, and when it counts as done, with the dependencies between tasks, their subtasks, and the task or message each one came from. A task has at most one assignee, the person or agent doing it, and labels such as bug or feature. It is filed open, or proposed when whoever files it is unsure it should exist.
Scopes
Areas of work: what the work in one is trying to achieve, the branches it happens on, and the tasks worked in it. Anyone works in any scope, and several people and agents may share one; a scope has no owner.
Messages
Everything a person or an agent says: a comment on a task or on lines of code, a question, a reply. Each is durable and threaded, and is resolved when it is settled. Anything a message names in its text is a mention: a person or an agent (@name), who hears of it, or a task, a decision, a scope, lines of code, or a whole file as it stands on disk, as staged, or at a commit.
Highlights and reviews
A highlight is lines someone is still talking about: a range of a file, anchored so that it survives the code changing, with a thread that is not resolved. A review is a task whose checklist is the highlights to read, each checked off beside its code.
Decisions
Rulings, numbered (D12) so that people and agents cite them. When one is repealed or replaced, the author of everything that cites it is told, with the reason.
Inboxes
One for each person and each agent. A notification is made only when a particular party needs to know, and it says in a sentence why it is there: impl-alice asked the project about Retry on disconnect.

How it runs

One binary, fwd, is both the command and the daemon: the first command that needs the daemon starts it, and one daemon for each user of the machine hosts every project, each in a database of its own. The daemon holds each project's graph as a durable node of Ankurah, a local-first, event-sourced database; the command, the page and the VS Code extension are nodes too, which read the graph live from the daemon and write to it with the same rules.

A project is known by its repository's upstream, the origin remote, never by a directory, so every clone and worktree of the repository belongs to the same project, and a project can span several repositories. The graph lives on your machine, in the daemon's data directory, and fwd hosts nothing elsewhere; your agents read it as they read your code, so what they read goes wherever their context goes.

Agents use the command and nothing else, so any agent harness with a shell can work in the graph, each command naming the agent it acts as. In Claude Code the fwd plugin does that naming: it stamps each command with the agent that ran it, and it brings the skills for the lead, the triage agent and implementers.

Who works in it

Every agent working in a project has a user of its own there, a principal it names itself, and selects one of four roles. A lead is a session that coordinates the project's work with you: it plans the work, hands it to implementers and looks at what they hand back, and there is one for each session or worktree that does so. A triage agent answers first for the scopes it serves, so that the leads and implementers working there are not distracted by first-line traffic: the questions asked of no one in particular about their work, the comments on their tasks and code, proposals and reviews reach it. A scope has one, which the lead coordinating its work starts; in a small project with small scopes, one may serve the whole project instead, taking what no scope's own triage agent takes. Implementers work tasks in scopes, and reviewers review what they are asked to, as many of each as the work needs. You hold no role: you are the project's person, and what is asked of you reaches you.

A message reaches whom it is addressed to

The daemon routes each message as it is written, by what it is about and whom it asks:

A comment on code reaches the people of the task near it dnorman comments on lines 120 to 134 of src/net/ws.rs. The task Retry on disconnect is anchored at lines 104 to 116 of the same file, within 50 lines, so its assignee, impl-alice, is told: dnorman commented on src/net/ws.rs:120-134, near Retry on disconnect, which is assigned to you. The triage agent of the task's scope, triage-retries, is told: dnorman commented on src/net/ws.rs:120-134. No one else is told. assignee triage src/net/ws.rs 104 116 120 134 Retry on disconnect dnorman's comment The task is anchored at lines 104–116, within 50 lines of the comment. impl-alice implementer dnorman commented on src/net/ws.rs:120-134, near Retry on disconnect, which is assigned to you triage-retries triage dnorman commented on src/net/ws.rs:120-134 No one else is told: not dnorman, who wrote it, nor any other person or agent. A comment on code reaches the people of the task near it dnorman comments on lines 120 to 134 of src/net/ws.rs. The task Retry on disconnect is anchored at lines 104 to 116 of the same file, within 50 lines, so its assignee, impl-alice, is told: dnorman commented on src/net/ws.rs:120-134, near Retry on disconnect, which is assigned to you. The triage agent of the task's scope, triage-retries, is told: dnorman commented on src/net/ws.rs:120-134. No one else is told. assignee triage src/net/ws.rs 104 116 120 134 Retry on disconnect dnorman's comment The task is anchored at lines 104–116, within 50 lines of the comment. impl-alice implementer dnorman commented on src/net/ws.rs:120-134, near Retry on disconnect, which is assigned to you triage-retries triage dnorman commented on src/net/ws.rs:120-134 No one else is told: not dnorman, who wrote it, nor any other person or agent.
A comment on lines of code reaches the assignee of a task anchored near them and the triage agent of that task's scope, and no one else.

Agents in Claude Code get their notifications between their steps, through hooks or fwd inbox pop; people read theirs on the page, in the extension's inbox view, or with fwd inbox. What an agent did about a notification is a reply in the thread it came from, where everyone who opens the thread reads it.

Where to go next