agent

:star: Help us reach more developers and grow the Stakpak community. Star this repo!

Try Stakpak Now

curl -sSL https://stakpak.dev/install.sh | sh # install Stakpak
stakpak init # understand your apps and tech stack
stakpak autopilot up # start the autonomous agent, running 24/7 in the background

For more installation options...

You can't trust most AI agents with your DevOps. One mistake, and your production is toast. Stakpak is built differently:

• Secret Substitution - The LLM works with your credentials without ever seeing them
• Warden Guardrails - Network-level policies block destructive operations before they run
• DevOps Playbooks Baked-in - Curated library of DevOps knowledge in Stakpak Rulebooks

Generate infrastructure code, debug Kubernetes, configure CI/CD, automate deployments, without giving an LLM the keys to production.

🤖 Autopilot (24/7 Autonomous Runtime)

Use the new lifecycle aliases for one-command setup/start/stop:

stakpak up        # alias for: stakpak autopilot up
stakpak down      # alias for: stakpak autopilot down

You can also use the canonical subcommands:

stakpak autopilot up
stakpak autopilot status
stakpak autopilot logs
stakpak autopilot down
stakpak autopilot doctor

Autopilot prerequisites

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

Unified configuration (profiles + autopilot wiring)

• ~/.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.

# default notification route: slack:#ops
stakpak autopilot channel add slack --bot-token "$SLACK_BOT_TOKEN" --app-token "$SLACK_APP_TOKEN" --profile ops --target "#ops"

# schedule runs with the monitoring profile and inherits the default route
stakpak autopilot schedule add health --cron '*/5 * * * *' --prompt 'Check health' --profile monitoring

# schedule still runs with monitoring, but notifies a different Slack target
stakpak autopilot schedule add deploy-watch --cron '*/15 * * * *' --prompt 'Watch deploys' --profile monitoring --notify-target "#deploys"

In ~/.stakpak/autopilot.toml, the same setup is represented as:

[notifications]
channel = "slack"
target = "#ops"

[[schedules]]
name = "health"
cron = "*/5 * * * *"
prompt = "Check health"
profile = "monitoring"

[[schedules]]
name = "deploy-watch"
cron = "*/15 * * * *"
prompt = "Watch deploys"
profile = "monitoring"
notify_target = "#deploys"

Slack public channel names such as #ops are accepted where Slack supports them. Channel IDs are most reliable for private channels, DMs, and scripts.

Full setup guide: cli/README.md

🔒 Security Hardened

• Mutual TLS (mTLS) - End-to-end encrypted MCP
• Dynamic Secret Substitution - AI can read/write/compare secrets without seeing actual values
• Secure Password Generation - Generate cryptographically secure passwords with configurable complexity
• Privacy Mode - Redacts sensitive data like IP addresses and AWS account IDs

🛠️ Built for DevOps Work

• Asynchronous Task Management - Run background commands like port forwarding and servers with proper tracking and cancellation
• Real-time Progress Streaming - Long-running processes (Docker builds, deployments) stream progress updates in real-time
• Infrastructure Code Indexing - Automatic local indexing and semantic search for Terraform, Kubernetes, Dockerfile, and GitHub Actions
• Documentation Research Agent - Built-in web search for technical documentation, cloud providers, and development frameworks
• Subagents - Specialized research agents for code exploration and sandboxed analysis with different tool access levels (enabled with --enable-subagents flag)
• Bulk Message Approval - Approve multiple tool calls at once for efficient workflow execution
• Reversible File Operations - All file modifications are automatically backed up with recovery capabilities

🧠 Adaptive Intelligence

• Rule Books - Customize agent behavior with internal standard operating procedures, playbooks, and organizational policies
• Persistent Knowledge - Agent learns from interactions, remembers incidents, resources, and environment details to adapt to your workflow

Installation

All installation options (Linux, MacOs, Windows)

Check the docs

Homebrew (Linux & MacOS)

brew tap stakpak/stakpak
brew install stakpak

To update it you can use

brew update
brew upgrade stakpak

Binary Release

Download the latest binary for your platform from our GitHub Releases.

Docker

This image includes the most popular CLI tools the agent might need for everyday DevOps tasks like docker, kubectl, aws cli, gcloud, azure cli, and more.

docker pull ghcr.io/stakpak/agent:latest

Usage

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

Option A: Running with a Stakpak API Key (no card required)

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

stakpak

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

Non-interactive setup (CI/scripts)

stakpak auth login --api-key $STAKPAK_API_KEY

Or set the environment variable

export STAKPAK_API_KEY=<mykey>

View current account (Optional)

stakpak account

Option B: Running Without a Stakpak API Key

Non-interactive setup (CI/scripts)

# Anthropic
stakpak auth login --provider anthropic --api-key $ANTHROPIC_API_KEY

# OpenAI
stakpak auth login --provider openai --api-key $OPENAI_API_KEY

# Gemini
stakpak auth login --provider gemini --api-key $GEMINI_API_KEY

Manual configuration

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

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

[profiles.byok]
provider = "local"

# Unified model preference field
model = "anthropic/claude-sonnet-4-5"

# Built-in providers - credentials can also be set via environment variables
# (ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY)
[profiles.byok.providers.anthropic]
type = "anthropic"
api_key = "sk-ant-..."

[profiles.byok.providers.openai]
type = "openai"
api_key = "sk-..."

[profiles.byok.providers.gemini]
type = "gemini"
api_key =