Skip to main content
The app is designed to run locally first. Most screens can be opened without external accounts. Live agent calls, database writes, auth, and workflow runners only need setup when you want to test those specific parts.

​
No-key mode

Without any keys, you can still:
  • Open the space.
  • Edit pages and tables.
  • Use the local chat fallback.
  • Preview these docs.
  • Open settings and setup screens.

​
Optional setup

  • OpenAI: add OPENAI_API_KEY for live agent responses.
  • Supabase: add URL and service role values for browser-visible Tables pages.
  • Inngest: start the app normally and start the dev server for local workflow runner tests.
  • WorkOS AuthKit: add the WorkOS values only when you want session-based auth.

​
Settings screen

The settings page stores local demo preferences in the browser. It includes sections for general behavior, appearance, agent behavior, keyboard shortcuts, space panels, database panels, workflow logs, OpenAI, Supabase, and Inngest. Some settings are visual or preparatory while the full demo surfaces are still being wired.

​
Current limits

  • /tables includes browser-visible Supabase table pages for users, spaces, teamspaces, groups, pages, AI chats, people, skills, tools, workflows, workflow runs, and workflow run steps.
  • /chats/new focuses on the agent chat; use /tables for current foundation and workflow data.
  • /chats/new is currently an authoring surface and does not auto-start durable Procedure runs. Use page Run or Preview when you want workflow execution evidence.
  • /workflows/runs/:runId shows the linked person, workflow definition, step status, inline @ procedure mentions, Inngest event id, and visible event log for one durable run.
  • The chat can fall back locally when OpenAI is missing, but fallback mode does not run the model.
  • The read_person and create_person Procedure actions require Supabase service credentials and a running Inngest worker for durable execution.
  • Optional AuthKit setup is allowed to be missing during local development.

​
What to check first if something looks wrong

  • If chat is fallback-only, check OPENAI_API_KEY.
  • If record panels are missing, check Supabase URL and service role values.
  • If workflow database tools are missing, check Supabase URL and service role values.
  • If workflow runs pause, check the run detail events for missing facts or requested human/user input.
  • If workflow runs do not progress, check the app startup command and local Inngest server.
  • If auth banners appear, open /auth/setup and follow the displayed configuration checks.