CLI Commands
archcore init
Section titled “archcore init”Initialize .archcore/ in the current directory.
archcore initWhat it does:
- Creates
.archcore/directory withsettings.json - Auto-detects installed coding agents
- Installs MCP server config for detected agents
- Installs session hooks for supported agents
If no agents are detected, falls back to Claude Code configuration.
archcore validate
Section titled “archcore validate”Validate .archcore/ structure and documents.
archcore validate [--fix]Checks performed:
- Directory structure exists
- File naming follows
<slug>.<type>.mdpattern - Slugs are lowercase alphanumeric with hyphens only
- Document types are valid (one of the 10 types)
- YAML frontmatter has required
titleandstatusfields - Frontmatter is valid YAML
- Sync manifest JSON structure
- Orphaned relations (documents referenced but not on disk)
Flags:
| Flag | Description |
|---|---|
--fix | Auto-remove orphaned relations and save manifest |
archcore doctor
Section titled “archcore doctor”Comprehensive health check.
archcore doctorRuns all validation checks plus:
- Verifies
settings.jsonexists and is valid - Checks server reachability (if server URL is configured)
archcore config
Section titled “archcore config”Manage configuration.
archcore config # Show current sync typearchcore config get <key> # Read a config valuearchcore config set <key> <value> # Set a config valueAvailable keys:
| Key | Values | Description |
|---|---|---|
sync | none, cloud, on-prem | Sync type (currently locked) |
project_id | integer | Project ID for sync (currently locked) |
archcore_url | URL | Server URL for on-prem (currently locked) |
language | language code | Language for document content (e.g., en, ru) |
Examples:
archcore config set language ruarchcore config get languagearchcore mcp
Section titled “archcore mcp”Run the MCP server or install MCP config.
archcore mcp # Start stdio MCP serverarchcore mcp install # Install MCP config for all detected agentsarchcore mcp install --agent <id> # Install for a specific agentThe archcore mcp command starts a stdio MCP server that coding agents connect to. It’s not meant to be run manually — agents launch it as a subprocess.
Agent IDs: claude-code, cursor, copilot, gemini-cli, opencode, codex-cli, roo-code, cline
archcore hooks
Section titled “archcore hooks”Manage agent hooks.
archcore hooks install # Install hooks for all detected agentsarchcore hooks install --agent <id> # Install for a specific agentAgent hook commands (called by agents, not manually):
archcore hooks claude-code session-startarchcore hooks cursor <event>archcore hooks gemini-cli <event>archcore hooks copilot <event>archcore update
Section titled “archcore update”Check for and install the latest version.
archcore updateQueries GitHub releases, compares versions, downloads the binary for your OS/architecture, verifies the checksum, and updates in place.
archcore —version
Section titled “archcore —version”Display the current version.
archcore --versionarchcore —help
Section titled “archcore —help”Show help with all available commands.
archcore --help