For teams, arriving in December
The Lanes gateway.
An optional bridge from your lanes to Autter, for teams that want every lane checked while agents work and reachable from the cloud.
You don't need Autter to use Lanes. Everything except the gateway itself works without an Autter account. Lanes is, and always will be, maintained as its own project, independently of Autter or any other product.
Connected, one repo at a time.
Photo: Filip Filkovic Philatz, Unsplash
How it works
Three steps, and the first two happen once.
- Your machineYour lanesfix-auth, add-tests, new-billing
- Opt-in, per repoLanes gateway
lane login, then choose repos - AutterChecks every laneRepo Q&A, Security checks while agents work, A safe-to-merge verdict on every PR, Cloud agents and CI without cloning
- 1Sign in. Run lane login to sign in to Autter.
$ lane login - 2Choose repos. Pick which repos to connect. Nothing is shared until you do, and every other repo stays on your machine.
- 3Work as usual. Lanes in connected repos reach Autter through the gateway, and Autter checks each lane as its agent works.
What you get
Repo Q&A
Ask about your repo, or any change in a lane, in plain English.
Security checks while agents work
Not after the pull request is open.
A safe-to-merge verdict on every PR
Including the ones lane promote opens.
Cloud agents and CI without cloning
They read the repo through the gateway.
How an Autter review runs on a lane.
Autter's reviews are hosted entirely in its cloud. Your lane stays on your machine, and the gateway lets the review read what changed.
Your machine
fix-authClaude Codesrc/auth.ts+38 −6src/session.ts+4 −1
Findings on this lane
- 2 review comments
- No security issues
- Tests pass
- Safe to merge
Autter cloud
Review running
- Code review
- Security checks
- Tests
Runs on Autter. Nothing runs on your machine.
The agent works in its lane
On your machine, as usual. Nothing extra runs locally.
The gateway shares the changes
For connected repos only, Autter's cloud reads the lane's changes through the gateway. No clone, no copy of the repo to keep in sync.
Autter reviews in the cloud
Code review, security checks and tests run on Autter, while the agent is still working.
Findings come back to the lane
Comments land on the lane and in the terminal app, and the PR gets a safe-to-merge verdict.
Where it's going.
The gateway arrives in December. Over time, it turns Lanes and Autter into one loop, from an agent's first step to a verified fix in production.
Write
Agents work in lanes, on your machine or in the cloud.
Check
Autter reviews, tests and security-checks each lane in its cloud while the agent is still working.
Ship
lane promote opens one clean PR, and Autter's verdict says when it's safe to merge.
Fix
When something breaks in production, Autter traces it and the fix comes back as a new lane, which goes through the same checks.
and back to the start: the fix is a new lane
This is a direction, not a promise of dates beyond December.
Coming next on the gateway.
After the gateway launches in December, connected repos get these too.
Lanes your team can open
A connected lane’s checkpoints are kept with Autter, not pushed to GitHub. A teammate runs lane open to get your agent’s lane on their machine, with its own ports and database, before it’s a pull request.
Agents with their own access
Register an agent by name, give it access to the repos you choose, and see its name on every change. Switch it off and its writes stop at once.
Merged after checks
A promoted lane can merge through Autter once its checks pass. If it conflicts, you get the files and lines, and nothing is written.
What stays the same
Autter is never required. Lanes stays open source under the AGPL-3.0, works fully without Autter, and is maintained independently of it.
Connecting is opt-in, one repo at a time.
Repos you don't connect never leave your machine. For them, Lanes sends only the anonymous install count, which you can turn off.