Skip to content

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.

docs(finish): trim order 954 to the Google client credential, production two-client check and pages rebuild

nirholasa0dd2183d5b1
diff --git a/prompts/finish/954-oauth-connector-google.md b/prompts/finish/954-oauth-connector-google.md
index 78cfc30e3..675ced7cc 100644
--- a/prompts/finish/954-oauth-connector-google.md
+++ b/prompts/finish/954-oauth-connector-google.md
@@ -1,9 +1,7 @@
-We have an OAuth 2.1 authorization server for MCP (api/oauth/[action].js with PKCE S256, dynamic registration, api/wk.js discovery documents) and sign-in with X, GitHub, SIWE, SIWS and Privy, but api/auth/google/ is empty. The target experience: one connector URL pasted into Claude or ChatGPT, sign in with Google or X, no API key, credentials never shown to the client. Competing connectors sign the first client out when a second connects; ours should not.
+Google sign-in, the grouped consent screen (Read, Manage, Trade, Spend, Launch with "still asks first" lists), Connected apps revocation with immediate effect, two clients staying connected, the /connect steps and docs/mcp.md are shipped and covered by tests (tests/api/google-signin.test.js, tests/oauth-endpoints.test.js, tests/api/oauth-*.test.js).
-Build Google sign-in properly (a direct OAuth authorization code flow with PKCE, account linking to an existing user by verified email with a confirm step, and a clean error state), and make it a choice on the MCP authorization screen next to X, GitHub and wallet sign-in. Verify the connector end to end against a real MCP client: Claude's custom connector flow and a second client at the same time, both staying connected. Scope the grant per tool group (read, trade, spend, launch) with a consent screen that lists what each scope can do and which actions will still ask for confirmation, and let the user revoke a client from settings with immediate effect.
+Remaining, owner-gated:
-Update /connect with the one URL and per-client steps. If a Google client credential is missing, follow the credential row in CLAUDE.md before concluding it does not exist. Document in docs/mcp.md and add tests for the token exchange and revocation.
-
----
-
-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. Create a Google Cloud "Web application" OAuth client in project aerial-vehicle-466722-p5 (console only, no CLI path) with redirect URI https://three.ws/api/auth/google/callback. Store GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET in Secret Manager and attach them to three-ws-api with `gcloud run services update --update-env-vars` / `--update-secrets`. Until then api/config.js hides the Google button.
+2. After deploy, connect Claude's custom connector and a second client at once against production and confirm both stay connected, then revoke one in Settings, Connected apps.
+3. Run `npm run build:pages` once the shared worktree's changelog edits settle (it errored in a dirty tree).