0gpc

Build on the trust layer for AI.

Intro

Use 0G Private Computer in your coding tools.

Requires macOS or Linux (Windows is not supported), Node.js 22+, and an installed coding tool.

Install or upgrade Node.js. If you already use nvm:

nvm install 22
nvm use 22

Integration

Currently supported coding tools:

• Claude Code
• OpenCode
• Pi
• Hermes Agent

OpenCode V2 and non-default Hermes profiles are not supported.

Features

• Guided setup — Connect your tool in a few steps.
• Model details — Compare providers, context and capabilities.
• Hidden key input — Enter your API key privately.
• Configuration preview — Review changes before saving.
• Reversible changes — Disconnect without removing unrelated settings.
• Connection management — Manage tools, models and keys.
• Optional verification — Confirm before paid checks or tool launch.
• Automation support — JSON output for scripts; no telemetry.

0gpc stores the Router root address for each key. It appends /v1 to requests that use the OpenAI-compatible or Anthropic-compatible API paths; do not include /v1 in the saved root address.

Security

• Your key stays private — Enter it with hidden input or --stdin. It is saved in 0gpc's own key store (~/.local/share/0gpc/keys/, readable only by you) and is never printed, logged or included in JSON output.
• Only 0gpc's own fields change — Interactive setup shows the configuration changes before saving; for scripts, apply --dry-run previews and apply --yes writes. key set saves the key at once and also updates the tool configurations already connected to it (for example the Hermes .env entry, or the base URL when the endpoint changes); it has no separate preview. Files are backed up and written atomically, unrelated settings are kept, and reset restores the values you had before.
• No paid checks without your consent — Listing models does not verify your key. Verification sends one minimal request only when you confirm it in setup, run key set --verify, or run doctor --network.
• Nothing runs behind your back — No telemetry and no automatic update checks. 0gpc shows install or update commands for you to run; it never runs them itself.

Quick Start

Get your 0G API key, then run:

npx @0gfoundation/0gpc@latest

Or install globally for the shorter 0gpc command:

# Install or upgrade
npm install -g @0gfoundation/0gpc@latest

# Start in your project directory
0gpc

Use ↑/↓ to navigate, Enter to confirm, and Ctrl-C to cancel.

Command list

The examples below use the global 0gpc command. Without a global install, replace it with npx @0gfoundation/0gpc@latest.

# Show help
0gpc -h
0gpc --help

# Show version
0gpc -v
0gpc --version

# Open setup or manage existing connections
0gpc

# API key management
0gpc key set                   # Save or replace a key using hidden input
0gpc key set --stdin           # Read a key from piped standard input
0gpc key rm                    # Remove an unused saved key

# Show connections
0gpc status
0gpc status --json             # Machine-readable output

# Health checks
0gpc doctor --offline          # Check local configuration
0gpc doctor --offline --strict # Fail on warnings as well as errors
0gpc doctor --network          # Verify access; may incur a charge

# Preview configuration (run from your project root)
0gpc apply claude --scope project --model <model-id> --dry-run

# Save configuration
0gpc apply claude --scope project --model <model-id> --yes

# Disconnect the connection used in this directory; keep the saved key
0gpc reset claude --yes

# Disconnect the user-level connection
0gpc reset claude --scope user --yes

Replace <model-id> with a compatible model ID. Tool IDs: claude, opencode, pi, hermes. Scopes: project or user; Pi and Hermes use user only. Claude Code and OpenCode may be connected to multiple projects; project identity is tracked per project. In a Git worktree, Claude Code's project configuration lives at the main checkout's root and is shared by all worktrees of that repository.

JSON output uses schema_version: 3.

Network troubleshooting

0gpc does not configure proxies or change request behavior. If a request fails while HTTPS_PROXY (or HTTP_PROXY for an HTTP endpoint) is set, Node.js 22.21+ and 24.0+ require proxy support to be enabled at process startup:

NODE_USE_ENV_PROXY=1 0gpc doctor --network

On older Node.js versions, upgrade Node.js first. NO_PROXY can bypass the proxy for selected hosts. 0gpc's diagnostic hint names only the environment variable; it never prints proxy values or addresses.

Configuration file

| Default path | Contents | |---|---| | ~/.config/0gpc/config.toml | Connections and preferences | | ~/.local/share/0gpc/keys/ | Saved API keys | | ~/.local/state/0gpc/ | Change records and backups |

Supports XDG paths and ZGPC_HOME for custom 0gpc storage.

| Tool | Default configuration files | |---|---| | Claude Code | Project: .claude/settings.local.json; user: ~/.claude/settings.json | | OpenCode V1 | Project: opencode.json or opencode.jsonc; user: under ~/.config/opencode/ | | Pi | ~/.pi/agent/models.json and ~/.pi/agent/settings.json | | Hermes Agent | ~/.hermes/config.yaml and ~/.hermes/.env |

MIT License · 0G CLI