arthai-marketplace

/arth-setup

Availability: Local is GA for every layer. Per-layer cloud endpoints (telemetry ingest at ingest.getarth.ai, your org’s own arth-memory server) work today; the unified Arth Cloud sign-in (one login for intelligence + memory + router + orchestrate) is pre-GA, /arth-setup says so when you pick cloud.

Set up the whole Arth stack in one command: intelligence (/otel-setup), memory (/memory-setup), and router (/router-setup) behind a single umbrella. Local: pick any subset, zero login. Cloud: sign in once (Google or email SSO) and get all three + orchestrate as one product. Also handles switch and uninstall; both are reversible and never touch data.

Synopsis

/arth-setup
/arth-setup switch <local|cloud|off> [intelligence|memory|router|all]
/arth-setup uninstall [intelligence|memory|router|all] [--purge-data]

When to use it

• You want the whole Arth stack (or any subset of it) set up in one sitting instead of running three setup skills by hand
• You’re switching posture, local ↔ cloud ↔ off, for one product or all of them (env rewrite only; data untouched)
• You’re removing one or more products and want the removal to be surgical: exactly what setup created, nothing else, data volumes preserved
• Not for: configuring a single product with its full option set, go straight to /otel-setup, /memory-setup, or /router-setup; the umbrella delegates to them anyway

Quickstart

/arth-setup

What you’ll see: a per-product state check, then one question, local or cloud? Local: pick any subset of intelligence / memory / router and each product’s own setup skill runs in sequence (no login anywhere, local services trust your machine). Cloud: one browser SSO sign-in wires all three + orchestrate together. Either way it ends with a combined health line: otel: arth ✓ (:4319) · memory: arth ✓ (local) · router: arth ✓ (:8600). Then open a new session, the env files it wrote load at session start.

Examples

/arth-setup                              # interactive — local/cloud, then (if local) pick a subset
/arth-setup switch off all               # back to the stock toolkit next session; data untouched
/arth-setup switch local router          # re-point just the router at localhost:8600
/arth-setup switch cloud all             # move every product to your org's Arth Cloud (needs ARTH_CLOUD_URL)
/arth-setup uninstall memory             # remove memory's env + MCP entry; prints the compose-down command
/arth-setup uninstall all --purge-data   # the only path that can delete data — typed confirmation required

Typical runs:

• First time, solo dev → local → tick memory (router is org-shaped , skip it solo, see the router guide) → /memory-setup runs with its own prompts → combined health line
• Trying cloud before your org has a deployment → cloud → clear message: “cloud posture requires an Arth Cloud deployment, coming at cloud GA; use local for now” (no cryptic failure)
• Leaving → switch off all → next session behaves exactly like a toolkit without Arth; containers and data still there if you come back

Arguments & flags

Argument	Values	Default	What it does
(none)	:	:	Interactive setup: local/cloud question, then (local) product subset
switch	local | cloud | off + optional product	product: all	Rewrites ONLY that product’s namespaced env file(s) and re-probes. Never migrates or deletes data. off removes the env files: next session is stock toolkit.
uninstall	optional product	product: all	Removes env files + the MCP registrations setup created, then prints the per-product compose-down command.
--purge-data	:	off	With uninstall only: additionally offers to delete data volumes: gated behind an explicit typed confirmation (purge <product>). Never implied.

What it does

1. Detects current state, probes each product independently (health endpoints, env files, markers) with short timeouts; a down service is reported, never an error.
2. Asks local or cloud, a user-confirmation checkpoint (always asked, never inferred).
3. Local path, a second user-confirmation checkpoint: a multi-select of intelligence / memory / router. Each chosen product’s existing setup skill then runs in sequence with its own prompts and confirmations, the umbrella delegates, it doesn’t reimplement. No login anywhere: local services bind localhost and trust the machine boundary.
4. Cloud path, no subset: cloud is the integrated product (all three + orchestrate, per-org). If ARTH_CLOUD_URL isn’t configured it stops with a clear “coming at cloud GA” message. If it is: one browser SSO flow (Google OAuth or email magic-link) issues one Arth JWT; the skill writes that one token to ~/.arthai/.env as ARTH_PLATFORM_TOKEN (the single value every Arth service reads, chmod 600) plus the remote URLs into the namespaced env files (confirmed before writing) and verifies all healths in one pass.
5. Switch / uninstall, reversible by construction: switch touches env files only; uninstall removes exactly what setup created and prints (never silently runs) the compose-down commands. Data volumes require --purge-data plus a typed confirmation.
6. Finishes with a combined health line per configured service, matching the session-briefing style, and reminds you to open a new session: the namespaced env files only load at session start, so the current session keeps stock behavior until you do.

Everything is fail-open: any product that’s absent or unhealthy simply falls back to today’s toolkit behavior (markdown KB, kg-query, static routing ladder) for that product only, the others keep working.

Output & artifacts

• Per-product namespaced env files: .claude/.arth-otel.env (intelligence), .claude/.arth-memory.env (memory), and the ARTH_ROUTER_URL key in ~/.claude/settings.json (router), the ONLY things switch rewrites
• Whatever the delegated skills produce (containers, markers, MCP entries) , see each product’s own page
• A combined health line: otel: arth ✓ · memory: arth ✓ · router: arth ✓
• On uninstall: the printed per-product compose-down commands (data volumes arthai_data / arth-memory-data / ~/.arthai/arth-router/ are never removed without --purge-data + typed confirmation)

Troubleshooting

Problem	Fix
“cloud posture requires an Arth Cloud deployment: coming at cloud GA”	Expected until your org has a hosted deployment. Use /arth-setup → local for now; set ARTH_CLOUD_URL and re-run when it ships.
One product’s setup failed mid-run	The umbrella continues with the rest (fail-open). Re-run /arth-setup: each delegated skill is idempotent and only redoes what’s missing.
Services show ✗ in the combined health line	Informational, not fatal: that product falls back to stock behavior. Check its container (docker ps) or re-run its per-product skill.
Switched posture but sessions unchanged	Env files load at session start: open a new session.
switch off but the containers are still running	By design: off is a config change, not an uninstall. Run /arth-setup uninstall <product> for the printed compose-down command.
Worried uninstall will delete your data	It can’t: data volumes are only touched with --purge-data AND an exact typed confirmation (purge <product>). Plain uninstall preserves everything.

Related

• /otel-setup, intelligence (telemetry + dashboard); the umbrella’s first delegate
• /memory-setup, the org decision/memory layer; the umbrella’s second delegate
• /router-setup, plan/credit-aware routing; the umbrella’s third delegate
• /router, day-to-day router operation once set up

Router prerequisite: /router-setup needs read access to the private ArthTech-AI/arth-router repo, separate from the plugin-repo invite. Ask productive@getarth.ai before ticking router, or it stops at the clone step.