Your setup docs, tested from a clean machine
Your README, proven on a clean machine.
Scroll to meet the crew
Your setup docs, tested from a clean machine
HUMBLE follows your setup docs on a brand-new machine, the way your next teammate will. It fixes the steps that break, proves every fix by doing the whole setup again from zero, and hands you a README that works.
[recorded run] acme-shop demo · no sign-in
A blue thread stitches every step. Pink crack = break. Blue stitch = fix. Taut replay = verified. Every command, failure, diagnosis, fix and duration comes from the real recorded run.
Numbers from an audit of 31 public repositories pinned to exact commits. See the audit
Docs drift. A version moves on, a service gets added, a step lives in someone's head.
The newest teammate finds out on day one, alone.
Six agents do the work. IBM Bob steps in when the rules can't explain a failure.
Scout · reads the repo
Reads the docs next to what is actually true: manifests, lockfiles, compose files, CI and code.
Planner · sequences the run
Turns the prose into the exact commands a newcomer would run, in order, and flags where docs and code disagree.
Runner · runs on a clean machine
Runs every step on a brand-new machine. Nothing installed, nothing assumed.
Doctor · diagnoses and fixes
When a step breaks, finds out why. Known causes get known fixes; the rest go to IBM Bob.
Verifier · proves from zero
Throws the machine away and replays the repaired guide from zero. A fix only counts if it passes here.
Scribe · rewrites the README
Writes the smallest README change that makes it true, with the evidence for every line.
Every number here comes from recorded runs you can open and replay.
Every card is a real run you can open, step by step.
Open the auditThe README said npm install then npm run dev. On a clean machine that broke five times. Drag to see the four lines HUMBLE changed in the README, plus the MongoDB version it wrote down.
The README runs prisma migrate deploy but never starts PostgreSQL or sets DATABASE_URL. A rule caught the variable; IBM Bob found the missing database. Replayed from zero in 63 s.
The README asks for Python 3.10; the project needs 3.12, and ./manage.py isn't executable in the clone. HUMBLE fixed the version and the command, then replayed all three from zero.
No silent failures. Every stop becomes a clear next step, and every stop makes the next run smarter.
The exact README line, the command, the error and every fix it tried, in the run's report.
An API key, a paid service, a login. 12 of 31 repos are fixed up to that one step and wait on you.
Today's stops are tomorrow's automatic fixes. IBM Bob's fixes already became free rules.
[recorded run] maitraysuthar/rest-api-nodejs-mongodb: bcrypt and the MongoDB placeholder fixed, 1 step left for you · sahat/hackathon-starter: MongoDB started for you, 4 steps flagged for the maintainer with the failing line.
Paste a public GitHub repo. In a few seconds HUMBLE shows where its docs and its code disagree, without running anything.
DR.BO. When no rule recognises a failure, Bob reads the repository and returns a structured fix. HUMBLE refuses anything that would change the application itself and keeps it as a suggestion for the maintainer.
Guide mode. A newcomer switches Bob to Guide mode and gets walked through the verified steps on their own machine, one at a time.
Lens. Circle an error anywhere on screen. If HUMBLE has already proven a fix for it, you get that fix instantly; otherwise Bob explains it.
Your README, proven on a clean machine.