Skip to main content
The Workflow Agent is a local demo app for running enterprise workflow work from one space. You can open space documents, write or edit workflow pages, run a page into the chat surface, and test an agent chat that can use real page-editing tools when the local services are configured. The app is still an MVP. These docs describe what is available now, not the finished meeting demo.

​
What you can do now

  • Browse spaces from the left sidebar.
  • Open saved pages and tables from seeded demo spaces.
  • Edit page content in a rich Markdown editor.
  • Open Preview from a page header to chat with that page in a side panel.
  • Add simple workflow instructions and IF blocks to pages.
  • Click Run on a page to hand the workflow to the chat view.
  • Use the agent chat at /chats/new with visible thinking and tool-call activity while the model runs.
  • Ask the agent chat to edit workspace pages and review the changed-line diff before opening the page.
  • Reopen saved AI chat threads from the sidebar, including Preview-created threads, and archive threads you no longer want shown.
  • Open a workflow chat after a page Run, with the workflow title and node-level Progress visible on the main chat page.
  • Open the Tables section to inspect live Supabase foundation tables and workflow tables.
  • Open settings for local demo preferences and integration setup.

​
What is wired behind the scenes

The Supabase schema includes users, workspaces, teamspaces, groups, pages, AI chats, AI messages, people, skills, tools, workflows, workflow steps, workflow runs, workflow run steps, and workflow run events. The chat and Preview routes save active chat threads and their user/assistant turns there. The live chat route registers selected workflow database tools only when Supabase service credentials are configured, starting with the narrow create_person tool. The main chat does not auto-start durable Procedure runs right now; use page Run or Preview when you want to execute a workflow page. The app also includes an Inngest-backed path for workflow page runs, a local Electron desktop wrapper, optional WorkOS AuthKit login, and repo checks that keep the monorepo structure in shape.

​
What is still being built

The biggest missing product piece is the polished first-run demo flow and production-grade WorkOS-to-Supabase permission mapping. The workflow tables are visible in the browser, but broader tenant-aware workflow write permissions are still being shaped.

​
Where to go next

Start with Quickstart if you want to run the app locally. Then read Agent Chat and Spaces to learn the two main ways to use the app today.