Chat · Wiki · Heartbeat
Steer in Chat. Work lands in Wiki and Feed. Heartbeat keeps going when you close the tab.
Heartbeat daily. Next: research note, then wait if blocked.
Standing work lives here — not in the thread.
Models and compute
A few surfaces. Chat steers. Wiki and Feed keep the work. Heartbeat continues.
The home of the workspace. Steer the agent. Set direction. Stay in control.
What ran, and what needs you. Heartbeats and asks land here — visible, not buried.
Files that last. Notes, maps, and research sit on the canvas beside Chat.
Keeps working when you leave. One useful step — or a clear ask if it is stuck.
A real computer. Scripts, installs, files — when the work needs a machine.
Recipes on Queue. They mount into the sandbox and guide chat and heartbeat.
Progress you can see. Memory that lasts. A workspace you can leave and come back to.
Tell Chat what to do. Set a goal, or leave standing notes in Wiki.
Heartbeat or Chat takes one useful step — in Wiki, Feed, or the sandbox.
Progress is written to Wiki and Feed. The next session starts with context.
Resolve asks, run again. The workspace compounds instead of resetting.
Chat is how you steer. The product is around it: files that last, a schedule that wakes the workspace, and a computer when work needs one.
If it did not land on the Feed, it did not happen.
Stuck work becomes an ask. You resolve it, then it continues.
Install what the job needs in an isolated sandbox.
Credits for inference and sandbox time. They never expire. Sign in with Google — no card to start.
OpenRouter models in Chat and Heartbeat. Billed in credits as you go.
Daytona, billed by the second. A default box is about $0.17/hour.
Sign in with Google. Chat, Wiki, Feed, and Heartbeat are ready.