Skip to main content

Agents

Codex, Claude Code, and Cursor are first-class, equally-supported agents in STAK — none is a primary integration with the others bolted on. Each section below covers the same four things for its agent: Skill projection, normal run, isolated try, and authentication.

Codex

Skill projection/binding

stak run codex reconciles main into Codex's Skill directory, protecting unmanaged content and removing only healthy STAK-owned bindings.

Normal run

Launches the Codex CLI (codex on your PATH) with the reconciled Skills projected — not the ChatGPT desktop app.

stak run codex

Isolated try

Runs Codex in a temporary CODEX_HOME; main and your normal Codex bindings are untouched and the trial runtime is cleaned up afterward.

stak try @owner/name -- codex

Authentication expectations

Codex's own CLI handles its sign-in; STAK only reconciles Skills and launches it, so sign in to Codex the same way you would outside STAK.

Claude Code

Skill projection/binding

stak run claude reconciles main into Claude Code's Skill directory, protecting unmanaged content and removing only healthy STAK-owned bindings.

Normal run

Launches the Claude Code CLI with the reconciled Skills projected.

stak run claude

Isolated try

Runs Claude Code in a temporary CLAUDE_CONFIG_DIR; main and your normal Claude Code bindings are untouched and the trial runtime is cleaned up afterward.

stak try @owner/name -- claude

Authentication expectations

Claude Code's own CLI handles its sign-in; STAK only reconciles Skills and launches it, so sign in to Claude Code the same way you would outside STAK.

Cursor

Skill projection/binding

stak run cursor reconciles main into Cursor's Skill directory, protecting unmanaged content and removing only healthy STAK-owned bindings. The official Cursor Agent CLI may be invoked as agent.

Normal run

Launches Cursor's agent CLI with the reconciled Skills projected.

stak run cursor

Isolated try

Runs Cursor in a temporary CURSOR_CONFIG_DIR; main and your normal Cursor bindings are untouched and the trial runtime is cleaned up afterward.

stak try @owner/name -- cursor

Authentication expectations

Isolated trials support a normal agent login session — if you're already signed in to Cursor that way, it's detected and reused automatically, no extra setup needed. You do not need to configure CURSOR_API_KEY to use STAK with Cursor; it's only an optional alternative, available as CURSOR_API_KEY or CURSOR_AUTH_TOKEN, for environments without an interactive agent login session.

See CLI Reference for every flag on run and try, and Workflows for the full task sequences these commands fit into.