arthai-marketplace

/cloud-setup

Configure the Arth dashboard’s UI/cloud features — the “Explain this session” LLM key and the experimental Cloud Orchestrator (calibrate/plan a repo). Runs on top of a telemetry-only /otel-setup install.

Synopsis

/cloud-setup

When to use it

• You ran /otel-setup (telemetry-only) and now want the dashboard’s “Explain this session” AI summary
• You want to turn on the experimental Cloud Orchestrator (point Arth at a Git repo to calibrate or plan a feature live)
• You’re adding an LLM key, GitHub token, or license to an existing Arth Intelligence install
• Not for: the OTEL telemetry stack itself (cost/token/session data) — that’s /otel-setup, which stays telemetry-only

Quickstart

/cloud-setup

What you’ll see: a precheck that your local Arth Intelligence stack is healthy, then two optional questions — enable Explain (pick a provider/key) and enable the Cloud Orchestrator (collect the required secrets, write the override, pull the sandbox). You can enable just one, both, or skip both entirely. Telemetry is never touched.

CLI parity

The same interactive flow ships in the Arth CLI for terminals without the toolkit:

arth cloud-setup

Install the Arth CLI first — it ships through the private Arth repo (gated by your GitHub access, no public package).

Examples

/cloud-setup        # the only form — the skill takes no arguments

Typical runs:

• Just want Explain → opt into Explain, pick a provider/key, decline the orchestrator → dashboard summaries turn on
• Want the full cloud experience → opt into Explain and the orchestrator → it writes the override, pulls the sandbox, and Runs / ☁ Calibrate a repo appear at http://localhost:3100
• No toolkit installed → run arth cloud-setup in a terminal for the identical flow

What it does

1. Precheck — Arth Intelligence must be running. Confirms Docker is up, ~/.arthai/docker-compose.yml exists (from /otel-setup → Local), and the engine is healthy on :4319. If not, it stops with the exact fix (run /otel-setup first, or start the stack).
2. Asks: enable “Explain this session”? (FIRST, and NOT experimental). A user-confirmation checkpoint. Optional and separate, API-billed (not your Claude Code subscription) — ~$0.001–0.002 per session on a small/flash model, or free with local Ollama / LM Studio. Pick a provider in plain language (Anthropic / OpenAI / Gemini / Ollama / LM Studio / Bedrock); it confirms your choice (e.g. “Anthropic, claude-haiku-4-5, ~$0.001/session”) and estimated per-session cost, then saves the key/host to ~/.arthai/.env and recreates the dashboard to pick it up. LM Studio auto-detects the loaded model (e.g. qwen) — no model id needed. Skip it and the dashboard shows a small “needs an LLM key” prompt where the summary would go. (/otel-setup also offers to turn on Explain inline at the end of its own flow, right after it verifies telemetry — so you don’t have to run this skill just for Explain.)
3. Asks: enable the Cloud Orchestrator? (experimental, off by default, Claude-only). A user-confirmation checkpoint. If you accept, it collects the required secrets and writes an additive ~/.arthai/docker-compose.override.yml (orchestrate flags + sandbox image + Docker-socket access — the base compose is untouched and reversible), pulls arthai/cloud-sandbox:latest, and recreates the dashboard with cloud enabled. The sandbox runs Claude only (for now), so it needs an ANTHROPIC_API_KEY — if your Explain choice in step 2 was Claude it’s reused; if it was a non-Claude provider (or you skipped Explain) you’re asked for a Claude key now (both keys are kept). It also needs ARTH_GITHUB_TOKEN + ARTH_LICENSE_KEY. Decline (default) and nothing changes.
4. Summarizes what’s now on (Explain / Orchestrator) and confirms telemetry is unaffected.

Output & artifacts

• ~/.arthai/.env — the LLM key (Explain) and any orchestrator secrets, expanded by docker-compose. Survives image updates (pulls/Watchtower never remove it).
• ~/.arthai/docker-compose.override.yml — orchestrator flags + sandbox image + socket mount (only if you enabled the orchestrator). Delete it to turn the orchestrator off.
• A recreated arthai-intelligence container picking up the new config. Dashboard at http://localhost:3100.

Troubleshooting

Problem	Fix
Arth Intelligence isn't installed yet	Run /otel-setup (pick Local) first, then re-run /cloud-setup
engine isn't healthy on :4319	Start the stack: docker compose -f ~/.arthai/docker-compose.yml up -d, then re-run
“Explain this session” still shows the key prompt	Re-run /cloud-setup, opt into Explain, and provide a key (or set up local Ollama for free)
No Runs / Calibrate a repo in the dashboard	The orchestrator flags aren’t set — re-run /cloud-setup and accept the Cloud Orchestrator step
Sandbox fails to start on a run	Confirm the Docker network: docker network ls | grep arthai should show arthai_default; adjust ARTH_CLOUD_DOCKER_ARGS in the override if it differs

To disable the orchestrator: delete ~/.arthai/docker-compose.override.yml and run docker compose -f ~/.arthai/docker-compose.yml up -d.

Related

• /otel-setup — the telemetry stack this builds on
• Cloud Orchestrator guide — full walkthrough of calibrate/plan a repo
• Arth Intelligence guide — what the dashboard shows
• Configuration → Explain this session