# at your desk, or away

2026-09-30, updated 2026-09-30

Burst for the task you want moving now. Sunrise for work you leave running. Both start in your usual coding app and end at a reviewed pull request.


A coding task can arrive while you are halfway through another one. You want the flaky test fixed,
but you also want to finish the feature you already have open. Later, you might leave the larger
cleanup running while you close the laptop and go elsewhere.

Wayari should be useful in both moments. You keep working in Claude Code, Codex, Gemini CLI, Grok
or Cursor, with the subscriptions you already pay for. Describe the task and say **use Wayari**.

The 0.8.0 release gives those two tempos names: **Burst** and **Sunrise**.

## a burst while you are there

Start with a task small enough that you can read its result during your current session:

> Use Wayari to fix the flaky auth test while I wait. Keep the public API the same and prove the fix with the auth tests.

Your existing agent can hand that sentence to Wayari. The new `wayari go` entry point reads it as
Burst and says why. Burst uses the small pipeline, with two builders by default. If your sentence
names enough separate pieces of work, the starting crew grows to three.

A small pipeline still meets the repository's checks and review. A separate reviewer reads the
change before it reaches the person who will decide whether to merge it.

You can keep working on your own task. The crew's branches and worktrees keep its edits separate.

## sunrise when you leave

For a job you want to leave running, say so in the sentence:

> Use Wayari to fix the flaky auth test overnight. Keep the public API the same and prove the fix with the auth tests.

Words such as **overnight**, **while I am away** and **by morning** choose Sunrise. It uses the full
pipeline. Planning, building and verification lead to the same hand-off: a pull request with its
review, waiting for your decision.

The current reader uses your words. It does not detect whether you have left the desk. If it reads
you wrongly, an explicit mode overrides it.

## try the reading without starting work

You do not need to learn a command to ask your own agent for work. If you want to inspect the reading
in a terminal, `--dry` shows it without opening a channel:

```sh
wayari go "fix the flaky auth test while I wait" --dry
wayari go "fix the flaky auth test overnight" --dry
wayari go "fix the flaky auth test" --mode sunrise --dry
```

When quick and overnight language conflict, the reader chooses Burst and explains the ambiguity.
That conservative reading avoids treating a quick job as a night of unattended work.

## a night is not a hidden deadline

**Overnight** chooses the pace. It adds no clock. A duration exists only when you name a number,
such as **for 30 minutes**, or give an explicit clock flag.

Neither mode grants a merge. Even a sentence that says "send it to production" does not deploy a
system through `wayari go`. Read the review, decide whether to merge, and make the release decision
for your repository.

[Start your first job](/docs#first-job), or [download Wayari](/download) and open it once to connect
the coding agents you already use.


[HTML version](https://wayari.com/blog/burst-and-sunrise)