Peridot Agent

VS Code panel for Peridot Agent — a Rust CLI/TUI autonomous coding agent with multi-LLM committee mode, native tool calling, and 2-Tier context management.

Status: v0.6.0 brings the latest session, branch, runtime, MCP, notes, TODO, context, diff, replay, import/export, autocomplete, and session-context surfaces into the VS Code/Cursor extension. The sidebar includes onboarding, queued prompts, persistent chat sessions, Markdown answers, single-line tool activity (with risk-class chip colouring), approval/diff cards, usage/budget HUD, an inline plan panel, a compact context donut, daemon-backed slash commands, and a structured /branch picker.

Commands

First run

The extension contributes a Get Started with Peridot walkthrough in VS Code's welcome flow. It links the same surfaces used day to day: open the Peridot sidebar, connect a provider, review workspace settings, then run a first task.

When you open the Peridot Activity Bar with no provider configured, you land on a three-button onboarding screen:

• Sign in with ChatGPT — OAuth via your ChatGPT account (peridot login openai-oauth under the hood).
• OpenRouter API key — one key, 75+ models. Stored in Peridot's local env store, never your shell rc.
• Local LLM endpoint — point at any OpenAI-compatible HTTP API (Ollama, LM Studio, vLLM, …).

Already configured? The session view opens directly. Use the "Switch provider" button in the session header to come back.

Sidebar

Once a provider is live, the sidebar shows workspace / provider / model / auth context, AGENTS/MCP/code-map/attachment/note status, a session dropdown, a HUD for token usage and cost / turn budget, an inline plan panel that follows plan_updated, a compact context donut in the composer options row, a chat-style Markdown transcript with single-line tool activity and inline unified diffs, plus approve/deny controls with a diff preview for file_write / file_patch. The slash picker loads the same command catalog exposed by the TUI through the daemon session.command_catalog RPC, and supported session-control slashes run through session.command so mode, permission, model, provider, committee, note, compact, branch, MCP, TODO, codemap, info, cost, plan show, goal control, session save, session count, session rename/delete, rewind, export, diff, undo, and context results stay aligned with the daemon. Typing /branch opens a picker backed by the current context turns; selecting a row runs /branch turn <id>. The session header also exposes artifact export for the active session's attachments, notes, and replay timeline.

Type at the composer — Enter sends, Shift+Enter inserts a newline. Sending while a task is in flight queues the message; the queue UI lets you edit, remove, or clear individual entries before they auto-run. Follow-up prompts continue the active session until you run /clear or open a new session from the dropdown. Typing @ at a token boundary opens a workspace file picker. Tab or click inserts the selected @path/to/file mention as a navigation hint for the model; the extension does not inline file contents automatically.

Configuration

Cursor remote install workaround

Some Cursor remote-server builds fail while updating Marketplace extensions whose VSIX response is transported with Content-Encoding: gzip. The Marketplace package is valid after HTTP decoding, but Cursor may cache the gzip transport body and then try to open it as a ZIP, reporting:

End of central directory record signature not found. Either not a zip file, or file is truncated.

Install the decoded VSIX directly on the remote host:

cd extensions/vscode
bash scripts/install-cursor-remote.sh 0.6.0

Or run the same workaround without a checkout:

curl -fsSL https://raw.githubusercontent.com/dlsxj101/peridot-agent/main/extensions/vscode/scripts/install-cursor-remote.sh \
  | bash -s -- 0.6.0

The script downloads the Marketplace VSIX with curl --compressed, validates that the saved file is a decoded ZIP/VSIX, and installs it via the newest ~/.cursor-server/.../cursor-server binary. Reload Cursor after it prints the successful install message.

Local development

Sideloading a .vsix you packaged yourself? npm run package produces a universal build and runs the extension unit tests through VSCE's vscode:prepublish hook. Unless you stage binaries under resources/bin/<target>/ first, Peridot falls back to peridot on your PATH. To exercise a single-platform bundled-binary path locally:

cargo build --release -p peridot-cli
cd extensions/vscode
npm run bundle-binary       # copies target/release/peridot into resources/
npm run package             # .vsix now contains the binary

For WSL/Cursor extension development, install extension dependencies first:

cd extensions/vscode
npm install
npm test

Then use the VS Code/Cursor launch configuration Peridot: Run Extension with bundled CLI. Its prelaunch task typechecks the extension, builds the release peridot-cli, copies the binary into extensions/vscode/resources/, and smoke-checks the bundled CLI with resources/peridot --version before opening the Extension Development Host.

resources/peridot, resources/peridot.exe, and resources/bin/ are gitignored so local binary copies never land on main. The release pipeline drops platform-specific binaries into resources/peridot[.exe] for target packages and into resources/bin/<target>/ for the universal fallback package.

Release

Extension releases use vsce/v<version> tags so they do not collide with Rust CLI v* releases. Before publishing, update extensions/vscode/package.json, then push a matching tag:

git tag vsce/v0.6.0
git push origin vsce/v0.6.0

The release workflow verifies that the tag matches the extension package version, builds six bundled CLI binaries, publishes platform-specific VSIX packages to VS Code Marketplace and Open VSX, publishes the universal fallback VSIX, and attaches all VSIX assets to the GitHub Release. The workflow requires VSCE_PAT and OVSX_PAT repository secrets.

Roadmap

• v0.5.0 — ✅ Bundled peridot binary for six targets, sidebar webview split into its own esbuild bundle, HUD panel for usage / budget / context, inline plan panel, inline unified-diff cards, pre-approval diff preview for file_write / file_patch, and cached / reused-daemon status reads.
• v0.6.0 — ✅ Hardened extension internals: daemon JSON-RPC per-request timeouts and graceful→forced shutdown, leak-free run lifecycle with strict approval routing, validated webview/persisted inputs, and the host entry point split into focused commands/ modules.
• v0.5.21 — ✅ VS Code/Cursor parity for persisted-session management, branch workflows, runtime controls, MCP management, notes, TODOs, context/diff, replay, import/export, shared slash autocomplete, session usage/context metadata, and quieter recovery output.
• v0.5.20 — ✅ agent_ask_user single-select and multi-select prompts include an Other free-form answer in the sidebar; long tasks show live and final elapsed time in a bottom footer.
• v0.5.19 — ✅ Request-context donut breakdown matching the next daemon/provider request, routine phase events hidden from the transcript, user-facing checking phase wording, and tool-result mutation markers.
• v0.5.18 — ✅ Editor-area settings webview (form for .peridot/config.toml), Hermes-style /skill-name slash skill invocation, daemon peridot.handshake schema-version check, routine phase-transition filtering for a quieter transcript, risk-class chip colours on tool rows, and an LLM-authored session title with "No title" fallback.
• v0.6.x+ — ✅ Settings webview polish, Hermes-style skill directories, skill pin/archive/restore/detail/search surfaces, daemon-backed session/slash parity, attachment inventory/lifecycle, session artifact export, stale worktree/session reconciliation, and shared autocomplete/help metadata across TUI and VS Code.

Source

Extension source lives at github.com/dlsxj101/peridot-agent/tree/main/extensions/vscode. The Rust agent core is in the same repository under crates/.