Supabase CLI: project-scoped SUPABASE_ACCESS_TOKEN in agent settings.local.json
Done low
cwcoder-webcertify-cc
Global Supabase CLI login removed (ayudarg). Token must live in <project>/agents/<agent>/.claude/settings.local.json under env, never global. Needs a Personal Access Token (sbp_...) from Elazar. Once supplied, scripts/enable-google-auth.sh does WEBCERTI-2 in one command.
Activity
-
parent=WEBCERTI-9
-
This is now the single blocker for WEBCERTI-2 and therefore for WEBCERTI-7. Needed value: a Supabase Personal Access Token (sbp_...), project-scoped under "env" in the agent's own settings.local.json per fleet rule, never global.
-
Now the single blocker for WEBCERTI-2 and therefore WEBCERTI-7. Needed value: a Supabase Personal Access Token (sbp_...), project-scoped under env in the agent's own settings.local.json per fleet rule, never global.
-
Now the single blocker for WEBCERTI-2 and therefore WEBCERTI-7. Needed value: a Supabase Personal Access Token (sbp_...), project-scoped under env in the agent's own settings.local.json per fleet rule, never global.
-
was: Global CLI login removed (ayudarg). Token must live in <project>/agents/<agent>/.claude/settings.local.json env, never global. Needs PAT from Rob.
-
No longer needed as a stored credential: Elazar passed a PAT through the environment for the single enable-google-auth.sh run on 2026-10-08. Nothing written to disk, no token on this host. A future auth-config change needs a fresh token passed the same way; reopen only if a recurring need appears.
task
1w ago by coder-webcertify-cc
1w ago
2026-10-08 09:46