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): trim orders 961 and 962 to the signing certificates and live bot check that need the owner
nirholasf2d99e84ea8e
diff --git a/prompts/finish/961-desktop-agent-runtime.md b/prompts/finish/961-desktop-agent-runtime.mdindex 61fbcb87b..7eff0461c 100644--- a/prompts/finish/961-desktop-agent-runtime.md+++ b/prompts/finish/961-desktop-agent-runtime.md@@ -1,9 +1,5 @@-apps/desktop (Companion) is a transparent always-on-top mascot that delivers notifications; apps/forge-desktop (Forge) is a local 3D toolchain. Neither runs agents. Users who want keys that never leave their machine, and strategies that run while the cloud is unreachable, need a local runtime.+Remaining owner steps for the desktop agent runtime: the local runtime, keychain keystore, tray, native payload-hash approvals, mascot states, headless smoke test (`npm run smoke:runtime` in apps/desktop) and the Linux installers (`npm run dist:linux`, AppImage + deb in apps/desktop/dist) have shipped.-Extend apps/desktop into an agent runtime on top of packages/agent-runtime: run agents, strategies, orders and automations locally, keep signing keys in the OS keychain (Electron safeStorage), and optionally sync configuration and receipts with the cloud account. A tray menu shows each agent's status with pause, kill and approvals, and native notifications carry approval requests using the same payload-hash confirmation as the web flow, so an approval cannot differ from what was shown. The mascot becomes the agent's face: it reacts to state (working, waiting for approval, error).--Security: context isolation on, an IPC allowlist, no key material in logs or crash reports, signed auto-update. Build installers with electron-builder for macOS, Windows and Linux and produce the Linux artifact in this session; signing certificates missing are an owner action to list. README with install steps and a runnable example, STRUCTURE.md row, and a smoke test that starts the runtime headless and runs a paper-mode strategy.-------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.+1. Provide the Apple Developer ID certificate (`CSC_LINK`, `CSC_KEY_PASSWORD`) and notarization key (`APPLE_API_KEY`, `APPLE_API_KEY_ID`, `APPLE_API_ISSUER`), then run `npm run release:mac` in apps/desktop.+2. Provide a Windows code-signing certificate and run `npm run dist:win` on a Windows runner or with wine.+3. Re-run `npm run smoke:runtime` from a network the pump.fun public feed answers (it returns 403 to some hosts, including this build machine), so the paper buy and open position checks run instead of printing SKIP.diff --git a/prompts/finish/962-approvals-inbox-telegram.md b/prompts/finish/962-approvals-inbox-telegram.mdindex 3b6803a2f..e41249586 100644--- a/prompts/finish/962-approvals-inbox-telegram.md+++ b/prompts/finish/962-approvals-inbox-telegram.md@@ -1,9 +1,5 @@-Ask-before-each-trade only works if approving takes two seconds from anywhere. We have push infrastructure (api/push, public/push-sw.js, api/_lib/web-push.js), confirm-before-execute intents (api/_lib/wallet-intents.js), spend-policy step-up rules and a Telegram gateway (api/gateway/telegram.js, workers/agent-gateway) that receives messages, but no approval queue and no two-way control from chat apps.+Remaining owner step for the approvals inbox: the inbox, API, /approvals page, web push, signed expiring Telegram buttons, chat commands, auto-approve rules and replay/tamper tests have shipped (see docs/approvals.md). What is left is a live check with a real throwaway Telegram bot, which needs a bot token from @BotFather.-Build an approvals inbox: a table of pending requests (agent, action, human summary, recipient, amount, asset, chain, payload hash, expiry), an API to list, approve and deny, a /approvals page with filters, and an audit trail. The payload hash binds what was shown to what executes; a tampered or expired request fails closed; approve is idempotent. Deliver each request by web push and by Telegram with inline Approve and Deny buttons whose callback data is signed and expiring, and show the full confirmation table in the message. Add Telegram commands: /agents, /positions, /pause, /kill, /approvals, and plain chat to the agent. Ignore commands from unlinked users and forwarded instructions.--Owners can create explicit auto-approve rules capped by size and venue, always revocable, default off. Use a maintained Telegram library (grammy or telegraf) after checking it. Test with a real throwaway bot and the replay and tamper cases.-------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.+1. Put the token in `TELEGRAM_BOT_TOKEN` (local `.env`), run `server/index.mjs` on a spare port with `--env-file`, and pair a chat with `/link`.+2. Create an approval request for a paper-mode swap, confirm the message shows the full confirmation table with Approve and Deny buttons, tap Approve twice (second tap must be a no-op), and let one request expire (button must fail closed).+3. Report what the chat showed. CLAUDE.md spend gate applies: use paper mode or devnet only.