Write.
temper · v0.1.0
From first draft to landed change.
Open source · Self-hosted · Agentic
Say how you work. Agents do the work. Code holds the line.
fabrig is a reliable, scalable and flexible agent-based software factory. Describe how you build and temper sets itself up that way, from one person approving every change to goals that land on their own.
Linux and macOS
$ curl -fLo temper https://fabrig.ai/v0/$(uname -s)-$(uname -m) && chmod +x temper && ./temper box
Open this link in a browser on this machine.
http://127.0.0.1:8367/…
One binary, a whole deployment on loopback. Try the playground with no account, or sign in your own model.
x86-64 Linux · Apple Silicon · needs git and ripgrep
ReliableEffects are made once.
ScalableA tree is proved once.
FlexibleYour process is configuration.
Open sourceMIT, self-hosted, one binary.
Agent-driven configuration
Tell it how you work.
temper’s configuring agent turns your words into settings, or says what it can’t do yet. Nothing applies until an owner accepts. How configuring works
Pair
you say
“I stay in the loop. An agent makes the change, and nothing reaches main until I’ve approved it.”
temper proposesillustrative
temper enforces
- main: CI passed, up to date, one person’s approval
your agents follow
- Ask before touching anything unrelated
- produce
- check
- repair
- you approve
- exact-commit merge
Team
you say
“Agents review everything, then one of us signs off. Anything under payments/ needs two of us.”
temper proposesillustrative
temper enforces
- main: CI passed, up to date, an agent’s review, one maintainer’s approval
your agents follow
- Flag changes under payments/ for a second person
it can’t say this yet
- Two approvals for one path. Landing rules cover branches, so the nearest is the rule above.
- produce
- check
- review
- repair
- one of you
- exact-commit merge
Stock
you say
“Nothing yet. What do you do by default?”
temper’s defaults
temper enforces
- Every branch: CI passed, up to date, an agent’s review
- A weekly spend for each project
your agents follow
- Your repository’s AGENTS.md
- produce
- check
- review
- repair
- resolve
- exact-commit merge
As fabrig builds itself
you say
“A person writes a design draft. One goal per draft, on its own branch. Designers first, then coding agents. It lands on main whole.”
temper proposesillustrative
temper enforces
- Goal template: a coordinator, on a branch of its own
- Goal branches: no CI, one merge at a time
- main: CI passed, up to date
- A model per role, the strongest where judgement is dense
your agents follow
- Design lives beside the code
- Push early, finish with a list of what’s left
- draft
- plan
- produce
- check
- repair
- exact-commit merge
- verify
The path is yours. The line isn’t.
A modelA personCode
Who is woken and what a person signs off are settings. A merge tool is never an agent’s.
Built by its own prototype
352 changes landed on main in the last 24 hours. Two things need a person.
Changes merged per hour, into main or a trunk. The last 24 hours are brighter.
- merged into a trunk, 24 h
- 1,040
- runs, 24 h
- 1,296
- ready to landed, median over 48 h
- 8.5 min
- landed with no rejection, 48 h
- 91%
One way of working, on one disciplined repository. What that does and doesn’t prove.
The factory
Prove.
a lab · direction
Automated QA.
Run.
ops · hearth first
Automated deployment and operations.
temper is the part you can run today. jig, the engine under it, carries all three.
Built for teams that hold a strict engineering bar.
A tool can enforce discipline. It can’t supply it. Manifesto · Hard questions