Run more AI agents. Keep your PC quick.
A dozen coding agents start more tests and builds than a CPU can run, and everything you
type into starts to lag. Keel lets their go test -race wait while your apps go
first, keeps the servers they started quick, and changes nothing until the PC is under
pressure.
Not out yet: one e-mail when it is, nothing else. Every install will start with 14 days of Pro, then stay on Free unless you buy it. No account.
keelctl bench --ab run. The receiptEvery process gets a lane.
A lane comes from Keel's built-in rules (Go, Rust, C and C++, Node, Python, .NET, Java, databases, and the agents themselves), your own rules, the process tree, and the window in front. How hard Keel acts depends on pressure: the CPU, and how late a normal thread wakes when it asks to, which is the stutter you feel.
- Normal
- left as Windows has it
- Lowered
- below-normal priority: waits for your apps
- Quiet
- idle priority, low memory and disk priority, efficiency mode
- Fenced
- quiet, and kept off the CPUs Keel keeps for you
| Lane | What | Steady | Busy | Strained |
|---|---|---|---|---|
| Responsive | servers, dev servers, databases, the window in front | Normal | Normal | Normal |
| Flexible | agent work no rule names, once it uses half a core | Normal | Lowered | Fenced |
| Background | tests, races, builds, compilers | Lowered | Quiet | Fenced |
| Untouched | anything no agent started and no rule names | Normal | Normal | Normal |
Steady, Busy and Strained are how hard the PC is working: the CPU, and how late a normal thread wakes. Work that waits three seconds without running gets its priority back for five, so a build never starves.
Don't take our word for it. Check the receipt.
- 1
More work than CPUs. Spinning tests, one and a half per logical CPU, on top of the agents already running on the PC.
- 2
Steering on, then off, in turns. Six turns of 20 seconds, so the load drifts across both sides alike.
- 3
Both sides of the trade. What you get (commands start, threads wake) and what the steered work loses. It yields; that is the cost.
Run it yourself: keelctl bench --ab. One machine so far (i7-11700K, 16 threads, Windows 10, not hybrid). Across runs the steered work got 21% to 56% less done; your own CPU work got no faster.
- machine
- i7-11700K, 16 threads
- cpus it ran on
- 14 (2 kept for you)
- load
- 21 spinners + the agents
- turns
- 6 × 20 s, on/off
| on | off | |
|---|---|---|
| command start, p50 | 110 ms | 1,335 ms |
| command start, p90 | 137–250 | 2,277–8,262 |
| late wake, p99 | 3.6 ms | 21.7 ms |
| your 10 ms of work | 10.5 ms | 10.4 ms |
It puts everything back.
Nothing outside your session
Not Windows, not the shell, not the terminal, not a process someone raised above normal. No administrator rights, no driver, no service.
Never fights you
Change a priority Keel set, or let the program change it, and it's yours from then on: Keel lets it go and puts its other changes back.
Nothing kept past quitting
Quit, uninstall or upgrade and everything is put back. Killed, a journal puts it back at the next start, including what steered work started.
Nothing leaves your PC
No telemetry, no account, no automatic installs. A Pro licence is checked offline; a subscription renews by sending its licence, which names only its order.
keelctl: what Keel sees, as text.
Your agents can ask why their build is slow without a screenshot: every command has --json.
Free for two agents. Pro for every one.
Every install starts with 14 days of Pro. Then it stays on Free unless you buy Pro: nothing stops working.
Free
$0for good
- Steers the work of your two oldest agents
- The built-in rules
- Relief for starved work, keelctl, everything put back
- No CPUs kept for you
- No rules of your own
Pro
$9a month · or $79 a year · or $129 once
- Steers every agent's work
- Keeps the CPUs you choose for you
- Your own rules, beside the built-in ones
- One licence for your own PCs
- Full refund within 14 days
Questions, answered.
Which agents does it know?
keelctl missed lists busy work Keel leaves alone, so a rule of your own can name it.Can my agents ask Keel why their build is slow?
keelctl answers in text or JSON, and keelctl mcp is an MCP server, so Claude Code and other MCP clients can ask what Keel lowered and why, what is loading the PC, or switch steering off for a timing run: claude mcp add keel -- "%LOCALAPPDATA%\Keel\keelctl.exe" mcp.Does it need administrator rights?
%LOCALAPPDATA%\Keel, steers only processes in your own session, and runs from the tray.