Skip to content

protoCLI

protoCLI is the namesake SDK and the default agent runtime for protoLabs Studio. Every new agent run routes through it; the Claude / Cursor / Codex / OpenCode CLI integrations remain available for users who prefer those tools but are no longer the primary path.

The agent in this app uses the bundled SDK (@protolabsai/sdk) so a standalone CLI install isn't required. Installing the standalone proto binary just lets you run protoCLI in any terminal outside the app.

Quickstart

The protoCLI quickstart, command reference, skill catalog, and configuration docs live in the upstream repo. Start there:

How protoLabs Studio uses it

Runtime path@protolabsai/sdk query() calls from the server's ProtoProvider (and from ClaudeProvider via the @protolabsai/sdk/anthropic-compat subpath)
GatewayAll requests route through https://api.proto-labs.ai/v1 by default. Override via GATEWAY_BASE_URL env.
AuthGATEWAY_API_KEY env (preferred) or OPENAI_API_KEY env. Org-issued; no per-user login.
Default modelprotolabs/smart

In-app status

The app autodetects protoCLI install + gateway connectivity:

  • Settings → AI Providers → protoCLI — connection status card with CLI version, env-var source, and gateway reachability
  • Setup wizard → Providers step — protoCLI is the default-active first tab and runs the same status check on open

Both surfaces read from GET /api/setup/proto-status on the server.

Where the rest of the docs live

This page intentionally avoids duplicating what's already in the protoCLI repo. For:

  • Install + login — see the protoCLI README
  • Available skills (test-driven-development, systematic-debugging, sprint-contract, etc.) — see the skills catalog in the repo
  • CLI commands (/help, /auth, /model, /skills, /memory, /voice, /team, etc.) — proto --help after install
  • SDK API (programmatic query(), tool(), MCP servers, hooks) — see packages/sdk-typescript README

Built by protoLabs — Open source on GitHub