Demo build. All companies, metrics, messages, and tasks are placeholder data. Nothing connects to a backend; nothing you click writes to a database.
Helix Studio

Chat with Helix Studio's CEO

Type a message. It becomes a paperclip issue + the CEO is invoked to respond (heartbeat run, 3-5 min typical). Auto-refreshes every 15s.

This company is not wired to the orchestrator yet (missing companies.meta.orchestrator_company_id). Onboard via: cd packages/helix-studio && ./onboard.sh
Cmd/Ctrl+Enter to send. 0/4000
Wire this company to paperclip first.

What happens when you send a message:

  1. Your message becomes a new paperclip issue (status=backlog, assigned to CEO)
  2. The CEO is invoked via heartbeat with your message as wake context
  3. CEO reads its instructions + state, decides, posts comments + dispatches to specialists
  4. Refresh (auto every 15s) to see responses appear

Each heartbeat run takes 3-5 minutes typical (Opus 4.7 thinking time).