Files

gsxdsm 1872abc1d0 fix(pi-claude-cli): source MCP tool list from session Context, not pi.getAllTools

The previous fix regenerated the MCP config per call but still pulled the tool
set from pi.getAllTools(), which depends on the runtime binding being scoped to
the right AgentSession. Engine-spawned triage/executor sessions register custom
tools (fn_review_spec, fn_review_step) and pi-ai already passes those to the
provider via Context.tools — that's the authoritative per-session list and
bypasses any binding ambiguity. Falls back to pi.getAllTools() when the caller
doesn't populate Context.tools.

Also logs the tool names on refresh so missing tools are diagnosable from stderr.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-25 14:31:15 -07:00

src

fix(pi-claude-cli): source MCP tool list from session Context, not pi.getAllTools

2026-04-25 14:31:15 -07:00

CHANGELOG.md

chore(release): v0.2.7

2026-04-25 11:38:48 -07:00

index.ts

fix(pi-claude-cli): source MCP tool list from session Context, not pi.getAllTools

2026-04-25 14:31:15 -07:00

LICENSE

feat: add "Anthropic — via Claude CLI" as a first-class provider

2026-04-23 23:02:34 -07:00

package.json

chore(release): v0.2.7

2026-04-25 11:38:48 -07:00

README.md

feat: add "Anthropic — via Claude CLI" as a first-class provider

2026-04-23 23:02:34 -07:00

tsconfig.json

chore: consolidate test files into __tests__/ dirs and clean stray engine artifacts

2026-04-24 19:39:20 -07:00

UPSTREAM.md

feat: add "Anthropic — via Claude CLI" as a first-class provider

2026-04-23 23:02:34 -07:00

vitest.config.ts

feat: add "Anthropic — via Claude CLI" as a first-class provider

2026-04-23 23:02:34 -07:00

README.md

pi-claude-cli

A pi extension that routes LLM calls through the Claude Code CLI as a subprocess. Use your Claude Pro/Max subscription as the LLM backend — no API key, no separate billing.

How it works

The extension registers as a custom pi provider exposing all Claude models. Each request spawns a claude -p subprocess using the stream-json wire protocol, with --resume on follow-up turns to reuse the CLI's session state instead of replaying full history. Claude proposes tool calls, pi executes them natively. Custom pi tools are exposed to Claude via a schema-only MCP server.

Requirements

Claude Code CLI installed and authenticated (claude on PATH)
A Claude Pro or Max subscription
pi or GSD

Installation

Add to ~/.gsd/agent/settings.json:

{
  "packages": ["npm:pi-claude-cli"]
}

Then select a Claude model via /model in the interactive UI. All Claude models appear under the pi-claude-cli provider.

Features

Streams text, thinking, and tool call tokens in real-time
Maps tool names and arguments bidirectionally between Claude and pi
Exposes custom pi tools to Claude via MCP (schema-only, no execution)
Break-early pattern prevents Claude CLI from auto-executing tools
Session resume via --resume eliminates history replay on follow-up turns
Configurable thinking effort with elevated budgets for Opus models
Cross-platform subprocess management (Windows, macOS, Linux)
Inactivity timeout and process registry for cleanup

License

MIT