Prioritize
Pull candidate work from Linear or accept a task through Fleet. A human can choose what matters next.
A durable workflow around every coding agent.
Agent sessions end. Engineering work does not. A Fleet member carries a task across multiple agent runs, CI waits, review comments, and human decisions without losing its place.
Member / velaFL-0192 · active
VvelaPayments backend · day 18working
Linear · ENG-482
Prevent duplicate capture during retry
Selected from the Payments backlog. The issue anchor and acceptance criteria have been added to the member context.
PriorityHighProjectBilling reliability
Issue selectedImplementedCI passedLand decision
The member workflow
From priority to merged change.
Implement
Start a short-lived Claude Code run on a customer-controlled runner with the repository context it needs.
Check
Run precommit and local checks, push a branch, open the PR or MR, and wait durably for CI.
Review
Route review comments back into the active member and perform a semantic review before landing.
Decide
Raise office-hours, budget, breaker, and landing decisions in one attributed decision inbox.
Land
Merge the reviewed change and transition or comment on the source tracker issue.
Supervision
Humans decide. Fleet carries.
Fleet does not remove review or invent a global autopilot switch. Each checkpoint can require approval, auto-pass after observation, or stop immediately when a budget or safety rule trips.
?Office hoursThe member needs a judgment it cannot infer.$Budget guardA provider run or token cap needs review.✓Land approvalChecks are green and the change is ready.
Private previewKeep your coding tools.
Keep your coding tools.
Give them one engineering system.
Fleet is prelaunch and not accepting accounts yet. Join the private-preview waitlist or explore the product and security model.