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(seeker): survive a tap that navigates while the hand indicator is painting
nirholasee9add31cb3c
diff --git a/.gitignore b/.gitignoreindex dc8b57d1b..7bf577d34 100644--- a/.gitignore+++ b/.gitignore@@ -519,6 +519,9 @@ marketing/*/kit/cards/*.png# The script removes them on a clean run; a killed run leaves hundreds of JPEGs# behind, and one got swept into a commit before this rule existed.marketing/*/.raw/+# The feature tour walks the whole app and leaves its own raw directory behind,+# 700 frames and 174 MB on the run that landed here.+marketing/*/.raw-*/# The product demo film (scripts/make-product-demo.mjs, `npm run demo:video`).# Every chapter is a 1080p screen recording of the live site and the set runs to@@ -529,6 +532,12 @@ marketing/*/.raw/marketing/product-demo/*.mp4marketing/product-demo/.smoke/+# Same reasoning for the Seeker long-form feature tour: seeker:screencast makes+# a 14 second listing clip small enough to track (seeker-device.mp4 /+# seeker-screen.mp4 stay committed), while seeker:feature-tour walks the whole+# app and lands hundreds of megabytes that GitHub would refuse on push anyway.+marketing/seeker-video/seeker-feature-tour-*.mp4+# Screenshot captures dropped in the repo root by browser and mobile checks.# Real assets belong in public/; scratch captures are never committed./*.pngdiff --git a/solana-mobile/scripts/lib/hand.mjs b/solana-mobile/scripts/lib/hand.mjsindex 311f350b7..23d314835 100644--- a/solana-mobile/scripts/lib/hand.mjs+++ b/solana-mobile/scripts/lib/hand.mjs@@ -123,8 +123,17 @@ export class Hand {await this.paint();}+ /* A tap that navigates tears down the execution context while the bloom+ frames are still painting into it. The indicator is re-installed on the+ next document by the capture's addInitScript, so the only lost thing is+ this one in-flight frame's position, which the next paint restores. The+ frame's screenshot applies the same policy a step further down. */async paint() {- await this.page.evaluate((s) => window.__seekerHand?.set(s), this.state);+ try {+ await this.page.evaluate((s) => window.__seekerHand?.set(s), this.state);+ } catch (err) {+ if (!/execution context|navigat|closed|destroyed/i.test(err.message)) throw err;+ }}/** One captured frame at the current state, with a breath of idle drift. */