arthai-marketplace

/memory-setup

Configure arth-memory — the org decision/memory layer for AI agents. Choose Cloud (talk directly to your org’s deployed server — zero local infra, best for trying it / team testing), Local (Docker store on this machine), or Global (offline replica of a central AWS/GCP server), then register the MCP server. Opt-in.

Test the org memory in ~1 minute (Cloud)

The fastest way to evaluate arth-memory — no Docker, no Ollama, nothing to run locally:

/memory-setup        # choose "Cloud" → paste your org's server URL (e.g. the ALB) → done

Then open a new session and ask an agent to do a task in a repo your org has seeded — it pulls the org’s decisions/constraints via compile_context automatically. Or browse the dashboard at <server-url>/dashboard. Behind the scenes this registers the arth-memory-mcp-remote bridge, which calls the deployed REST API over HTTP.

To share with teammates: send them your toolkit branch + the server URL. They run /memory-setup → Cloud → paste the URL. That’s it.

Synopsis

/memory-setup

When to use it

• First-time setup: you want your coding agents to recall your team’s Decisions, Constraints, and Facts (the “why”) and have rule violations flagged at coding time
• Switching a machine from a standalone Local store to a shared Global (central) one, or vice versa
• Re-pointing at a different central server, or verifying an existing config still works
• Not for: running /calibrate itself — /memory-setup just configures where knowledge is stored and synced; /calibrate fills it

Quickstart

/memory-setup

Pick Cloud to test your org’s deployed server instantly (no local infra), Local to run an offline Docker store, or Global to replicate the central server offline. Then run /calibrate.

Examples

/memory-setup        # the only form — the skill is interactive

Typical runs:

• First time, solo/offline → choose Local → a Docker FalkorDB store starts, the MCP server is registered, the store is created at ~/.arthai/memory
• Joining an org with a central server → choose Global → provide the server URL + your reader token → an offline replica syncs down (gated at 1 GB)
• Already configured → re-run → it offers to reconfigure, or just re-verifies your existing setup

What it does

/memory-setup is fully opt-in and additive — if you never run it, the toolkit behaves exactly as today (no memory MCP server, no container).

1. Installs the arth-memory CLI if it isn’t already on your PATH.
2. Asks how to connect — a user-confirmation checkpoint:
   • Cloud — talk directly to your org’s deployed server over HTTP (no Docker/Ollama/store). You provide its URL (+ optional reader token). Fastest to try / test.
   • Local — a Docker FalkorDB store on this machine + native Ollama. Fully offline, ~$0.
   • Global — an offline replica synced from your org’s central AWS/GCP server (you provide its URL + a reader token).
3. Asks where the local knowledge store lives (default ~/.arthai/memory). Knowledge is more than one repo — KB/KG for every repo you work on lives in this one store, and each repo points at it via gitignored symlinks (.claude/knowledge → store). Knowledge is never committed per-repo.
4. Registers the arth-memory MCP server in .claude/settings.local.json (so agents get compile_context, constraint_check, write).
5. Runs an initial 1 GB-gated sync: under 1 GB → downloads everything into the store; larger orgs defer to selective sync (a later milestone).

Output & artifacts

• ~/.arthai/memory-configured — marker (cloud

  local

  remote)

• ~/.arthai/config.json — { mode, memory_dir? , api_url? } (read by the toolkit lib + context hook)
• A running store: none for Cloud (direct API); arth-memory-falkordb Docker container (Local) or arth-memory-replica (Global)
• <repo>/.claude/settings.local.json — the arth-memory MCP server block (git-ignored; reader token only)
• <repo>/.claude/{knowledge,project-profile.md,okf} — gitignored symlinks into the store

Troubleshooting

• arth-memory CLI not found after install — open a new shell so PATH updates, then re-run.
• Local: Docker not running — start Docker Desktop and re-run; the store container needs it.
• Local: recall is keyword-only — native Ollama isn’t reachable; install it and pull nomic-embed-text, then re-sync.
• Global: 401 — your reader token is wrong or expired; get a fresh one from your admin.
• Global: total_live: 0 — the central store itself is empty; an admin needs to seed it (org build / first calibrate).
• Nothing changed in a repo — /memory-setup configures the machine; run /calibrate in the repo to populate/hydrate.

Related

• /calibrate — establishes the store, emits an OKF bundle, and (when memory is configured) pushes generated knowledge up / hydrates it down
• /implement, /planning, /qa — automatically read the memory store as context (injected by the toolkit’s context hook)
• /otel-setup — the sibling opt-in configuration skill (observability)