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): log order 026 scoped connector keys with its evidence in the x-grok progress file
nirholasad5635521fc6
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.mdindex 087761cf3..e83f78189 100644--- a/prompts/finish/_context/x-grok-PROGRESS.md+++ b/prompts/finish/_context/x-grok-PROGRESS.md@@ -77,3 +77,10 @@ Cross-session handoff for the `x-grok-` orders ([x-grok-00-CONTEXT.md](x-grok-00- Shipped `b025b8bb2`: `/api/mcp-grok` lists no widget templates or ui:// resources, and a caller with a valid OAuth token or connector key also gets an allowlist of account agent, memory, skill and avatar tools (`api/_mcp-studio/account-tools.js`). A tool on the financial policy tier or with a wallet, payment, trade or launch scope is never listed or callable. `?auth=oauth` on the URL forces the 401 challenge so Grok starts sign-in.- Measured: the same surface already existed on the diverged `evolve` branch; it was ported by hand onto main (main lacks `spendScopeFor`, so value-moving detection is the policy tier plus a scope regex). Probe against a clean worktree server: all 8 servers pass, grok anonymous 14 tools, with a key 24, OAuth challenge ok. 72 tests pass across the grok, resources, probe and install suites.- Not verified: the probe on the shared :3000 server (stale modules and another agent's unapplied `preset` migration made it fail for reasons outside this order).++## 2026-10-09: order 026 (scoped connector keys) done++- Shipped `addf07b55`: coarse key scopes `read generate agents:write spend` expand into the fine scopes routes already check (`api/_lib/key-scopes.js`), and the "For an AI agent (Grok Bot, schedules, CI)" preset is stored in `api_keys.preset` (migration `20261009153000_api_key_connector_preset.sql`, applied to Neon). A connector key is stripped of every spend-capable scope at `authenticateBearer`, so REST spend gates (`wallet:write`) refuse it, `api/_mcp/policy.js` hides value-moving tools from its `tools/list`, and calling one returns JSON-RPC `-32003` with `data.reason = spend_requires_browser_session` and the dashboard link.+- Pre-migration keys keep their power: the migration backfills `spend` onto keys holding `wallet:write` or `services:write`; tests cover a legacy spender and a legacy reader.+- Evidence: `tests/connector-keys.test.js` (18) refuses every value-moving tool on every server in the shared policy table and runs JSON-RPC end to end; full vitest 32064 pass, 3 failures in `onboarding-tier` and `x402-discovery-green` belong to other sessions. In a browser on a local dev server against the real DB, the New API key dialog showed the preset (default), the custom switch and the one-time reveal, and a key it minted got `-32003` on `paired_launch` and `agent_card_create`. Test keys were revoked.+- Judgment calls: `confirm_delete` and `confirm_run` stay allowed for connector keys (they move no funds); `read` excludes `profile`; the legacy `/api/api-keys` and CLI mint routes do not offer the preset.