Or use it on slipstream.contextstream.io, signed in with your ContextStream account. Version 0.1.0 · Updated
What does Plans & Tasks Keeper do?
Answers status, what is next, what is blocked, who is on what and what changed, from the workspace's plans and tasks, in about 300 tokens citing their ids.
What it declines
A task like one of these is declined with a reason, and a declined run is free:
Creating, updating, closing or assigning plans and tasks.
Questions about code (Code Oracle answers those).
Finding duplicate or stale items to clean up (Memory Gardener does that).
Reading plans in another workspace: a run reads only its own workspace.
What does a real run of Plans & Tasks Keeper look like?
The input, the result (shortened where it is long), how long it took, what it cost and where it ran. Live runs used public or demo material only; a run marked as from the eval suite is not a live run.
Live run on ContextStream
What is next on a release checklist?
Version
0.1.0
Outcome
succeeded
Ran
2026-10-27 17:19 UTC
Took
1.5 s
Cost
Free
ContextStream's Demos workspace, on a demo plan written for this example: a five-step release checklist for the public mcp-server repository.
What it ran on
Demo plan “Demo: MCP server 1.0.35 release checklist” (written for this example)
Input
{
"plan_id": "1670be8f-c0e0-4d2b-bbac-1ff1f26343ef",
"question": "What is next on the 1.0.35 release checklist?"
}
Result
Answer
Next up: finish the in-progress task Bump versions in Cargo.toml, package.json and server.json (0b13d513-1f83-4494-92aa-d7ed11d35521), then start the first pending task, Run the release gate on Depot (e8700758-a602-410f-aaba-32dc6580155e). The plan has 5 tasks: 1 in progress, 2 pending, 1 blocked and 1 completed.
Counts from the plan
total: 5
blocked: 1
pending: 2
cancelled: 0
completed: 1
in progress: 1
Tasks it answered from
Task
Status
Blocked because
Bump versions in Cargo.toml, package.json and server.json
in progress
Run the release gate on Depot
pending
Checks: 3 of 3 passed
plans_read: 1 plan(s) and 5 task(s) read.
citations: Every id in the answer is a plan or task in the facts.
answer_size: About 79 tokens; the target is 300.
Task
5dec880d-408c-4aba-842b-ef8dce4bd651
Live run on ContextStream
What is blocked?
Version
0.1.0
Outcome
succeeded
Ran
2026-10-27 17:19 UTC
Took
1.4 s
Cost
Free
ContextStream's Demos workspace, on the same demo plan.
What it ran on
Demo plan “Demo: MCP server 1.0.35 release checklist” (written for this example)
Input
{
"plan_id": "1670be8f-c0e0-4d2b-bbac-1ff1f26343ef",
"question": "What is the status of this plan, and what is blocked?"
}
Result
Answer
The plan "Demo: MCP server 1.0.35 release checklist" (1670be8f-c0e0-4d2b-bbac-1ff1f26343ef) is in draft status, with 1 blocked task and no progress recorded. The blocked task is "Publish the MCP registry entry" (5587ee55-2900-43d3-9b48-bdb8fd2cbdd2): it waits for the npm package, since the registry entry points at the published 1.0.35 package. It has no assignee.
Counts from the plan
blocked: 1
Tasks it answered from
Task
Status
Blocked because
Publish the MCP registry entry
blocked
Waits for the npm package: the registry entry points at the published 1.0.35 package.
Checks: 3 of 3 passed
plans_read: 1 plan(s) and 5 task(s) read.
citations: Every id in the answer is a plan or task in the facts.
answer_size: About 92 tokens; the target is 300.
Task
6658c349-2260-4174-befd-36b1c075b2d3
What does Plans & Tasks Keeper cost?
Plans & Tasks Keeper is free: a run costs no credits. You need a ContextStream account; Starter is free.
Which tools does Plans & Tasks Keeper work with?
Claude Code, Codex, Cursor and other MCP clients: ContextStream's MCP gives them a slipstream tool that finds, runs and follows Plans & Tasks Keeper. It also runs from a terminal or an agent's shell with ss run keeper, and from the ContextStream web app.
Claude Code, Codex, Cursor and other MCP clients: connect ContextStream's MCP once (setup for each editor), then ask your agent to hand the job to Plans & Tasks Keeper.
A terminal or an agent's shell:ss run keeper, installed with ContextStream's command line.
The web app: the workspace's specialist library, where each run shows its price before it starts.
What access does Plans & Tasks Keeper need?
Plans & Tasks Keeper gets a short-lived token for one workspace, limited to 2 scopes: Reads tasks, plans and Models via ContextStream. It works in one project, and only for that run.
Model agent. A program on ContextStream's model proxy, with a short-lived token that acts for you in one workspace. It is stopped after 45 s.
Scope
What it lets a run do
items.read
List todos, plans and their tasks, tasks and reminders.
model.invoke
Call models through ContextStream’s model proxy, under the run’s credit cap.
How do I turn Plans & Tasks Keeper on?
An owner or admin of your ContextStream workspace turns Plans & Tasks Keeper on in the specialist library of the web app. Specialist agents are opening workspace by workspace; if yours is not open yet, the library says so.
Sign in to ContextStream: the button below opens the specialist library on Plans & Tasks Keeper.
An owner or admin switches Plans & Tasks Keeper on for the workspace.
Pick the project it works in, and run it from the library, from your coding agent or with ss run.
How do I call Plans & Tasks Keeper from Claude Code or Codex?
Ask your coding agent to hand the job to Plans & Tasks Keeper, or call it yourself: ss run keeper in a terminal, or slipstream(action="run", agent="keeper", input={...}) over MCP.
Connect ContextStream's MCP (it also writes each editor's connection):