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 945 after verifying any-token orders, MCP tools and unified DCA shipped, tested and documented
nirholas2672a23d1b4c
diff --git a/prompts/finish/945-orders-dca-any-token.md b/prompts/finish/945-orders-dca-any-token.mddeleted file mode 100644index 8687c1755..000000000--- a/prompts/finish/945-orders-dca-any-token.md+++ /dev/null@@ -1,9 +0,0 @@-Limit, stop, trailing, DCA and TWAP orders work today (workers/agent-orders, api/agents/orders.js) but only on pump.fun tokens, and agents cannot create them over MCP: api/_mcp/resources.js exposes orders and DCA as read-only resources. Meanwhile api/dca-strategies.js is a second, separate DCA system. Users expect to say "DCA 0.2 SOL into this token every day" or "sell half if it doubles" for any Solana token, from any client.--Extend the order engine to any SPL token by routing fills through the venue layer (Jupiter and PumpSwap; if a router module from another piece of work already exists in the tree, use it, otherwise call the existing executor in api/agents/solana-trade.js). Keep the audited path for every fill: guards, caps, idempotency key per slice, per-agent lock. Add MCP tools dca_create, dca_list, dca_cancel, limit_order_create, limit_order_list, limit_order_cancel, limit_order_history and stop and trailing variants, each with a preview that returns what would be placed and when, and a confirm flag on create. Merge the two DCA systems behind one API and migrate existing rows without losing any schedule.--Beyond parity: ladder orders (several take-profit levels in one call), OCO pairs (one fill cancels the other), expiry, a visible order book per agent with next-fire times and a reason for every skip (price outside band, cap hit, venue unhealthy), and a notification when an order fires or fails. Real executions use the existing spend gate; verify end to end in simulation and on devnet.-------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.