Zirkles

Connect your agent harness

What it is

Your finished plans (Planning) and checks (Research) can be read by the agent you code with, as plain plan.md Markdown files. The agent reads them through the same MCP server as everything else. Reading changes nothing and spends no coins.

A plan or check can contain text from documents and from other peoples repos. Zirkles hands it over inside a labelled frame, and a good agent treats the inside as data, not as instructions from you.

Connect it

Claude Code. Add the server once, then run /mcp and sign in:

claude mcp add --transport http zirkles https://lsjimakbumovwrrxbxrj.supabase.co/functions/v1/mcp

Codex and other clients

Codex reads ~/.codex/config.toml. Any other client that speaks MCP over HTTP needs the same address:

[mcp_servers.zirkles]
url = "https://lsjimakbumovwrrxbxrj.supabase.co/functions/v1/mcp"

Allow it to read

Plans and checks follow your notes: an agent reads them only after you approved it for at least one knowledge collection of that workspace. The first time, the agent calls knowledge_request_access and gives you a link. Open it, check what it asks for, and approve. You can revoke it any time under Agents.

What the agent can call

  • plan_list: your finished plans and checks, newest first, with an id each.
  • plan_get: one of them as a plan.md file. An id that is not yours looks the same as one that does not exist.
  • knowledge_route, knowledge_search and knowledge_add: find, read and add notes.

From a script

No agent needed: an API key reads the same files.

curl -s "https://lsjimakbumovwrrxbxrj.supabase.co/functions/v1/api/v1/plans" \
  -H "Authorization: Bearer $ZIRKLE_API_KEY"

curl -s "https://lsjimakbumovwrrxbxrj.supabase.co/functions/v1/api/v1/plans/PLAN_ID" \
  -H "Authorization: Bearer $ZIRKLE_API_KEY"

Staying in control

An agent sees nothing until you approve it, and only what the approved collection reaches. Plans and checks can be long: the agent gets the first part and is told when it was cut.