Skip to content

Platforms and agents

Agents Pack installs as a standalone executable and targets Claude Code, Codex, and Cursor. Support differs by machine platform and by installation scope.

The public installer supports:

Platform Architectures
macOS 13 or newer Apple Silicon (ARM64), Intel (x64)
Linux with glibc ARM64, x64

The installer:

  1. reads the Agents Pack CLI registry
  2. selects the matching macOS or Linux release
  3. downloads the archive and checksum file
  4. verifies the SHA-256 checksum
  5. checks the archive layout and starts the downloaded executable
  6. installs atomically at ~/.local/bin/agents-pack (or AGENTS_PACK_INSTALL_DIR)

It does not use sudo. Bun, Node.js, and npm are not required for the installed binary.

Override install location or version with environment variables. See Install the CLI.

Select agents with --agents on init:

Value Meaning
claude Claude Code
codex Codex
cursor Cursor
all Shorthand for claude,codex,cursor (non-interactive)

Pass a comma-separated list, for example --agents claude,codex.

Agent Repository scope Global scope
Claude Code Supported Supported
Codex Supported Supported
Cursor Supported Not supported

Global Cursor instructions are not supported yet. Selecting Cursor with --scope global stops before writing anything. Use Cursor in repository scope, or initialize global scope for Claude Code and Codex only.

Interactive init prevents incompatible global Cursor selection. Repository scope, all compatible agents, and recommended components are the interactive defaults.

Agents Pack renders provider-native files. Repository examples include:

.claude/rules/agents-pack/
.claude/skills/
.claude/agents/
AGENTS.md
.agents/skills/
.codex/agents/
.cursor/rules/agents-pack/
.cursor/skills/
.cursor/agents/

The exact skill copies depend on the selected agent combination. Agents Pack may reuse Claude or Codex compatibility roots for Cursor instead of creating a third identical copy. See File layout.

The lifecycle supports one active Agents Pack scope at a time. Installing both global and the current repository causes a scope conflict. Prefer repository scope when unsure; it is easier to inspect, commit, and remove without affecting unrelated projects. See Repository vs global.