Sending a task

One sentence in your own words. The clearer the target, the easier the result is to check.

Phrasing

• Name the file or the area. “In DateUtils.kt, lift the hard-coded labels to constants” is checkable. “Clean up the date code” is not.
• Say what should happen afterwards. “Then run the build to check nothing broke” turns a guess into a verified change.
• Say what not to do. “Do not commit” is honoured.

What happens next

1. Queued

   The task joins the workspace queue and waits for a machine to pick it up.

2. Claimed

   A executor takes it. The card shows which machine.

3. Pre-flight

   KernelHub reads your sentence for tiers it will obviously need. If one is missing, it stops here — before spending a run.

4. Running

   The agent works. Evidence and diff stream back.

5. Result

   Done, blocked, or failed — with what it changed.

Changing your mind

Revise sends a follow-up into the same task, keeping its history and its diff. Cancel is honoured mid-run.

Several tasks at once

One agent can run several tasks concurrently, but two tasks editing the same files will fight. Keep concurrent tasks on separate areas of the code.