arcanon

Arcanon

Cross-repo service dependency scanner for Claude Code. Map your architecture, detect drift, and sync to Arcanon Hub — all from inside your editor.

Arcanon is a Claude Code plugin that discovers services, endpoints, connections, and schemas across all your repositories, then helps you reason about cross-repo impact before you merge. The plugin works fully offline; when connected to Arcanon Hub, findings sync to a cloud service graph that powers org-wide drift detection and impact analysis.

---

Why Arcanon?

Most dependency tools stop at package.json and Cargo.toml. Arcanon traces the runtime graph — the HTTP calls, gRPC streams, message-bus topics, and shared schemas that actually couple your services together — across repository boundaries.

Pillar	What it means
Discover	Agents walk each repo, emit a structured JSON findings file.
Reconcile	Findings are stitched into a single cross-repo graph in local SQLite.
Detect drift	Compare a live scan against the last uploaded snapshot from the hub.
Sync to hub	Upload findings to api.arcanon.dev so your team, CI, and other repos can query them.

Quick start

# 1. Install the plugin marketplace (one-time)
claude plugin marketplace add https://github.com/Arcanon-hub/arcanon
claude plugin install arcanon@arcanon --scope user

# 2. In your repo, run your first scan
/arcanon:map

# 3. (Optional) Connect to Arcanon Hub
/arcanon:login            # paste your arc_... API key
/arcanon:status           # check sync state + queue

Full walkthroughs live in docs/getting-started.md.

Commands

Every /arcanon:* command supports --help, -h, or help.

Scanning & graph

Command	What it does
/arcanon:map [view|full]	Scan repos, build or refresh the local service graph.
/arcanon:rescan <repo>	Re-scan exactly one linked repo, bypassing the incremental skip.
/arcanon:shadow-scan	Scan into a sandbox shadow DB; live DB is byte-untouched.
/arcanon:export	Emit Mermaid / DOT / JSON / self-contained HTML from the latest scan.

Read-only navigation

Command	What it does
/arcanon:list	5-line project overview — repos, services, connections, actors, hub.
/arcanon:view	Open the graph UI in your browser.
/arcanon:doctor	8-check smoke-test diagnostics with structured exit codes.
/arcanon:diff <scanA> <scanB>	Compare two scans (int IDs, HEAD/HEAD~N, ISO, branches; --shadow mode).

Corrections & verification

Command	What it does
/arcanon:correct <kind> --action ...	Stage a scan_overrides row consumed on the next scan.
/arcanon:verify	Re-read source at cited line ranges; flag drifted connections.
/arcanon:promote-shadow	Atomically swap the shadow DB into live with a timestamped backup.

Cross-repo intelligence

Command	What it does
/arcanon:impact <target>	Query cross-repo consumers of a service / endpoint / schema.
/arcanon:drift [graph|versions|types|openapi]	Detect drift across repos (8 ecosystems for versions).

Hub sync

Command	What it does
/arcanon:login	Store your Arcanon Hub API key.
/arcanon:sync	Upload current repo's scan, then drain the offline queue (--offline, --repo, --dry-run, --force, --drain).
/arcanon:status	Worker + hub + queue + per-repo scan freshness (commits-since-scan).

Maintenance

Command	What it does
/arcanon:update	Version check / worker kill / cache prune / verify.

See docs/commands.md for the full reference (flags, exit codes, examples).

Configuration

Arcanon reads arcanon.config.json from the repo root.

{
  "project-name": "my-project",
  "linked-repos": ["../sibling-service", "../shared-lib"],
  "hub": {
    "auto-sync": true,
    "url": "https://api.arcanon.dev"
  }
}

Hub credentials can live in the plugin's userConfig (preferred, stored in the system keychain), the ARCANON_API_KEY environment variable, or ~/.arcanon/config.json. See docs/hub-integration.md.

How it works