Titpea
Pi, unchanged
Pi's own terminal interface, engine and tools. History stays in Pi's JSONL files.
celagent Built on Pi, the open-source terminal coding agent
Resume on a new machine.
Saves each Pi coding-agent session to Baidu Object Storage (BOS), turn by turn. Resume it on another machine you have set up.
curl -fsSL https://github.com/hxddh/celagent/releases/latest/download/install.sh | sh Pi Coding Agent TUI · Baidu BOS
- License
- MIT
- Version
- v0.4.3
- Released
- Aug 26, 2026
- Network
- Automatic
- Source
- hxddh/celagent
$ celagent
COMMANDS
-
celagent -
celagent list -
celagent <id> # restore from BOS -
celagent task ledger
persistence Completed turns → BOS write queue → restore by session ID after a successful write
Configure both machinesConflicting writes from two machines are caught
The full Pi session, not a summary
Saved per turn
Each finished turn is queued and written to BOS; conflicting writes are caught.
No silent fallback
A failed write stays queued to retry; a truncated cached copy never replaces history.
Configure storage
Set up BOS; celagent doctor checks access, celagent cas-probe checks conflict detection.
Resume by ID
On a configured machine, celagent list shows sessions; celagent <id> opens one.
Get started
After installing, check that celagent can reach your BOS bucket.
-
Check configuration, credentials, and BOS access
celagent doctor
Where your data goes
- Each completed turn is written to your BOS bucket as Pi JSONL; Celld, a local runtime that celagent starts, caches it.
- Prompts and tool results go to the model you configure, DeepSeek by default.
- Without a model API key, celagent answers with placeholder replies so you can test storage.
- Storage keys come from environment variables or the
[bos]profile in~/.aws/credentials;celagent rm <id>deletes a session.
FAQ
Does it sync my workspace?
No. Session recovery does not set up the project files or environment on the other machine. Wait for the BOS write to succeed before relying on remote recovery.
What if a BOS write fails?
Retryable failures stay queued, and recovery on another machine waits for a successful write. Recovery reads BOS first and uses the local Celld cache only when the session is not in BOS at all. A BOS timeout or permission error never falls back to that cache, which may be truncated.
How is history stored?
Each session is saved in your bucket as sessions/<id>.jsonl, Pi's own history format, with tool calls and branches. Older .json sessions can still be read and are restored as text.
How do I install it?
Run the install script at the top of this page. On Windows, run the README’s install.ps1 command in PowerShell; it installs celagent without Celld, which has no Windows package upstream. Then run celagent doctor.
celagent