Choose Plugin or CLI

Archcore has two entry points: the plugin and the CLI. Both read and write the same .archcore/ directory. The plugin wraps the CLI in slash commands and guardrails; the CLI gives you the MCP tools directly.

The short answer

• Using Claude Code, Cursor, Codex CLI, or GitHub Copilot CLI? Start with the Plugin. You get skills, guided plan flows, built-in agents, and guardrails. (Codex CLI also has a CLI-only fallback if you’d rather not enable Codex’s hooks feature.)
• Using any other agent (Gemini CLI, OpenCode, Roo Code, Cline), or scripting in CI? Use the CLI directly.
• 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, GitHub Copilot CLI	All 8 supported agents
Interface	4 slash commands (/archcore:init, /archcore:plan, /archcore:document, /archcore:review)	MCP tools + natural language
Multi-step tracks	/archcore:plan tracks and /archcore:document cascades 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 a supported host	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. You can switch paths, or use both at once, without migrating anything.

The mental model

• CLI is the engine. It reads .archcore/, builds the graph, speaks MCP.
• Plugin is the runtime on top of it. It applies that graph inside Claude Code, Cursor, Codex CLI, and GitHub Copilot CLI through skills, slash commands, gated tracks, and hooks.

More depth in Mental Model.

Next steps

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