Workflow guides

Run, isolate, coordinate, verify, and deliver agent work safely in Synara.

Synara workflows are built around one rule: every body of work needs a clear owner and a verifiable result. The tools—tasks, worktrees, handoffs, browser automation, scheduled runs, and agent-to-agent coordination—are useful only when they preserve that boundary.

Start with the smallest workflow

NeedStart here
One focused changeOne task in a known checkout
Independent work in the same repositorySeparate worktree-backed tasks
A second provider continuing the same objectiveProvider handoff
Visual or web behavior verificationBrowser verification
Review and delivery through GitHubPull requests
Recurring workAutomations
Long-running, output-oriented workStudio
One Synara agent coordinating other Synara tasksAgent Gateway
Another local application creating restricted Synara tasksExternal MCP

Do not begin with maximum parallelism. First learn the complete loop: objective, execution, supervision, verification, review, and delivery.

Core workflow

Begin from a known state

Confirm the repository, branch, existing changes, provider, model, and task environment before sending work.

Give one owner a bounded objective

State the outcome, scope, constraints, and verification. Split work when those cannot be expressed clearly.

Supervise the work

Watch plans, tool activity, approvals, questions, and the growing diff. Correct wrong assumptions early.

Verify independently

Inspect every changed file and run the relevant checks. Use the browser when visible behavior matters.

Preserve and deliver intentionally

Commit only reviewed changes. Push, open a pull request, or archive the work only after its ownership and state are understood.

Guides

Last updated on