AI-life balance
Your AI life, measured.
One command turns activity across your coding agents into a clear view of your day and night.
Your AI life report
Your week has a pattern.
One view across the coding agents you already use.
Your agents worked for 31 hours. They needed 4h 12m of your actual attention.
↗ 2.1h more than last weekprotected
11:47pm: agents were still productive. Your correction rate was not.
See your AI day and your night together.
AI saved you 7.4 hours.
You gave 5.1 of them back by launching more work after your planned stop time.
Let them run. Don't supervise.
Two agents can finish without you. Your next useful check-in is tomorrow at 9:00am.
This would create a local boundary—not stop or kill your agents.Not another productivity cop
The boss sees output. This is for the human still awake at 2am.
Local content boundary
Read logs locally, keep counts and timestamps, and discard prompts, source code, outputs, projects, and paths before sync.
Life over usage
A billion tokens is not a win. An evening returned, a walk taken, or a task finished without supervision might be.
One experiment
No guilt spiral. Try two agents instead of five, protect one stop time, and see whether the work actually changes.
The short answers
AI-life balance, without the surveillance energy.
What is AI-life balance?
AI-life balance measures whether coding agents reduce human attention and protect time away from work—not merely how many tokens or tasks they consume.
Which coding agents does Afterhours track?
Afterhours currently reads counts from Codex app and CLI, Claude Code, and Gemini CLI. It detects Cursor and other installed coding agents while adapters mature.
Does Afterhours upload my prompts or code?
No. Your first report is created on your computer. If you connect Teeras, activity counts and timestamps sync for your history; prompt text, source code, model output, project names, and file paths stay on your computer.
How do I install Afterhours?
Run npx @teeras/afterhours. It shows when your coding agents worked, when you checked in, and whether those check-ins reached into the night—including activity from Codex desktop and CLI. Connect to web and mobile to see AI activity, sleep, and recovery—in one view.
Start measuring.
See when your coding agents worked, when you checked in, and whether those check-ins reached into the night—including Codex desktop and CLI.
npx @teeras/afterhoursConnect after your first reading to see AI activity, sleep, and recovery together on web and mobile.
Already measuring? Open Afterhours →