Skip to content
How it works

A fix session, step by step.

Every fix moves through the same five steps, and anyone on your team can drive them. The model researches and proposes, the contributor decides, your host runs the checks, and an engineer reviews before anything merges.

One fix session

Five steps. Anyone can run them, and an engineer has the last word.

  1. 01DescribeAnyone describes it, or a ticket, signal or log spike opens it.
  2. 02InvestigateThe model reads the repo with read-only tools.
  3. 03ReviewThe contributor reads a staged diff. Nothing is written yet.
  4. 04VerifyThe patch is applied and your checks run.
  5. 05ShipA pull request opens. An engineer reviews and merges.
acme/storefrontfixroom/coupon-null-percentExample session

Done by you, or a signal

Say what the customer sees.

Write the symptom in plain language, or let a signed webhook, a log threshold or a customer ticket open it. Signal and log text is passed to the model as untrusted evidence, never as instructions.

Checkout returns a 500 when a customer applies a coupon that expired yesterday. It started after Tuesday's deploy.INCIDENT · LOCKED WHILE A PATCH IS OPEN
  • Duplicate failures collapse into a count before any rate limit
  • Per-source and host-wide incident ceilings
  • Refusals are kept in memory, not written as rows

Done by the model, on your host

Read-only research, then one answer.

Up to twelve research rounds with grep, git, list_dir and read_file, all confined to the workspace. Then one final reply with no tools.

grep      "percent" src/billing      4 matches
read_file src/billing/applyCoupon.ts lines 1–58
git       log -n 5 -- src/billing    a91c2e0 coupons: soft-expire
read_file src/billing/coupons.ts     lines 40–77
edit_file src/billing/applyCoupon.ts staged, not written
  • No bash tool exists to approve
  • Paths that leave the workspace are refused
  • Fixroom's own data directory can't be reached

Done by you

Review the proposed patch.

Edits come back as a unified diff, and nothing is written yet. Applying it writes every file or none. Each file must still match the version the patch was made against.

src/billing/applyCoupon.ts+3 −1
@@ -21,7 +21,9 @@ export function applyCoupon(cart, code) {   const coupon = findCoupon(code)-  const discount = coupon.rule.percent+  // A soft-expired coupon has no rule: treat it as no discount.+  if (!coupon?.rule) return { ...cart, discount: 0 }+  const discount = coupon.rule.percent   return { ...cart, discount }
moves this example to Verify
  • Edit the patch by hand before you apply it
  • A hand edit adds a Co-authored-by trailer
  • Reviewed side by side in a diff editor

Done by the host

Run your own checks.

Fixroom runs the project's test, lint, build and typecheck commands and attaches the output to the session. The commands can't see Fixroom's settings or tokens, and they get a scratch data directory.

$ npm test -- src/billing
✓ applyCoupon › applies a live coupon
✓ applyCoupon › expired coupon gives no discount
✓ coupons › soft-expire keeps the code reserved
$ npm run typecheck
✓ no errors
  • Fixroom's own settings and GitHub tokens are removed from the environment
  • Autofix runs in its own git worktree, never your checkout
  • After a set number of failed tries, the incident is quarantined

Done by you, merged by a person on GitHub

Approve, push, open the pull request.

Commit, Push and Pull request are one click each. The author is the Fixroom App's bot and the committer is you. Trailers record who approved the change, because a rebase rewrites the committer.

fix(billing): treat a soft-expired coupon as no discount

Author:    fixroomai[bot]
Committer: you <[email protected]>

Approved-by: you <[email protected]>
Fixroom-Session: <session id>
  • Pushes with your GitHub token, never a force push
  • The default branch is never pushed directly
  • Commit, push and PR each leave an audit row
The loop

Each step names who does it.

Most coding tools stop at "here is a suggested change." Fixroom is built around what happens next. The model only does research and proposes changes. Every step that changes something belongs to a person or to your host.

Your AI model · only the calls you configure01DescribeAnyone, or a signalSays what the customersees, in plain words.02InvestigateThe agentReads the code, changesnothing. Proposes a fix.03ReviewThe contributorReads the proposed changeand applies it.04VerifyYour serverYour own checks runon the applied change.05ShipThe contributorOpens the pull request. Fixroomhas no way to merge it.Your serverReports inTickets, chat,errors, peopleTo GitHubAn engineerreviews, merges
People decideThe agent proposesYour server runs itThe route a fix takes

Fixroom · Sheet A-1 · How a fix moves · Business view, not to scale

01

Describe

A plain-language symptom, a signed signal, a log watcher crossing its threshold, or a customer ticket.

Anyone / signal
02

Investigate

An OpenAI-compatible model reads focused repository context through read-only tools and stages edits.

Model
03

Review

A unified diff, checked against the files it was written for. Nothing is written until the contributor applies it.

Contributor
04

Verify

The project's own commands run against the applied patch. Their output stays with the session.

Host
05

Ship

The contributor approves the commit and opens the pull request. An engineer reviews and merges it on GitHub, under your branch protection.

Contributor · Engineer
Contributors

Who can do what.

A fix doesn't need an engineer to write it. It needs an engineer to review it. Fixroom's roles are built that way.

WhoAccountWhat they do
QA, designers, product managersDeveloper roleRaise tickets, start fix and improvement sessions, read the staged diff, run the checks, open the pull request, or press Solve to have Fixroom take an investigated fix to a pull request on its own
Support teamReviewer roleFile and triage tickets, group duplicates, draft replies to customers
Customers, anyone in your Slack or DiscordNoneReport through a help desk, the support mailbox, a chat thread or the in-app widget
EngineersAny role, or noneReview the pull request on GitHub, with the tests run and the fixroom/ai-review check on it, then merge
What keeps it safe. Each contributor works through their own GitHub account and needs write access to the repository. Fixroom never pushes to your default branch and has no merge operation, so with branch protection requiring a review, nothing reaches main without an engineer. Verifying a fix runs your project's tests on your server, so give the Developer role to people you'd trust with a CI runner.
Autonomy

Every level is opt-in, one step at a time.

Patching, delivery and operations are three separate settings. Turning on pull requests doesn't make Fixroom take more risk. The defaults below are what a fresh install does.

FIXROOM_AUTONOMY_LEVEL

Patching

  1. A0A signal opens the incident. A person does everything after that.
  2. 1Nothing patches on its own until you raise the level.default
  3. A1The ceiling: the agent applies its own patch in an isolated worktree and verifies it there. It still never pushes.
  4. gateA change above your level stops in awaiting_human.
FIXROOM_DELIVER_PRS

Delivery

  1. offThe agent doesn't push or open pull requests.default
  2. onPushes and opens a PR after citations check out. The AI reviewer posts one COMMENT review. A person merges.
  3. capOpen pull requests are capped, and approvals faster than the estimated read time are flagged.
FIXROOM_OPS_AUTONOMY

Operations

  1. B0Nothing watches the release.
  2. B1Observe and report. It has no authority to act.default
  3. B2Recommend rollbacks. This is how you find out a threshold is wrong before it acts on its own.
  4. B3Redeploy the previous artifact without asking. This changes the image tag, never the code.
The kill switch is checked at every stage boundary. If it's engaged through FIXROOM_KILL_SWITCH=true, nobody can release it through the API.
Get started

Run it on your own server.

Fixroom is proprietary software from Barox Labs, licensed per developer. Every plan comes with a written licence, the free one included.

  • ServerDebian or Ubuntu
  • Repositorieson GitHub
  • Model endpointOpenAI-compatible
  • Licencefree up to 3 developers
  1. 1

    Ask for a licence

    Tell us how many developers you have. Community is free for up to three, with every feature.

  2. 2

    Install it on your server

    We send you the Fixroom release and its install and update scripts for a Debian or Ubuntu server. Or we run it for you on Cloud.

  3. 3

    Create the owner and connect GitHub

    The first run asks for the owner account, then helps you connect GitHub and pick repositories. Fixroom asks for the AI provider when you start your first fix.

No benchmark figures yet. The evaluation baseline hasn't been recorded, so this page quotes no latency, quality or cost numbers.