User Guide
For the person who runs flows: you give coding agents a task, a loop to work in and a budget, and Humanize drives them until the work is done or the budget is spent. Nothing here asks you to write Python; writing flows is the Writing Flows guide.
How this guide is built
- Get started and the Tutorials are lessons: follow them in order, every command written out, every step checked before the next.
- Everything else is a guide to one task: what it is for and what you need, a Try it short enough to paste, how the thing works, a worked example with every part of it explained, how to check it worked, what to do when it does not, and where to go next.
- Help pages, and the Reference, are for when you know what you want.
Get started
- Installation Humanize Desktop or the CLI, and one coding agent CLI signed in. About five minutes.
- Your first run Choose a flow, give it an agent and a budget, watch it fix a bug, and stop it.
- Security What to check before a flow touches work you care about.
New words on the way are in the Glossary.
Tutorials
Then take a whole piece of work start to finish. Each is one path, with real output at every step:
| Tutorial | You learn | Takes |
|---|---|---|
| Beat a benchmark | two agents taking turns, a task file, checking a result against cheating | an hour of you, hours of the machine |
| Port a project | an actor and a reviewer, a run that ends itself | about an hour |
| Build a coding agent | three flows in a row: idea, plan, build | an afternoon |
Ways to use it
| Where | Best for | |
|---|---|---|
| Humanize Desktop | an app on macOS or Windows | every epic in one window, with notifications |
hmz web | a browser, on any machine | the same page, and your servers' epics beside yours |
hmz | the terminal, in a repository | setting a flow up and talking to it at the prompt |
hmz exec | a script, or CI | runs nobody watches |
Everything else
While it runs
Agents and accounts
Where the work lands
After a run