Free
$0
- Issues, projects, cycles and the board
- Agents over MCP and the Claude Code plugin
- Live presence and overlap warnings
- GitHub branches, pull requests and checks
- A document base for each project
The pictures in this section are four simulated devices: Maya's laptop running Claude Code, Tom's monitor with the Taskr web app, Sam's tablet with the board and Priya's phone with Taskr in its browser. They all show issue TSK-148.
Taskr, the issue tracker for people and their agents
One team, every agent, every screen.
The unit of collaboration is a person plus their Claude Code agents. When an agent claims a ticket, runs into someone else's files or merges, every open screen shows it in about 55 ms.
Presence
Who is on what, right now.
Every open session shows its person, its agent, the issue, the branch and the files it has touched. Paths only, never contents.
Maya's laptop
It starts with one sentence.
Maya asks Claude Code to fix the double charge when Stripe retries a webhook. Nothing is claimed yet, and nobody else knows.
01 Claim
The agent claims the ticket.
The Taskr plugin finds TSK-148 and calls start_work: assigned to Maya via Claude Code, on its own branch.
55ms
One change. Every screen.
TSK-148 moves to In progress on Tom's monitor, Sam's tablet and Priya's phone in the same beat. The median from an agent's write to every open browser is about 55 ms.
02 Brief
Every session starts briefed.
About 600 tokens: the ticket, its acceptance criteria and who else is working where.
03 Overlap
Claims warn. They never block.
Tom's agent edited src/billing/sender.ts 4 minutes ago for TSK-139. Both agents are told, and Maya's keeps its change inside handleRetry().
The same warning, on every screen.
Anyone looking at TSK-148 sees who else is in src/billing/sender.ts.
04 Progress
The plan ticks in Priya's hand.
The agent's todo list is mirrored onto the issue as it works. Priya follows along in her phone's browser; nobody has to ask how it is going.
05 Merge
Merged. Done on every screen.
Pull request #212 links to the issue with its checks. Merging it moves TSK-148 to Done everywhere at once, on the record as Maya via Claude Code.
Connect
One command on every laptop.
$
claude mcp add --transport http taskr https://mcp.taskr.bbdev.app/mcp
> /mcp
taskr: sign in to connect
Add the server, then run /mcp in Claude Code and sign in. The Taskr
plugin briefs each session in about 600 tokens, opens tickets for untracked work
("Tracking this as TSK-148") and mirrors the agent's todo list onto the issue.
Issue and pull request text reaches agents delimited as untrusted data, never as instructions.
Fourteen toolsover a remote MCP server
- search_issues
- Find issues, or rank Todo for the next one
- get_issue
- An issue with its branches, PRs and checks
- create_issue
- Open a ticket for untracked work
- update_issue
- Change status, assignee, priority, fields
- comment
- Reply on an issue
- start_work
- Claim and move to In progress
- report_progress
- What the agent is doing now
- finish_work
- Done, handoff or blocked, with a summary
- whats_happening
- Who is working on what, right now
- check_overlap
- Is anyone else in these files?
- my_context
- Replies waiting for this session
- workspace_info
- Projects, workflow states, labels, people
- link_git
- Attach a branch or pull request
- pr_feedback
- Review comments and failing checks
For the people: keyboard first. ⌘K goes anywhere, C creates an issue, and the whole app works in your phone's browser.
The pictures in this section show three windows: Tom's Taskr web app, the sandbox where Taskr Worker runs, and Maya's terminal. Tom assigns TSK-152, Refund partial captures, to Taskr Worker; the worker starts in the sandbox and its progress shows on the issue; then Maya takes it over with claude --resume.
Remote workers
Hand a ticket to Taskr Worker.
Assign a ticket to Taskr Worker and it runs Claude Code in a sandbox, with the same plugin, tools and briefing as your own.
01 Assign
Assign it like a teammate.
Taskr Worker sits in the assignee list next to the people. Tom picks it for TSK-152, Refund partial captures.
02 Sandbox
It runs in a sandbox.
On your organisation's own Anthropic key. Keys and tokens stay outside the sandbox, so nothing in an issue or a repo can read them.
03 Progress
It reports back like any agent.
The worker claims the ticket, reports progress and gets overlap warnings like any other agent. TSK-152 moves to In progress on Tom's screen.
04 Take over
Take it back on your laptop.
claude --resume picks up the worker's run in Maya's terminal, on the
same branch with the same transcript.
Same ticket. Now it's Maya's.
The assignee changes to Maya via Claude Code. The activity log keeps both: Taskr Worker started it, Maya took it over.
The pictures in this section show two windows: Maya's terminal running Claude Code and Tom's Taskr web app. The agent records the double charge, fixes it and records the same steps passing; the evidence lands on issue TSK-148, and pull request #212 gets a Taskr proof check that passes.
Proof of work
Review starts from evidence.
Agents attach what a good engineer would: a recording of the bug, the same steps passing after the fix, and the regression test.
01 Reproduce
First, it records the bug.
Before changing code, the agent records the failure: Stripe delivers invoice.paid a second time, and the card is charged $48.00 again.
02 Verify
Then the same steps, passing.
After the fix it records the same steps again. The retry is skipped because the event was already processed.
03 Evidence
The evidence lands on the issue.
Each piece says how it was made: reported, recorded, or re-run by Taskr. Tom reads it on TSK-148 before he opens the diff.
04 Check
One check on the pull request.
Taskr proof lists the evidence on #212, next to your other checks, with the regression test re-run by Taskr.
05 Review
A person still approves.
Tom reviews #212 with the evidence in front of him. Your branch rules decide whether merging waits for the Taskr proof check.
Pricing
Priced per person. Agents come with them.
Agents work through the seat of the person who runs them, so you never pay for them twice.
Team
$8per person
per month
- Everything in Free
- Doc updates proposed when a ticket closes
- Remote workers
- Proof-of-work checks
Enterprise
Custom
- Everything in Team
- Single sign-on
- Audit log export
- Invoiced billing and a written agreement
Put the whole team on the same ticket.
People and their agents, on every screen they own.