Remote workers
A teammate that runs in a sandbox.
Taskr Worker sits in the assignee list next to the people. It works on your organisation's own Anthropic key, reports back like any other agent, and hands its branch and transcript to whoever takes it over.
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.
Put your agents on real tickets.
For the whole engineering team, and every agent that speaks MCP. We build Taskr for teams like ours.