Stakpak Agent CLI

You can use your own Anthropic or OpenAI API keys, custom OpenAI compatible endpoint, or a Stakpak API key.

Before running autopilot on a remote VM:

- Docker must be installed and accessible to the current user
- 2GB+ RAM is recommended for reliable autopilot + sandbox runs
- Swap is strongly recommended on small Linux hosts
- Linux user services may require linger to survive logout

stakpak up now runs preflight checks before startup, and stakpak autopilot doctor can be used as a deployment-readiness check before first boot:

stakpak autopilot doctor
stakpak up

See also: cli/README.md

- ~/.stakpak/config.toml: profile behavior (model, allowed_tools, auto_approve, system_prompt, max_turns, provider credentials)
- ~/.stakpak/autopilot.toml: runtime wiring (schedules, channels, notification routes, service/server settings)

Use profile = "name" on schedules/channels and keep behavior inside profile definitions. Profiles control how the agent behaves: model, allowed tools, auto-approval, system prompt, max turns, and provider credentials. Notification routes only control where messages are delivered.

Schedule and channel profiles are intentionally separate:

- schedule --profile monitoring: behavior for runs started by that schedule
- channel --profile ops: behavior for sessions started from inbound Slack/Telegram/Discord messages
- notification --target "#ops": where schedule notifications are sent; it does not choose the model or tools

Notification routing uses two words everywhere:

- channel: the transport, such as slack, telegram, or discord
- target: the destination inside that transport, such as Slack #ops or C1234567890

autopilot channel add ... --target sets the default notification route. Schedules inherit it unless you add --notify-target or --notify-channel.

Check the docs
Just run stakpak and follow the instructions which will create a new API key for you.

> Brave users may encounter issues with automatic redirects to localhost ports during the API key creation flow. If this happens to you:

>

> Copy your new key from the browser paste it in your terminal

Create ~/.stakpak/config.toml with one of these configurations:

Option 1: Bring Your Own Keys (BYOK) - Use your Anthropic/OpenAI API keys:

stakpak mcp proxy

stakpak mcp proxy --config-file ~/.stakpak/mcp.toml

External MCP servers are configured in mcp.toml (or mcp.json) and loaded by stakpak mcp proxy.

Config file discovery order:

1. ~/.stakpak/mcp.toml or ~/.stakpak/mcp.json
2. .stakpak/mcp.toml or .stakpak/mcp.json (from current directory)
3. ./mcp.toml or ./mcp.json

Add servers via CLI:

stakpak mcp add internal-tools --command npx --args "-y,@acme/internal-mcp" --env "MCP_API_KEY=<token>" --env "MCP_REGION=us-east-1"
stakpak mcp proxy

Or define servers directly in ~/.stakpak/mcp.toml:

[mcpServers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp"]
env = { MCP_API_KEY = "<token>", MCP_REGION = "us-east-1" }
[mcpServers.github]

url = "https://api.githubcopilot.com/mcp"

headers = { Authorization = "Bearer <token>" }
[mcpServers.optional]

command = "npx"

args = ["-y", "some-mcp-server"]

disabled = true

Use disabled = true to keep a server configured without loading it.

1. Install Stakpak (if not already installed)
2. Configure Zed Editor - Add to ~/.config/zed/settings.json:

{
  "agent_servers": {
    "Stakpak": {
      "command": "stakpak",
      "args": ["acp"],
      "env": {}
    }
  }
}

3. Start ACP Agent:

stakpak acp

4. Use in Zed - Click Assistant (✨) → + → New stakpak thread

Your deployment procedures and guidelines here...
```