Choose Plugin or CLI

Archcore has two entry points. Both read and write the same .archcore/ directory, but they meet you at different levels.

The short answer

• Using Claude Code, Cursor, or Codex CLI? Start with the Plugin. You get skills, tracks, built-in agents, and guardrails without extra wiring. (Codex CLI also has a CLI-only fallback if you’d rather not enable the plugin’s plugin_hooks feature flag.)
• Using any other agent (Copilot, Gemini CLI, OpenCode, Roo Code, Cline), or scripting in CI? Use the CLI directly.
• Just want to understand the model first? Read the shared concepts.

Pick your path

Best for most teams

Plugin

Use Archcore through a higher-level plugin in Claude Code or Cursor. Skills, tracks, built-in agents, and guardrails out of the box.

Plugin quick start →

Best for direct integrations

CLI

Use Archcore as a core context layer through the CLI, MCP server, and session hooks. Works with 8 coding agents.

CLI quick start →

Understand the model

Concepts

Document types, relations, layout, and why Archcore exists. The shared mental model that both paths build on.

Read concepts →

How they compare

	Plugin	CLI
Install method	Install CLI globally, then add the plugin from the marketplace	Single binary via curl / PowerShell
CLI prerequisite	Required (same one-line installer as standalone CLI)	Required
Hosts	Claude Code, Cursor, Codex CLI (Copilot planned)	All 8 supported agents
Interface	7 slash commands (/archcore:init, /archcore:context, /archcore:capture, /archcore:plan, /archcore:decide, /archcore:audit, /archcore:help)	MCP tools + natural language
Multi-step workflows	/archcore:plan --track and /archcore:decide continuations orchestrate document chains automatically	You drive them manually through MCP
Guardrails	MCP-only writes, post-mutation validate, cascade warnings	MCP available; guardrails are opt-in via hooks
Best for	Day-to-day use inside Claude Code or Cursor	Scripting, CI, agents without plugin support

Both paths share the same .archcore/ directory and the same MCP server backed by the globally-installed archcore binary. Switching paths — or using both at once — requires no migration.

The mental model

• CLI is the compiler. It reads .archcore/, builds the graph, speaks MCP.
• Plugin is the runtime. It applies that graph inside Claude Code, Cursor, and Codex CLI — skills, hooks, workflows.

More depth in Mental Model.

Next steps

• Plugin quick start — install the plugin in Claude Code, Cursor, or Codex CLI.
• CLI quick start — install the CLI and create your first document.
• What is Archcore? — the problem, the solution, and the shared mental model.