Settings
Your keys, your rules.
How Artificial OS keeps your data and tokens yours.
Hosted demo
Anthropic API key
Powers the “API key” chat engine. Required on the hosted site; optional when running locally with Claude Code.
Privacy model
- The hosted site has no key and no data of its own. Its server refuses every local endpoint before touching a file or process, so nobody can spend the owner’s tokens or read their sessions.
- Your API key stays in your browser. It’s sent only to api.anthropic.com, enforced by this site’s Content-Security-Policy.
- Local mode answers only to this machine. The server binds 127.0.0.1, checks the Host header against DNS rebinding, and rejects cross-site requests.
- Secrets are never displayed. MCP entries show only the transport and host — no env values, headers or tokens.
Run it on your machine
Running locally unlocks the Claude Code engine (your subscription, MCP servers, skills and plugins), the session browser, real usage and the setup inspector — all read from your own ~/.claude.
- 1
git clone <your fork of artificial-OS> && cd artificial-OSGrab the code. - 2
pnpm installNode 20+ and pnpm. - 3
pnpm build && pnpm startServes http://127.0.0.1:7332 — loopback only. - 4
claude /loginOptional: sign in to Claude Code to unlock the Claude Code engine.