Taskr
Start a workspace

Docs

Docs that keep up with the tickets.

Each project gets a document base. When a ticket closes, Taskr reads the ticket, the agent's notes and the merged diff, and proposes changes for a lead to accept, edit or reject. Agents read the docs over MCP.

Start a workspace

The pictures in this section show three windows: issue TSK-148 in the Taskr web app, Priya's Billing docs in the web app, and Tom's terminal running Codex. Pull request #212 merges and TSK-148 moves to Done. Taskr Docs reads the ticket, its comments, the agent's notes and the diff, and proposes changes to two pages. Priya accepts one change and edits the other; a block Sam edited yesterday is left as he wrote it. Then Tom's agent starts a related ticket and its start_work result points to the updated Webhooks page.

Docs

The ticket closes. The docs catch up.

Taskr Docs proposes the doc changes a closed ticket implies. A lead reviews them.

01 Closes

A ticket closes.

#212 merges and TSK-148, Double charge on webhook retry, moves to Done. Closing a ticket starts a docs run for its project.

02 Reads

It reads the diff and the notes, not whole files.

Taskr Docs reads the ticket and its comments, the progress notes and finish summary from Maya's agent, and the diff of #212.

03 Proposes

A change request, not a silent edit.

Taskr Docs never changes a page itself. It opens a doc change request with a diff per page: Webhooks updated, and a new step in the double-charge runbook.

04 Review

The lead decides, hunk by hunk.

Priya accepts one change and edits the other. Sam edited the Testing section yesterday, so that block stays as Sam wrote it. Human edits win.

05 Next session

The next agent starts from the new page.

Tom's Codex agent picks up TSK-157. Its start_work result lists the Webhooks page Priya just accepted.

Docs feed the next ticket.

Tom's agent reads the page with get_doc and reuses processed events instead of writing a second check.

Spaces

A space per project, seeded by a template.

Each project gets a document base, called a space, and the workspace gets one more. A space has a page tree, an editor, history and search. Pages are Markdown, and people and agents write in the same ones.

Pick a template for the kind of project: web app, API or service, infrastructure, mobile, library or SDK, or blank. It seeds the page tree and the writing rules Taskr Docs follows on each page.

Proposals

Proposals, never silent edits.

Taskr Docs opens a change request and never edits a page itself. A project or team lead accepts, edits or rejects each change, down to each hunk.

Human edits win. A block-level three-way merge leaves alone any block a person changed since Taskr Docs read the page.

Everything sent to the model is fenced as data, and the model gets no tools. Routing is zero-data-retention, with an EU region option.

Delivery

Daily, or one per ticket.

Each space sets its own delivery. By default the day's closed tickets collect into one change request, so a busy team reviews once a day. A small team can get one per ticket as each closes.

Proposed doc updates are on the Team plan. Spaces, pages and search are on every plan.

Agents

Agents read the docs before they edit.

Any agent connected over MCP can search and read pages with search_docs and get_doc. When it claims a ticket, the relevant pages arrive in its start_work result and its session brief.

Page text reaches the agent fenced as data, the same way issue text does.

Put your agents on real tickets.

For the whole engineering team, and every agent that speaks MCP. We build Taskr for teams like ours.

Start a workspace Sign in