Showrunner is a desktop app for operating local workspaces without splitting the job across five different tools.
Today the product is strongest where day-to-day workspace operations usually break down:
- terminal sessions that need to stay alive inside the product
- Git workflows that should not require constant shell context switching
- file structure and workspace roots that matter operationally
- dashboards for tasks, ventures, leads, observability, and ecosystem state
What Showrunner Is
Showrunner currently ships as a monorepo with three connected surfaces:
- Desktop app - the main operating surface
showCLI - workspace bootstrap and runtime commandsshowrunner-core- local HTTP runtime for health, status, sessions, commands, heartbeats, tasks, costs, and logs
This matters because the product is not just "another Electron wrapper". It is a local operating layer for teams and operators who already work inside structured repos and venture environments.
What The Desktop App Does Today
The delivered app already includes:
- workspace navigation across the Quartzo folder model
- file tree, preview, inline editing, upload, and move flows
- persistent terminal sessions via PTY
- Git sync surfaces for status, branches, drafts, and history
- onboarding for workspace path, optional apps path, and Git preferences
- operational dashboards like Home, Tasks, Leads, Ventures, Observatory, and Heart 3D
What It Does Not Claim Yet
Showrunner should not be positioned today as a fully shipped AI chat product.
There are runtime and AI-adjacent building blocks in the monorepo, but the product story that holds up right now is local workspace control, not speculative chat capability.
Why We Built It
The core problem is fragmentation. Files live in one place, terminal in another, Git in another, and operational context somewhere else. The work itself is local and continuous, but the tooling stack keeps forcing context loss.
Showrunner reduces that operational fragmentation.
Early Access
Showrunner is currently Windows-first. If your workflow depends on local workspaces, terminal sessions, Git operations, and venture-aware desktop tooling, request access and we will talk.