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
fix(tutorials): list the Grok Bot recipes tutorial in the manifest so it is reachable, and log the agent-gateway worker audit
nirholascb39f2612b5c
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.mdindex 2f2adbab0..679e6e522 100644--- a/prompts/finish/_context/x-grok-PROGRESS.md+++ b/prompts/finish/_context/x-grok-PROGRESS.md@@ -128,3 +128,9 @@ Added `agent-get-started`, `daily-3d-brief`, `asset-pack`, `avatar-from-photo` t- `scripts/audit-agent-operability.mjs` (`npm run audit:agent-operability`) drives /create, /forge, /connect, an agent profile and /launch with getByRole/getByLabel only. Before: 24 findings across 5 flows. After: 5/5 flows pass, 0 findings, 0 console errors. Evidence: `prompts/x-grok/_generated/operability.json`.- Fixes: accessible names contain the visible text (forge engine, Surprise me, Enhance, More ideas, Roll & Forge, create cards, x402 badge), launch counters moved to aria-describedby, atlas hint chip is a real button, walk companion canvas is a keyboard-operable named button.- Not verified: forge generation completing (the local run stalled at 95% after 200s); the audit asserts the visible status during the wait instead.++## 2026-10-09: order 045 (gateway worker rebuild) found already built, one line open++- Step 0: `workers/agent-gateway` is fully committed (src/index.js, drain.js, adapters/telegram.js and discord.js, setup.js, Dockerfile, cloudbuild.yaml, README.md, scripts/deploy-env.mjs, 4 test files; commits 7da824e6b, eaba66bc6, 604801491, 34d2f93c1). The order's premise (package.json only) is stale; nothing was rebuilt.+- Evidence: worker `npm test` 62/62 pass on a real Postgres engine (PGlite running the shipped gateway migrations) with adapter fakes at the platform boundary; the `/help` Telegram fixture drains through `handleEvent` and the adapter, row acknowledged. `npm run dev` boots, serves `/healthz` (503 with no bot token, as documented), backlog read from the real inbox. README coverage loop prints nothing. `cloudbuild.yaml` parses, pins `three-ws-build@` and `three-ws@`; `gcloud builds submit` has no dry-run flag; `check:gcloudignore` OK. Root `npm test` had one red, `tests/tutorials-manifest.test.js`, because `grok-bot-recipes` (order 038) had no manifest entry; added it to `public/tutorials-manifest.js` and the test passes.+- Open line: "npm run dev drains a locally queued Telegram event". The Neon HTTP driver cannot reach a local Postgres, and `.env.local` is production, so a live drain would claim and answer real chats with a real token. Proven in tests instead. Owner: after deploy, send `/help` to the bot and watch `/healthz` counters (`GATEWAY_CHAT_KEYS` confines a local run). Deploy: `gcloud builds submit --config workers/agent-gateway/cloudbuild.yaml . --region us-central1 --project aerial-vehicle-466722-p5 --substitutions=SHORT_SHA=manual$(date +%s)`. Order file left in place.diff --git a/public/tutorials-manifest.js b/public/tutorials-manifest.jsindex ebc83ccb4..612b00418 100644--- a/public/tutorials-manifest.js+++ b/public/tutorials-manifest.js@@ -714,6 +714,16 @@previewModel: '/animations/robotexpressive.glb',ctaPrimary: { label: 'Browse the guards', href: '/guards' },},+ {+ slug: 'grok-bot-recipes',+ tier: 'middle',+ title: 'Grok Bot recipes',+ blurb: 'Six jobs to hand Grok Bot through the three.ws connector, each with the exact sentence to give it, the tools it calls in order, and the real output captured from production.',+ builds: 'Six working Grok Bot jobs and a script that reruns each one',+ time: '20 min',+ previewModel: '/animations/robotexpressive.glb',+ ctaPrimary: { label: 'Read the Grok Bot guide', href: '/docs/grok-bot' },+ },];const TIER_META = {