代码智能助手

deploy-staging

Run the test suite, build, then npm run deploy:staging. If the build fails, surface the error and stop — don't deploy a broken build. ```

The agent gets the bundle catalog injected into its system prompt on every iteration and can invoke any bundle via the invoke_skill tool:

• /skills bundles — list installed bundles
• /skills create-bundle <name> — scaffold a new project skill
• /skills show <name> — print the SKILL.md
• /skills browse [query] — search the public marketplace
• /skills install <owner>/<slug> — pull from marketplace
• /skills publish <name> [--public] — share to codeep.dev
• /skills unpublish <owner>/<slug> — remove your published skill

Web marketplace: publish skills to codeep.dev/skills as public (browseable by anyone) or private (only you). Manage your published skills at /dashboard/skills. From the VS Code extension, use the Codeep: Browse Skill Bundles… / Codeep: Create Skill Bundle… / Codeep: Open Skills Folder commands.

Installation

Setup

1. Install Codeep globally:

npm install -g codeep

1. Add to your Zed settings.json:

"agent_servers": {
  "Codeep": {
    "type": "custom",
    "command": "codeep",
    "args": ["acp"]
  }
}

1. Make sure your API key is set in the environment Zed uses:

export DEEPSEEK_API_KEY=your_key   # or whichever provider

1. Open Zed's AI panel and select Codeep as the agent.

Example for macOS Apple Silicon:

curl -fsSL https://github.com/VladoIvankovic/Codeep/releases/latest/download/codeep-macos-arm64 -o codeep chmod +x codeep sudo mv codeep /usr/local/bin/ ```

Quick Start

```bash

Usage Examples

maxIterations: 12 # optional budget

You write safe, reversible DB migrations… ```

tools is an allowlist enforced at dispatch (a researcher literally can't write files). Sub-agents inherit your profile + project rules, and their changes are covered by /undo.

Guaranteed review: enable Agent Auto-Review in /settings (agentAutoReview) and after any run that changes files, Codeep automatically delegates to the reviewer and appends its findings — a review stage that always happens. Off by default.

Optional Codeep-specific extensions:

codeep-min-version: 2.0.0 codeep-requires-mcp: [postgres] allowed-tools: [read_file, write_file, execute_command]

Self-Verification (Optional)

When enabled in Settings, the agent can automatically verify its changes by running build, tests, or type checking after completing a task. Disabled by default — the agent works freely and you decide when to verify.

Configure in Settings → Agent Auto-Verify: - Off (default) — no automatic verification - Build only — checks compilation after changes - Typecheck only — runs TypeScript/PHP type checking - Test only — runs test suite after changes - Build + Typecheck + Test — full verification

If errors are found, the agent tries to fix them automatically (up to 3 attempts, configurable).

Supported project types:

Personal config sync

account sync / account push also carry your personalities and custom slash commands between machines — the Markdown files in ~/.codeep/personalities/ and ~/.codeep/commands/:

codeep account push   # Upload local personalities + commands to codeep.dev
codeep account sync   # Download them onto a new machine

Merging is additive — sync only writes files that don't already exist locally, so it never clobbers a personality or command you've edited on this machine. View what's synced (and prune stale entries) under Personalities and Custom commands on the dashboard.

Hooks and MCP server configs are deliberately not synced: hooks run arbitrary shell, and MCP configs often embed tokens, so both stay local to each machine.

Option 1: curl (Quickest)

curl -fsSL https://raw.githubusercontent.com/VladoIvankovic/Codeep/main/install.sh | bash

Custom installation directory:

curl -fsSL https://raw.githubusercontent.com/VladoIvankovic/Codeep/main/install.sh | INSTALL_DIR=~/.local/bin bash

Specific version:

curl -fsSL https://raw.githubusercontent.com/VladoIvankovic/Codeep/main/install.sh | VERSION=1.0.0 bash

Option 2: Homebrew (macOS/Linux)

brew tap VladoIvankovic/codeep
brew install codeep

Update:

brew upgrade codeep

Option 3: npm

npm install -g codeep

Update:

npm update -g codeep

Option 4: Manual Binary

Download the latest binary for your platform from GitHub Releases:

```bash

AI Configuration

Model favorites — save provider+model combos and switch instantly:

> /provider      # switch to z.ai
> /model glm-5.1
> /profile save fast

> /provider      # switch to openai
> /model gpt-4.1
> /profile save work

> /model fast    # instantly switch to z.ai / glm-5.1
> /model work    # instantly switch to openai / gpt-4.1

Configuration

Config Locations

Environment Variables

Settings (`/settings`)

API key sync

Add keys once on the dashboard, then sync them to any machine:

codeep account sync   # Pull keys + config from codeep.dev → local
codeep account push   # Push local keys + config → codeep.dev

Keys are encrypted at rest using AES-256-GCM.

On first run, enter your API key

Loading CLI sessions in Zed

Zed's left sidebar shows only sessions Zed itself created (one per "New Thread") — it does not auto-list sessions you saved from the CLI or from a previous Zed window. Two ways to access those:

Inside the chat (recommended):

/sessions                    # show all saved sessions for this workspace
/session load <name>         # restore one

When you open a fresh chat in Zed, Codeep also shows you the most recent CLI sessions for that project right in the welcome message, so you can switch with one command.

Via Zed's import modal:

Open Zed's command palette (Cmd+Shift+P) and search for "Import Threads". Codeep's saved sessions appear there as an importable list — once imported they show up in Zed's regular sidebar.

Git Integration

• /diff - Review unstaged changes with AI assistance
• /diff --staged - Review staged changes
• /commit - Generate conventional commit messages

Git Integration

Zed Editor Integration (ACP)

Codeep supports the Agent Client Protocol (ACP), letting you use it as an AI coding agent directly inside Zed.

Native chat & agent integration (new in 2.3)

• @codeep chat participant — invoke Codeep from VS Code's built-in Chat view: type @codeep and ask, or @codeep /explain / @codeep /review with a selection. Answers come from your configured Codeep provider/model via the CLI (not VS Code's model picker), on an independent session.
• #codeepSkills language-model tool — exposes your workspace's Codeep skill bundles (.codeep/skills/*/SKILL.md) to VS Code agent mode and #-references, so the native a

Configurable permissions (Zed & VS Code extension)

Via the agent settings panel you can toggle which tools ask for approval before running — same controls available in the TUI via /settings:

• Confirm: delete_file — ON by default
• Confirm: execute_command — ON by default
• Confirm: write_file / edit_file — OFF by default

These apply in Dangerous confirmation mode (the default). Choose Always to confirm every action, or Never to skip all prompts.

VS Code Extension

Install Codeep from the VS Code marketplace. The extension is a thin UI around the CLI — all credentials and sessions live in the CLI's config (~/.config/codeep/config.json), so keys set anywhere are visible everywhere.

Set API keys without leaving VS Code

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run:

• Codeep: Set API Key — pick a provider, paste the key, done. Writes into the CLI config, so running codeep in a terminal immediately sees the new key.
• Codeep: Open Chat — open the Codeep sidebar.
• Codeep: Review Current File — run /review <file> on the active editor.
• Codeep: New Session — start a fresh session in the chat.

If you already set up keys in the CLI (or via the codeep.dev dashboard + codeep account sync), the extension picks them up automatically on first launch — no welcome prompt.