Create and run a task
From "I have a thing to do" to a merged diff, end to end.
The shortest path from idea to merged change.
1. Frame the task
Write the task description like a brief for a careful colleague. Name the file, name the convention, name the constraint.
Good:
Add audit logging to the settings save handler at
src/server/routes/settings.ts. Use the existingauditLoggerfromsrc/lib/audit.ts. Log the user id and the keys changed - never the values.
Bad:
Improve settings logging.
2. Start the run
vibe run "Add audit logging to the settings save handler..."Add --ui if you want the dashboard alongside:
vibe run "..." --uiPick a Flow if the work warrants the extra rigor:
vibe run "..." --flow quality-arbitrationOverride the provider for this run:
vibe run "..." --provider claudeOr use the effort bucket:
vibe run "..." --effort high3. Watch (or don’t)
Vibestrate runs through plan → architect → execute → validate → review → fix → verify on its own. You can watch each phase in the terminal or the dashboard, or close the terminal and check back later - the run keeps going as long as Vibestrate’s process is alive.
When the run finishes, it lands in one of:
merge_ready- diff is ready to ship.blocked- reviewer or verifier flagged something a human should decide.failed- unrecoverable error during a stage.
4. Inspect the result
vibe status # what landed
vibe replay <runId> # full read-only inspectorOr open the dashboard’s Git tab to read the diff inline.
5. Merge - by hand
Vibestrate does not push, does not merge. The run leaves the diff on its branch in the worktree. You decide:
cd ../.vibestrate-worktrees/<runId>-<slug>
gh pr create # if you want review by a human
git push # if you just want to share the branchOr merge locally:
git checkout main
git merge --ff-only vibestrate/<runId>-<slug>Or abandon it:
vibe abort <runId>
# worktree is preserved for inspection; remove when you're done