Skip to main content

Pi

Timon can run agents on Pi (pi.dev), the token-frugal coding agent. It drives Pi through the pi-acp adapter, over the Agent Client Protocol; Pi keeps its own sign-in and provider keys, and Timon never sees or stores them.

Set it up​

  1. Install Pi and its adapter (Node.js 22 or later):

    npm install -g @earendil-works/pi-coding-agent pi-acp

    The adapter needs the pi command (version 0.81 or later) on the same PATH. Timon does not launch it with npx -y pi-acp: a first npx run downloads the package while the mission waits.

  2. Sign in, in a terminal, under the OS account that runs Timon:

    pi-acp --terminal-login

    (or configure Pi's providers or API keys as Pi's own documentation describes).

  3. Restart Timon. Pi then appears among the LLM backends.

If Pi does not appear, run timon doctor: it tells you whether the pi-acp binary was found. A command installed somewhere the service's PATH does not cover can be pinned: set host.binaries.pi-acp to its absolute path. If a mission stops with "sign in first", run pi-acp --terminal-login in a terminal on the machine that runs Timon, then retry.

Models​

Timon does not pick a model for Pi: the default is Pi's own. Pi routes to several providers, so the model picker lists what your Pi setup offers. The list is asked from Pi and refreshed at most every 12 hours; opening it starts Pi briefly, which leaves one empty session in Pi's own history. A model change applies from the next session.

What agents can do​

Replies stream into the chat and tool calls appear with their results. Stop in a chat ends the current turn and keeps the conversation; after a restart, the mission reopens its Pi session.

Pi decides its own tool permissions: Timon shows no Allow / Deny card for it and cannot restrict what it does. The agent editor says so.

Limitations​

  • Not yet tried on a tester's own account. Timon was checked against a scripted stand-in, not a full session on a real Pi setup, so a first mission may still fail. Report what you see.
  • Timon's own tools do not reach Pi. The adapter does not pass MCP servers on, so the Kanban, questions, missions and memory tools, and the MCP servers configured for the agent, are not available to a Pi agent.
  • No separate reasoning block. The adapter sends Pi's answer as one stream.
  • No live model switch. A model change applies from the next session.
  • No quota gauge. Timon does not display your remaining usage.