foolish-bandit adds a no-login demo mode to Gary

You can now walk through the whole interface without first standing up an account system.

infrastructurechat-ui

foolish-bandit wired in a switch that runs the app with a fake stand-in user, skipping the usual login step entirely. Flip it on and the assistant's screens open straight away - useful if you want to show the interface to a colleague or a prospective client without wiring up a real accounts service first.

There's a deliberate limit. The demo only dresses up the front end; anything that needs to reach the actual backend still expects a real, logged-in session and won't get one, so those requests fall flat. It's built to showcase how the product looks and feels, not to run a fully working system end to end. The switch is also locked in when the app is built, so there's no risk of it quietly slipping into a live, customer-facing deployment.

So what Worth a look if you're sizing up this fork and want to tour the interface before committing to any setup.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

0b9ad4db Add NEXT_PUBLIC_GARY_SKIP_AUTH dev/demo bypass Claude 2026-05-07 ↗ GitHub

SHA	Subject	Author	Date
`0b9ad4db`	Add NEXT_PUBLIC_GARY_SKIP_AUTH dev/demo bypass	Claude	2026-05-07	↗ GitHub
commit body Lets us inspect the app without going through Supabase login during development and on demo deploys. Frontend-only. When NEXT_PUBLIC_GARY_SKIP_AUTH=true: - AuthContext initializes with a fake demo user ({ id: "00000000-...-000", email: "demo@gary.local" }) via lazy useState, so isAuthenticated is true immediately. - The Supabase session check + auth-state-change subscription are skipped (the useEffect bails out after a one-time console.warn). - signOut becomes a no-op so the demo session stays stable. - A slim amber "Dev auth bypass enabled" banner renders at the top of the (pages) layout via the new DevAuthBanner component. - The flag is exposed as `isAuthBypassed` on the auth context so any consumer can branch on it later. When the flag is unset or "false": - useState initializers return null/true, identical to today. - The effect's bypass branch is dead and the original Supabase logic runs unchanged. Login/signup, signOut, and the redirect gate in (pages)/layout.tsx are untouched. Documents the variable in frontend/.env.local.example as commented-out so normal setups stay on real auth. No backend changes, no schema changes, no auth contract changes. Backend calls made while the bypass is on will 401 because no real Supabase session exists - that's intentional and noted in the console warning. https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL

commit body

Lets us inspect the app without going through Supabase login during
development and on demo deploys. Frontend-only.

When NEXT_PUBLIC_GARY_SKIP_AUTH=true:
- AuthContext initializes with a fake demo user
  ({ id: "00000000-...-000", email: "demo@gary.local" }) via lazy
  useState, so isAuthenticated is true immediately.
- The Supabase session check + auth-state-change subscription are
  skipped (the useEffect bails out after a one-time console.warn).
- signOut becomes a no-op so the demo session stays stable.
- A slim amber "Dev auth bypass enabled" banner renders at the top
  of the (pages) layout via the new DevAuthBanner component.
- The flag is exposed as `isAuthBypassed` on the auth context so
  any consumer can branch on it later.

When the flag is unset or "false":
- useState initializers return null/true, identical to today.
- The effect's bypass branch is dead and the original Supabase
  logic runs unchanged. Login/signup, signOut, and the redirect
  gate in (pages)/layout.tsx are untouched.

Documents the variable in frontend/.env.local.example as
commented-out so normal setups stay on real auth.

No backend changes, no schema changes, no auth contract changes.
Backend calls made while the bypass is on will 401 because no
real Supabase session exists - that's intentional and noted in
the console warning.

https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-269.md from inside the repo you want the changes in.

⬇ Download capture-thread-269.md