Skip to main content
Setup ends when you read a draft you would send. One command opens the dashboard; then you describe your product, run a finder, review its candidates, and preview a batch before anything sends. You need Bun 1.3 or later.

​
Open the dashboard

This downloads the published dashboard server. The terminal CLI is not on npm. It needs a source checkout.

​
Install from source

Install from source to get the terminal CLI as well as the dashboard.
The dashboard opens on the workspace’s port, normally http://127.0.0.1:3030 for the default workspace.

​
Configure your motion

Configuration happens in two dashboard pages: Setup for who you are, Queue for who you look for. In Setup, describe your product, who it is for, and the founder experience that makes your approach credible. Add factual product links. Replies may use them but should not invent others. Optional founder fields can stay blank. Configure your LLM provider and OneShot credentials, and add a sender identity before sending. doctor reports missing credentials and deliverability issues. Some finders need extra keys: GitHub finders need GITHUB_TOKEN for practical rate limits. In Queue, configure a finder, check its readiness message, and run it. Discovery and research can spend money. Review the queued person’s evidence and draft before approving or sending.

​
Preview a drain

A dry run previews a drain and sends nothing. Choose a play that matches approved rows in your queue. See finders for discovery and sending for sender setup. For a fictional dashboard, run bun run cli -- demo seed, then bun run cli -- demo ui. Demo state is isolated; action calls are not simulated.