Nothing to install first
Mavambo carries its own Python. No runtime to match, no version to pin, no environment to repair. Install it and it works.
My code, your code, our code, their code — it doesn't matter.JUST START BUILDING.
Windows 10 & 11 · 64-bit installer
Inside Mavambo
The route is handled in auth/middleware.ts, which already wraps every request, so the limiter belongs there rather than on the route itself.
I’ll use a token bucket keyed on IP and account, since keying on IP alone lets one attacker lock out a shared office, and cover both cases with tests before touching login().
Most of it went on reading audit/ — 47 files, 186k tokens across nine turns. The remaining 18k was the write and its tests.
The signup route is behind a different middleware chain, so the limiter would never run there without moving it.
NEEDS YOUR DIRECTIONMoving it changes behaviour for three other routes. Tell me to proceed, or point me at a narrower fix.
Why this one
Mavambo carries its own Python. No runtime to match, no version to pin, no environment to repair. Install it and it works.
Every command it wants to run and every file it wants to write stops and waits for you — until you tell it not to. Approval or Auto is a dropdown in the composer, switchable mid-session.
Live token and cost tracking on every session, turn by turn. On DeepSeek it also meters what is left of what you topped up. You never find out afterwards.