Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(finish): close order 960 after re-verifying it already shipped
nirholasfb71ef596edb
diff --git a/prompts/finish/960-one-flag-installers.md b/prompts/finish/960-one-flag-installers.mddeleted file mode 100644index c8c3e6ae7..000000000--- a/prompts/finish/960-one-flag-installers.md+++ /dev/null@@ -1,9 +0,0 @@-The three-ws CLI (packages/three-ws-cli) already writes MCP config for many clients through npx three-ws setup and verifies each server with a live tools/list. What is missing is the one-line install experience: a hosted shell installer, a single flag per client, and a Claude Code integration that also installs skills.--Build: a /cli/install script that checks OS and Node, installs or runs the CLI, and prints next steps; a /cli/claude script that wires the MCP and the skills into Claude Code and offers a one-command launch ("claude \"launch my agent\""); and per-client flags (npx three-ws --claude, --cursor, --codex, --vscode, --windsurf) that do the whole setup non-interactively. Pipe-to-shell is a trust problem: serve each script with a checksum and signature, document how to download and read it first, make it idempotent, and never write secrets to disk in plain text. Add npx three-ws team and agent status commands that show live state, and npx three-ws doctor that diagnoses a broken setup (bad config, expired auth, unreachable server).--Test on a clean container for each client config path. Update /connect, docs/cli.md and the CLI README with commands that actually run.-------This brief is standalone. Assume no other brief has run, and keep working if others run at the same time: use names unique to this work for tables, routes and files, give migrations a fresh timestamp, append to shared files instead of rewriting them, and re-read a shared file before you edit it. CLAUDE.md governs everything, including its spend gate (anything that signs or moves funds shows recipient, amount, asset and chain and waits for an explicit yes; test with devnet, simulation or paper mode) and the rule that nothing naming another crypto project is committed without the owner's approval, so list any new third-party names you introduce in your report. Never name any competitor in a committed file. Finish it fully: wire it, document it, add the changelog entry, verify it for real, and report what you observed.