Swarm and shared runs

Many vendors, one reviewed result.

Connect your coding agents, choose a repository, and start a Swarm with a specific goal. Velora proposes a versioned plan with provider assignments, file ownership, dependencies, acceptance checks and a cost estimate. Workers wait for your approval.

Review the plan

Approve the current revision, edit it into a new revision, or reject it. Parallel workers receive separate worktrees and declared ownership. Writes outside that ownership are quarantined; unresolved integration conflicts stop for review.

Follow work and accept the result

The board shows each node’s activity, dependencies, changed files and reported usage. Missing cost reports stay unknown. The combined change receives fresh independent review; findings can trigger at most two repairs. Accept and merge is available after the approved revision passes independent review.

Invite a teammate

Share the role-scoped link from the run’s Room panel. Teammates can sign in and follow the room in their browser. Owners and maintainers approve plans; contributors can comment and steer; viewers follow shared summaries. The desktop host processes controls while the panel is closed and the app remains running.

Shared projections include plan summaries, status and activity. Model output and patch bodies stay private. Running execution stays on its host; cloud execution and transferring a live host between machines are later phases.

Use Rooms, Runs, Library and Brain navigation, or enable Classic navigation for earlier workflows. Cursor availability depends on a compatible installed ACP CLI. Current prices and entitlement-enforcement defaults are unchanged.