Tutorials

Every task in yothere follows the same shape: you hail it in one line, the fleet advances it on its own, and it comes back to your inbox only when it needs a human. These four recipes show that loop end to end, with the exact commands and what you’ll see.

Every recipe below can be dispatched three ways, they are equivalent:

• CLI: yothere spawn "<task>"
• Cockpit: type the task in the command bar at /overview and press Dispatch.
• Voice: tap Connect and say it out loud.

Recipe 1: Ship a fix

Hail it:

yothere spawn "fix the layout shift on the pricing page and open a preview"

The runner picks it up on the next tick and a brain (Claude Code on your machine) starts working in your project directory. You’ll see it in the Working lane with a live activity line: reading files, editing, running the build.

Because the send-gate is on by default, it will not push or merge on its own. When it has a branch and a preview URL, the thread moves to your Inbox as a result to review: “Pricing page fix ready.” Glance at the screenshot it attached, and either:

yothere reply <id> "looks good, merge it"

or click Looks good on the card. Done means done.

Recipe 2: Research a decision

Hail it:

yothere spawn "scan our top 3 competitors and draft a one-pager"

This is the classic ambient task: it runs for a while on its own, and pings you exactly once, at the fork that actually needs your judgment. Partway through you’ll get a question in your inbox, “Which segment should I prioritize, enterprise or mid-market?”, with the two options as one-tap chips. Answer it:

yothere reply <id> "mid-market"

It resumes on the next tick and finishes with a sourced one-pager in Past sessions. You spent ten seconds; it spent twenty minutes.

Recipe 3: Triage and draft

Hail it:

yothere spawn "triage the support inbox and draft replies for anything urgent"

yothere reads the inbox, groups what matters, and writes replies, but it never sends. Each drafted reply arrives in your inbox as a draft to send with the text inline and a Send button. You approve the good ones, edit or discard the rest:

yothere reply <id> "send it"

Nothing outward leaves your machine without that explicit yes.

Recipe 4: A standing job

Some work should just happen on a schedule. Presets are named, repeatable tasks:

yothere presets                 # list what's available
yothere preset news-scan        # run one now

A scheduled preset (for example a 7am news scan) advances quietly in the background and only surfaces a digest to your inbox on the days there’s something worth reading. On the quiet days, you hear nothing, which is the point.

Hailing by voice

Every recipe works hands-free. Tap Connect in the cockpit to open a live voice call, say the task out loud, and watch the transcript stream as the fleet answers back.

Where to go next

• The full command surface is in the CLI reference.
• The lanes and cards are covered in the Cockpit tour.
• Setting up on a fresh machine? Start with Onboarding.