Desktop cheat sheet · Nick gospel 2026-07-03

Public vs Private Jarvis Pages

Every page lives at /p/{slug}. Default = auth gate (“Text jarvis for access”). Public = anyone with the link.

How the gate works

HTML file: imessage-bridge/pages/common/{slug}.html
URL: https://jarviscooks.com/p/{slug}
If slug ∉ PUBLIC_PAGE_SLUGS → cookie/role required
If slug ∈ set → 200, no login

Make public (pick one)

Instant (until restart): admin POST

POST /api/public-pages
Authorization: Bearer <admin api key>
{"slug": "my-page-slug"}

Persistent: add slug to PUBLIC_PAGE_SLUGS in both:

imessage-bridge/server.py
imessage-bridge/pipeline/config.py

Verify: incognito GET — title loads, no gate page

Make private again

DELETE /api/public-pages
{"slug": "my-page-slug"}

Remove from both PUBLIC_PAGE_SLUGS sets for persistence across restart.

Example (Impact Team hub)

Slug: impact-team-x-agexa-hub
Live: jarviscooks.com/p/impact-team-x-agexa-hub
Bug was: file existed, slug missing from allowlist → false gate

Rule: never post a team link without incognito check first.

When to use which

Public — client hubs, demos, shareable playbooks (this page)
Private — internal ops, P&L, credentials, WIP strategy
Role ACL — middle ground via PAGE_ACLS (logged-in, role-gated)