cookie agent

cookie agent is a subagent-first coding harness. A local daemon owns provider connections, sessions, model execution, permissions, and persistence; the terminal UI communicates with it over the versioned JSON-RPC protocol.

Session history uses versionless events with best-effort reading; other persisted and wire surfaces remain current-only. Architecture describes how the pieces fit together; this site turns that implementation into task-oriented guides and reference material.

Quickstart

First install cookie agent, then run it from the workspace where it should operate:

cookie

No configuration file is needed to start. If no provider is available, the TUI opens in setup mode; type /connect to store a managed provider connection. Provider setup and credentials are per-user and shared across workspaces. Credentials are checked when the provider is first used, not during the connect flow.

The installation guide ends with provider setup; Run covers interactive and headless operation. See Providers for managed and custom provider options, Plugins for executable extensions, and Configuration for every configurable item.

Keep credentials out of Git

Prefer /connect or ${env:NAME} interpolation. Do not commit .env, a credential-bearing config, or provider-store data.

Development

See Building and testing for the Rust toolchain and required gates, Plugin development for extension authoring, and the Rust API documentation for public workspace interfaces.