pi-codebuddy-sdk

Pi extension that registers CodeBuddy as a model provider. You keep using Pi for the TUI, tools, skills, and extensions; CodeBuddy Agent SDK runs inference locally via the codebuddy CLI. No HTTP proxy and no changes to how you work in Pi beyond picking a model.

What it does

• Exposes CodeBuddy models in Pi (codebuddy/... in /model)
• Bridges Pi tools to the SDK (Pi still executes tools; CodeBuddy only plans and calls them)
• Forwards Pi's system prompt, skills, and project AGENTS.md so the model acts as Pi—not as standalone CodeBuddy Code
• Supports session resume, compaction, streaming, thinking levels, and images
• Optional AskCodebuddy tool to delegate a focused sub-task to another CodeBuddy call

Install

pi install npm:pi-codebuddy-sdk

Restart pi if it was already running.

Requirements

• codebuddy on your PATH — the extension spawns the same CLI you use standalone. If which codebuddy fails, either add it to PATH or set pathToCodebuddyCode in codebuddy-sdk.json (see Configuration).
• CodeBuddy auth already working — if codebuddy works in your terminal, you do not need extra setup for this extension.

Quick start (already using CodeBuddy)

No codebuddy-sdk.json and no plugin-specific env vars are required.

1. pi install npm:pi-codebuddy-sdk
2. Restart pi
3. /model → pick codebuddy/...

Optional: set defaultProvider / defaultModel in ~/.pi/agent/settings.json so you skip /model each time.

The first query after startup may take a few seconds while models are discovered from the SDK.

Auth

The extension does not store credentials. The CodeBuddy CLI reads them from your machine. Use one of the following:

1. CLI login (recommended)

codebuddy login

Complete login in the browser. Credentials stay on your machine; Pi reuses them automatically.

2. API key

export CODEBUDDY_API_KEY="your-api-key"

Obtain the key from your CodeBuddy account. Do not commit it or store it in repo files.

3. Tencent iOA (internal network)

export CODEBUDDY_INTERNET_ENVIRONMENT=ioa
codebuddy login

Use this when CodeBuddy must run on the iOA network. Add CODEBUDDY_API_KEY as well if your environment requires it.

Usage

pi
/model

Pick any entry prefixed with codebuddy/ (for example codebuddy/hy3-preview-agent-ioa).

Tools, skills, extensions, /compact, and steer behave the same as with other Pi providers.

Configuration

Optional. Defaults work for most users.

File: ~/.pi/agent/codebuddy-sdk.json or .pi/codebuddy-sdk.json in a project.

{
  "askCodebuddy": {
    "enabled": true,
    "allowFullMode": true
  },
  "provider": {
    "appendSystemPrompt": true,
    "strictMcpConfig": true,
    "pathToCodebuddyCode": "/path/to/codebuddy"
  }
}

| Option | Default | Meaning | |--------|---------|---------| | askCodebuddy.enabled | true | Register the AskCodebuddy delegation tool | | askCodebuddy.allowFullMode | true | Allow write-capable delegation mode | | provider.appendSystemPrompt | true | Use Pi's system prompt instead of CodeBuddy's default identity | | provider.strictMcpConfig | true | Use only Pi-bridged MCP tools | | provider.pathToCodebuddyCode | auto | Path to codebuddy when it is not on PATH |

Privacy

• The extension does not send conversation data to this repository or any third-party telemetry endpoint.
• Credentials are handled entirely by the CodeBuddy CLI on your machine.
• Optional debug mode (CODEBUDDY_SDK_DEBUG=1) writes local logs under ~/.pi/agent/; paths are redacted, prompts and tool payloads are not logged. Delete logs when finished.

Troubleshooting

export CODEBUDDY_SDK_DEBUG=1

Default log: ~/.pi/agent/codebuddy-sdk.log. See CONTRIBUTING.md for maintainer details.

Development

Maintainers: CONTRIBUTING.md.

License

MIT

Inspiration

Early MCP bridge patterns were inspired by pi-claude-bridge. This package is a separate codebase on @tencent-ai/agent-sdk.