Good things take time.
Make that time yours.
Your agent is working. Your next move is up to you.
Turn the wait into a little practice, right in your terminal.
curl -fsSL 'https://waitdojo.dev/install.sh' | sh -s -- --agent codexA little space for you.
Live, interactive demo
Temporary simulation. No repository access, no agent connection, nothing saved. Resets on reload.
Open the practice room- Made for your workflowCodex + Claude Code
- At home in your terminalmacOS · Linux · WSL2
- Your practice, your machineLocal by default
01 / A little perspective
The minutes add up.
One wait is easy to overlook. A week of them is a window for something worthwhile.
50minutes each workweek
10 min a day5 workdays
Small windows. Room for a little more practice.
Cumulative minutes over a five-day workweek
Start with your day
What does your wait look like?
Adjust the example to match your workflow.
Calculated here. Nothing saved or sent.
Arithmetic from your inputs, not a promise of time saved. Actual practice depends on the waits you choose to use.
02 / A better in-between
Stay in the flow.
Even when you wait.
No new window. No feed to fall into. Just one useful rep, alongside the work you already do.
- 01
Your agent starts working.
Passive hooks notice a lifecycle event without reading the work itself.
working - 02
WaitDojo recommends one rep.
A local policy considers available time, recent practice, goals, and weaker tracks.
recommend - 03
You complete one useful rep.
Practice in the sidecar and get a clear, activity-specific result.
practice → result - 04
Your agent needs you again.
The activity pauses, the pane collapses, and your original context is waiting.
return
When your agent needs you, your place is preserved. The work comes first.
03 / Small practice. Real presence.
A moment well spent.
Sharpen a skill. Stretch your thinking.
Choose what this little window becomes.
~30 seconds
Find your flow.
A short passage. A little more precision. Build command fluency with live speed and accuracy feedback.
Explore the live demo Focus, at your fingertips.Private Codebase Teachback
Get to know what you’re building.
Your agent prepares small, evidence-backed lessons from your codebase. You review and approve them. The questions and repository contents stay on your machine.
More time on your hands? Full chess games and longer poker sessions are always opt-in.
04 / Yours, by design
Your practice.
Your machine.
Your business.
WaitDojo only needs to know when your agent is working and when it needs attention. The work itself stays yours.
Read the privacy contract- 01 / What hooks see
- Events and timestamps.Lifecycle signals. Never prompts, code, commands, or agent output.
- 02 / Where practice lives
- Right where you are.Local by default, under
~/.codex/waitdojo/. The browser demo needs no account. The installed beta requires a claimed invitation and GitHub sign-in. - 03 / What leaves your machine
- You decide.Progress backup is opt-in. Required access checks send no practice content. Practice-content downloads happen only when you run
waitdojo chess download.
05 / Nothing to take on faith
A closer look, always welcome.
Published beta v0.2.6
Historical UI proof v0.2.4
Read the installer before you run it. Check the published release, signatures, and security boundary. The product source is private. The installation path is open to inspection.
“WaitDojo should earn trust with behavior you can inspect—not a wall of invented logos or adoption numbers.”
A few good questions
Before your
first rep.
No. It is a temporary simulation. It cannot read a repository, contact an agent, or save your demo progress.
Passive hooks record lifecycle event names and timestamps. WaitDojo does not capture prompts, source code, agent output, or command contents.
Only Typing Sprint, Quick Quiz, and offline Chess Tactics are in the normal short recommendation pool. Longer activities require a deliberate choice.
The browser demo needs no account. Invited-beta access requires a claimed invitation and GitHub sign-in. Practice data stays local by default; optional backup is one-way and is not cross-device sync. The published release requires access checks but does not force activity uploads.
WSL2 is supported when WaitDojo, tmux, and your coding agent run inside the same Linux distribution. Native Windows is not supported.
Your next wait is an opening.
Make room for
a better habit.
The installer is public. Beta access requires an invitation claimed with your GitHub account. Join the waitlist for an invitation.
curl -fsSL 'https://waitdojo.dev/install.sh' |
WAITDOJO_CAMPAIGN_BUCKET='unknown' \
WAITDOJO_BASE_URL='https://waitdojo.dev/releases' \
sh -s -- --agent codex
~/.local/bin/waitdojo