Lotsa pilots your coding agents through a rule-enforced pipeline, running in parallel across your repos. Self-hosted. Your keys, your rules.
Apache-2.0 · self-hosted · works with Claude Code & Codex · your keys never leave your machine
Conventions you set become stages the pipeline must execute. They don't depend on a prompt the agent might forget three tasks from now.
Your guardrails and review steps are pipeline stages, executed in order — every run, not when the model remembers.
Each stage must pass before the next begins. No skipped tests, no silent edits, no "I forgot to write the spec."
Approve the plan. Approve the PR. Lotsa never merges on its own — you stay the pilot at every gate you choose.
Task #100 gets the same rigor as task #1.
Drive Claude Code, Codex, or your own model through one consistent, repeatable flow.
Kick off many tasks at once across every repo you own — a whole fleet moving together.
Spec, plan, test, code, review, verify, PR — in that order, on every single run.
Pause for approval exactly where you want a person in the loop. Skip them where you don't.
Self-hosted and model-agnostic. Nothing routes through us — ever.
Every task lands as a branch and a pull request — then follows it to merge, fixing review and CI feedback along the way.
Tell Lotsa the task in plain language, right in the chat.
It writes a spec and a plan against your rules — and waits for your gate if you want one.
Your agent writes the code and the tests, iterating until everything is green.
A self-review pass and your human gate stand between the work and the branch.
Lotsa pushes a branch and opens a pull request — your harbour for the finished task.
The same pipeline, many tasks, every repo — each one piloted into its own pull request in parallel.
Most tools hand you a pull request and walk away. Lotsa keeps watching it — when a reviewer or CI leaves actionable feedback, it dispatches a fix, pushes again, and re-runs its own review, automatically, until the PR is merged. You're not the one ferrying review comments back to an agent.
It pilots the ship all the way into harbour — not just to the harbour mouth.
Lotsa doesn't replace the tools you code with. Reach for it when you want…
enforced rules — your conventions run as steps, every task, not when the model remembers
quality you can trust — tests written, the diff reviewed by a fresh agent, the build verified before any PR opens
to close your laptop — kick it off, walk away, come back to an open pull request
to run a fleet — many tasks at once, across every repo you own
the PR handled to merge — it watches the PR and fixes review/CI feedback for you
a person in the loop only where it counts — a gate where you want one, nowhere you don't
on your own terms — your machine, your keys; nothing routes through anyone
"I keep Claude Code open for hands-on work, and hand Lotsa the tasks I want run to a standard without babysitting. Use the right one for the moment."
An idea, a ticket, a chore.
Claude Code, Codex, your model.
Rules, gates, order — enforced.
A pull request, ready to review.
One binary, static-hostable, Apache-2.0. Read every line, run it air-gapped, bring your own model keys.
Shared pipelines, org-wide rules, and a fleet view for everyone. Be first to know when it ships.
No spam. One email when Teams launches.