Skip to main content
Gobare does not have an agent of its own. Every session runs pi — the open-source coding agent by Mario Zechner, MIT-licensed — inside the session’s sandbox, unmodified. Gobare is the computer around it and the API in front of it. So the agent you are calling is one you can read, run on your own laptop, and compare against.

​
Which pi

Gobare follows pi’s releases: the pi core in the sandbox is updated regularly to track upstream, so improvements to pi reach your sessions without you doing anything. The table shows the version running today; between an upstream release and the next update, the sandbox can be a release or two behind the latest on npm.

​
What “unmodified” means

pi is installed from npm exactly as published — no fork, no patches. Gobare drives it through pi’s own SDK (createAgentSession, SessionManager) and changes its behaviour only through the extension points pi provides for that. That is checked, not asserted. Inside a production sandbox, the published tarball was downloaded fresh and compared file by file with what the agent runs:
pi-ai was identical. pi-coding-agent was identical in every file the package ships; the only difference was the node_modules directory npm creates when it installs the package’s own dependencies. You can run the same check yourself: log into a session’s machine and run it there.

​
What pi does, and what Gobare adds

A session’s conversation is a genuine pi session file. The first line of one, from a production sandbox:

​
Why it matters

  • It is not a black box. When the agent does something surprising, the code that decided it is public. Read it, or reproduce the behaviour with pi on your own machine.
  • Your prompts carry over. The agent loop and native tools are the ones you get running pi yourself. What Gobare adds sits on top, through pi’s own extension points, rather than replacing anything.
  • What you learn about the agent is yours. It stays true outside Gobare.

​
Bringing a pi session in, and back out

If you already work with pi locally, the gobare CLI moves a stopped pi session into Gobare as a project, together with its workspace:
For a project imported that way, gobare pi export downloads its latest checkpoint back out as a pi session file:
This is a migration, not a live sync: finish or cancel anything pi still has queued before you exit it, because pending follow-up messages live only in the running pi process and are not part of the session file. The CLI is a Node 22+ package installed from its GitHub releases; its README covers tokens, resuming an interrupted upload, and what is and is not carried across. These two commands were not exercised in writing this page.

​
Next