Claude CodeCodexCursorGemini CLIOpenCode for shippinga feature in 2 hours.an MVP in one evening.a fix in 45 minutes.a landing page over lunch.a demo by the deadline.
Set the timer. One skill gives your agent a clock, one locked deliverable, and a gate that says no to everything else until a stranger can click a URL. The Habitat night, inside the editor you already build with.
Works in Claude Code Codex Cursor Gemini CLI OpenCode and any agent that reads a SKILL.md.
600+ people · 200+ MVPs · 8 cities · 4 countries · free, open source, local

| # | Hop | What happened | Gate |
|---|
Two hours, replayed live · every hop gated · nothing leaves your machine
Why a timer
Focus is a container, not a trait.
If you do your best work when a clock is running and someone is waiting to see the result (hi, ADHD brains), this is that container, taken from 200+ Habitat nights and put inside your agent. You pick the timer. The bunny does the rest.
2 hours · 45 minutes · an evening · a hackathon deadline. Any window works.

01
One deliverable
One sentence a friend can repeat
You lock one sentence. Everything else that comes up mid-build is parked in backlog.md, not lost. The backlog remembers so you do not have to.
02
A clock that talks
Four hops, one window
The bunny splits your window into lock, build, ship and roast, and speaks up when you drift or go quiet. "Behind pace" is a fact, not a feeling.
03
Done is a URL
localhost does not count
Not "almost", not a demo on your machine. When the timer ends, either a stranger can click it or it did not ship. Then the roast says what was true, and what one move comes next.
One skill, every hop
One skill. Every hop.
Say it in plain words. The agent builds, the bunny paces, and the gate says no where a prompt would have said sure. Each card is one thing you can say mid-build and what happens next.
- lock_idea · rejects a vague ICP
- ship · refuses localhost
- next_hop · will not skip a hop
- check_scope · parks it in backlog.md
- sprint_status · on pace · behind · overtime
- start_sprint · solo · team · event · any hours
- roast · rubric, event addendum
- ship_log · everything that hit a URL
- lock_idea · rejects a vague ICP
- ship · refuses localhost
- next_hop · will not skip a hop
- check_scope · parks it in backlog.md
- sprint_status · on pace · behind · overtime
- start_sprint · solo · team · event · any hours
- roast · rubric, event addendum
- ship_log · everything that hit a URL
Why it works
The container, not the advice.
AI removed the barrier to building, not to finishing. Agents are infinitely patient and infinitely agreeable, so they help you build forever. At Habitat nights the magic was never the advice. It was a timer, a locked scope, and a room waiting to see what you made.
agent alone
Still building.
Infinitely agreeable. Says yes to dark mode. Calls localhost a demo.
agent + bunny
A URL when the timer ends.
Four hops, one clock. Says no to dark mode. Refuses localhost.

The burrow
Always one hop ahead.
Everything the bunny knows lives in .habitat/ next to your code: the sprint, the backlog, the ship log. Human-readable markdown. Delete the folder and the bunny forgets everything.
What it costs
No cohort. No retainer. No equity.
The ritual that made 200+ people ship in one evening is a set of markdown files and a tiny local server. It runs where your agent already runs, and it does not phone home.
what "someone who keeps you honest" usually costs
- Founder coach$300 / hr
- Startup cohort$2,500
- Accelerator7% equity
- Accountability app$19 / mo
- Hackathon mentorfully booked
- A system prompt that says "be strict"ignored by hop 2
with habitat-bunny
free · MIT · local
No backend, no account, no API key. Nothing leaves your machine.
Event mode · for organizers
Run your whole hackathon on a tool every participant installs in one line.
Tell the bunny you are at an event and paste the brief. From then on the ritual bends to your event, not the other way around.
The clock is the deadline.
Not four hours from now. The real submission time, split into hops that end before it.
The grill checks the theme.
Ideas get locked against the brief, so nobody spends the night on something the judges cannot score.
Ship checks the requirements.
Repo link, demo video, team slide: the ship hop refuses to close until every submission item is there.
The roast uses your rubric.
Impact, feasibility, demo, originality: whatever your criteria are, the roast scores against them, honestly.
Set up
Give your agent a timer.
Paste one line into the agent you already build with. It reads the setup notes, installs the skills, runs /setup-habitat, and hands you back three things to try. Then name a timer and one deliverable.
What happens: the agent picks the skill route for your editor, never installs both, runs /setup-habitat once in your repo, and asks before adding the optional MCP gate. Nothing is sent anywhere. Then say "ship sprint, 2 hours, one feature".
Claude Code
pluginA managed bundle of exactly the promoted skills. Type both lines.
/plugin marketplace add ycanerden/habitat-bunny
/plugin install habitat-bunnyCodex, Cursor, others
skills.shWrites files you own and edit. Keep setup-habitat selected.
npx skills@latest add ycanerden/habitat-bunnyThe MCP gate
optionalMakes the no a tool, not a suggestion. Sits next to either route.
# Claude Code
claude mcp add habitat-bunny -- npx -y habitat-bunnyThe two skill routes are exclusive: pick one. Then run /setup-habitat once per repo. Add the gate to Cursor
One hop at a time.
Set the timer, lock the sentence, ship the URL, take the roast. Then do it again tomorrow. That is the whole ritual, and it fits in the editor you already have open.
Want a Habitat night at your company or in your city? Get in touch
600+ people · 200+ MVPs · 8 cities · 4 countries