pi-zit

Zit for the Pi coding agent. Pi works in a disposable Zit workspace, claims what it edits so other agents on the same repository do not duplicate it, and its work is recorded as a Zit change with its own account of what it did and why.

sequenceDiagram
    participant U as you
    participant P as Pi + pi-zit
    participant Z as zit
    U->>P: /zit add usage docs
    P->>Z: zit materialise --agent pi
    Z-->>P: .../ws/<id>/tree
    P->>P: session moves into the workspace
    P->>Z: zit_claim README.md#Usage
    Z-->>P: claimed (or refused: held by ...)
    P->>Z: zit_record "what and why"
    U->>P: quit
    P->>Z: zit record --dispose

Requirements

• Pi. Tested with 0.84.4.
• The zit binary on PATH, or ZIT_BIN set to it. Without it the tools fail with an install hint.
• A git repository. /zit offers to run zit init the first time.

Install

From npm, or from a checkout of this repository:

pi install npm:pi-zit                           # all projects (~/.pi/agent/settings.json)
pi install /path/to/getzit/integrations/pi      # or from a checkout
pi -e /path/to/getzit/integrations/pi           # this run only

Once published to npm:

pi install npm:pi-zit

pi install git:github.com/autohandai/getzit does not work: Pi installs a git repository from its root, and this package lives in integrations/pi.

Install it for all projects (the default), not with -l. A session started by /zit runs in the workspace directory, and Pi reads project settings (.pi/settings.json) from there. A project-scoped install is only seen in the workspace if .pi/settings.json is committed, names the package by npm: rather than by a local path, and the workspace is trusted.

Use

Three ways into a workspace. In all of them the extension detects the workspace (path .../ws/<id>/tree next to a meta.json, or ZIT_WORKSPACE), turns on the tools below and adds the Zit rules to the system prompt.

From a session: /zit add usage docs. This creates a workspace and moves the session into it: Pi's tools and ! commands run there from then on, and your checkout is not touched. With no intent, Pi asks for one.

From the command line: pi --zit "add usage docs", which runs /zit at startup. Not in print (-p) or JSON mode, where the prompt runs before the session can move; there pi-zit prints the alternatives below and does nothing else.

Without the slash command:

cd "$(zit materialise --agent pi --intent "add usage docs")" && pi

For headless runs, zit run --agent pi --intent "..." runs pi -p in a workspace and records it when Pi exits; pi-zit then writes Pi's last reply to $ZIT_SUMMARY_FILE so zit run keeps it with the change.

What the model gets

The system prompt says: you are one of several agents; claim before editing; if a claim is refused, pick other work or stop; zit_status shows the others; do not commit; finish with zit_record and a short summary of what was done and why.

Commands and flags

When Pi quits

Inside a workspace, quitting Pi runs zit record --summary <Pi's last reply> --dispose: the work becomes a change, the reply (at most 8,000 characters) is stored as its summary, and the workspace is deleted. If nothing changed since the last record, the workspace is just deleted. With auto-record off the workspace is left in place for zit record or zit dispose. Under zit run, pi-zit leaves recording to zit run.

Switching session (/new, /resume, /fork) or /reload does not record.

Limits

• /zit needs a saved session: it switches to a new session file whose working directory is the workspace. With --no-session, use the cd "$(zit materialise ...)" form.
• --zit hands off to /zit asynchronously; a prompt sent in the same instant may still run in the original directory.
• Claims prevent wasted work; they guarantee nothing. What lands is decided when a change is accepted.
• The model's side has not been run end to end yet: on the machine this was built on Pi's model provider key had expired ("API key expired"). Against real Pi 0.84.4 (RPC mode, which drives the same commands as the terminal UI) and the real zit binary, without a model turn: /zit, --zit, the session moving into the workspace, the tools being enabled, the system prompt, /zit-record, and recording on quit. The tool handlers are covered by npm test.

Develop

npm install
npm test          # node:test against the real zit binary in a temp repository
npm run check     # tsc --noEmit

Tests use ZIT_BIN, defaulting to ../../target/release/zit (cargo build --release at the repository root), and a temporary ZIT_HOME.

Licence

GPL-2.0-only, the same as Zit and git: LICENSE.