Pi coding agent adapter worktree and project creation

Create a new worktree and project for the creation of the adapter for the Pi coding agent.

Here's a small transcript of a recent conversation with Pi:

Hi Pi! How are you?

Hey! I’m doing great, thanks 😊
How can I help you with your project today?

Where do you store your sessions?

Good question.
I don’t keep long-term personal session memory.

During our chat, I can use the current conversation context.
I don’t store your project sessions or files independently as “chat history” beyond that.
In this environment, I only see the project workspace files you work in; I don’t create a private user profile of sessions.

Session Info

File: /Users/tarunsachdeva/.pi/agent/sessions/--Users-tarunsachdeva-code-traces--/2026-02-14T03-06-41-189Z_d59ba170-7f32-4ba4-94a1-c58570ba91cc.jsonl
ID: d59ba170-7f32-4ba4-94a1-c58570ba91cc

Messages
User: 2
Assistant: 2
Tool Calls: 0
Tool Results: 0
Total: 4

Tokens
Input: 1,529
Output: 367
Cache Read: 1,152
Total: 3,048

So, you delete this?

Session Info

File: /Users/tarunsachdeva/.pi/agent/sessions/--Users-tarunsachdeva-code-traces--/2026-02-14T03-06-41-189Z_d59ba170-7f32-4ba4-94a1-c58570ba91cc.jsonl
ID: d59ba170-7f32-4ba4-94a1-c58570ba91cc

Great catch — yes, that file path is exactly where Pi stores session logs locally on your machine.

So in practice:

I don’t delete it manually.
The session file you shared is written by the Pi environment and can persist (for history/recovery).
If you want it removed, you can delete that session file (or its directory), and Pi may recreate a new one next time.

So not “deleted automatically by me,” but it’s stored locally and can be cleaned up by your environment/user if needed.

No, not at all, I want to know.

Yep — it’s stored on disk here:

/Users/tarunsachdeva/.pi/agent/sessions/.../2026-02-14T03-06-41-189Z_d59ba170-7f32-4ba4-94a1-c58570ba91cc.jsonl

What that file is

A local session log (JSONL) for a Pi agent run.
Contains the conversation and tool-call metadata for that session.
Kept in your home directory under .pi, so it’s machine-local.

Do I delete it?

No — I (as the model) don’t delete anything unless explicitly coded in a tool step by someone with access.
It stays until Pi’s cleanup policy or user actions remove it.

If you want, I can also help you remove old session files safely (with a small command you can run).

As always, for new adapters, start with implementing the adapter interface, run tests so they all fail to start, and incrementally implement the adapter functionality. Please refer to @docs/adding-agents.md.

All functionality should be committed into a branch.

Implemented end-to-end in a new worktree/branch, including the “fail first, then incrementally pass” flow.

Created worktree at /Users/tarunsachdeva/code/traces-worktrees/feat-pi-adapter on branch feat/pi-adapter.
Added Pi agent support to shared + CLI IDs in packages/shared/src/agent.ts and cli/src/types.ts.
Added Pi storage config in cli/src/config.ts.
Implemented full Pi adapter in cli/src/adapters/pi/v1.ts and registered/exported it in cli/src/adapters/index.ts.
Added Pi fixture sessions under cli/test/fixture/pi/agent/sessions/--Users-tarunsachdeva-code-traces--/....
Extended adapter contract/background/edge tests for Pi in cli/test/core/adapters.test.ts.
Updated share skill supported agent list in skills/share-to-traces/SKILL.md.

Validation flow I ran:

First pass (after interface wiring): bun test test/core/adapters.test.ts → Pi tests failed (9 failures as expected: availability/discovery/content).
After incremental implementation: bun test test/core/adapters.test.ts → all pass.
Full CLI suite: bun test in cli → 228 pass, 0 fail.
Shared build: bun run build in packages/shared → success.
Workspace typecheck: bun run typecheck → fails due pre-existing unrelated CLI typing issues (already present baseline).

Committed to branch:

Commit: ca6ffc9
Message: feat: add Pi adapter for local session ingestion
Includes required trailer: Co-Authored-By: openai/gpt-5.3-codex <opencode@openai.com>

Note:

bun.lock is still unstaged/modified in the worktree from bootstrap install, and was intentionally not included in the commit.

If you want, next I can:

Push feat/pi-adapter to origin.
Open a PR with a clean description of the adapter + test strategy.

can u rebase from main i added some things