Archcore CLI

The command-line tool for Archcore. It sets up project context and connects your coding agents through MCP and supported hooks.

Install CLI

Install the CLI, then run archcore init in your project folder.

curl -fsSL https://archcore.ai/install.sh | bash

archcore init

archcore-ai/cli·CLI docs

What the CLI does

Run archcore init in your repository, then choose the agents you use.

Create the context directory. archcore init creates .archcore/ for project documents and configuration.
Connect your agents. Choose the agents to configure. The CLI writes their MCP configuration and installs hooks where supported.
Add the plugin where available. For selected plugin hosts, init also installs the plugin. Cursor requires installation through its Plugins panel.

Connect the agents your team uses

All eight agents below can read the same project documents through MCP. Hook support varies by host.

Claude Code · Cursor · Gemini CLI: MCP and session hooks.
Codex CLI: MCP and hooks. Check your Codex version, trust the project, and approve hooks before relying on them.
GitHub Copilot CLI: MCP and session hooks. Pre-write context injection is not available.
OpenCode · Roo Code: MCP configuration through the CLI.
Cline: Manual MCP configuration.

Per-agent setup ↗See what the plugin adds →

Project documents you can review in Git

Documents are Markdown files with YAML frontmatter. You choose their folders; each agent keeps its own MCP configuration.

Example project documents

.archcore/
├─ auth/
│  ├─ rate-limits.adr.md
│  └─ api-errors.rule.md
└─ release-checklist.guide.md

Keep the instructions you already use

Keep CLAUDE.md, AGENTS.md, .cursor/rules, and docs/. Ask your agent to turn a useful section into an Archcore document, then review the result.

“Turn the database decision in CLAUDE.md into an Archcore ADR.”

Migration guide ↗What is repo memory? →

CLI FAQ

What does archcore init create?

It creates .archcore/ and configures the agents you select. Project documents are created through MCP or with the plugin's skills.

Which AI agents does the CLI support?

Claude Code, Cursor, Codex CLI, GitHub Copilot CLI, Gemini CLI, OpenCode, Roo Code, and Cline. Cline needs manual MCP setup. Hook support differs by host; see the agent list above.

Do I need any external services?

Archcore stores project documents locally and runs an MCP server on your machine. It needs no hosted Archcore backend. Your coding agent's own provider and data settings still apply.

What does the plugin add?

The plugin adds skills for setup, planning, documentation, and review on Claude Code, Cursor, Codex CLI, and GitHub Copilot CLI. It uses the same CLI and project documents. Other MCP agents use the CLI directly.