Most workdays begin with a pile of unread things and a faint sense that something important is hiding in it.
Daybreak begins them with a painting.
Every weekday, a little before your day starts, it reads what happened while you were away: email, calendar,
tickets, docs and Slack. Then it writes you one calm page and leaves it on your new tab. It tells you what matters
today, who is waiting on you, which meeting deserves ten minutes of preparation, and what can safely wait until
Thursday.
Think of it as the colleague who gets in early, reads everything, and leaves a tidy note on your desk. This one never
asks for credit.
What's on the page
The brief opens with Push your work forward: the one or two moves that would make today count. It arrives with
the ticket numbers, names and deadlines already filled in, so you don't have to go digging. Next to it sits a yellow
starburst that says Let's do it. Press it and Daybreak starts on the work with you. We tried removing the sticker
once. It felt wrong.
Top to-dos are the loops you owe other people. Each one has a link back to where it came from, and a button that
hands the job to the assistant.
New updates tells you what moved in each thing you're working on since yesterday. Every item is numbered, carries a
status tag (Active, Awaiting reply, Needs you), and shows who's involved.
Your day lays out your meetings and points at the one worth preparing for.
Looking ahead asks what you'd like to work on tomorrow. Tomorrow's brief remembers your answer.
The brief opens as its own tab the first time you use your browser in the morning. To bring it back any time, press
⌥⇧B, click Brief at the top of the side panel, or right-click the toolbar icon and choose Open today's brief.
The rest of the day
Five minutes before a meeting, a small card slides into the corner of whatever page you're on, with Ignore,
Prep notes and Join. The prep notes are written ahead of time from your email, tickets and docs. They cover
what the meeting is really about, what's likely to come up, and what you might want to ask.
When someone is genuinely waiting on you, Daybreak may tap you on the shoulder. Gently. At most three times an hour,
and never in the evening.
If you're off in another app, both kinds also arrive as a regular system notification, with Join and Prep notes
buttons on the meeting one, so a page you can't see doesn't make you late. The card waits on the page for when you're
back. (On macOS, allow notifications for your browser under System Settings → Notifications.)
Open the side panel (⌥⇧D) and you have an assistant that already knows your week. You can:
- ask about the page you're reading, or about the project behind it
- have it draft the reply you've been putting off (it writes the draft and never sends it)
- turn a messy thread into a one-pager, a deck or a recap
- set up recurring jobs like "every weekday at 5:30, recap what I shipped"
What Daybreak will never do
- Send, post or change anything. Background work is read-only. Chat can write email drafts, and that's where it
stops.
- Ping you after hours. Pop-ups respect your work hours and a rate limit.
- Ask for an API key. It uses the Claude subscription you already have, through the Claude Agent SDK.
- Phone home. Everything lives in one folder on your computer. The only outside calls go to your Claude account,
the tools you've connected, and a museum (for the painting).
Getting started
You'll need Claude Code signed in with a Claude subscription (claude,
then /login), and Python 3.11 or newer. For a good brief, connect Gmail, Google Calendar, Google Drive and Atlassian
under claude.ai → Settings → Connectors. Daybreak uses whatever is connected and skips the rest.
1. Install the helper
git clone https://github.com/kiraa06/daybreak.git && cd daybreak
python3 -m venv .venv && .venv/bin/pip install -e .
.venv/bin/daybreak install
install does five things:
- copies Daybreak into its own environment in your data folder
- copies the extension there too
- registers it with every Chromium browser it finds (Chrome, Edge, Brave, Arc, Dia, Vivaldi, Opera, Chromium)
- starts the helper at login: a launchd agent on macOS, a systemd user service on Linux
- links
daybreak into ~/.local/bin, if you have one, so you can run it from anywhere
2. Give Daybreak its own sign-in
.venv/bin/daybreak login
A browser window opens. Sign in with the Claude account you use for Claude Code. Daybreak keeps this sign-in to
itself, so its background work can never log your terminal out, and logging in or out in your terminal never stops
Daybreak. (You can skip this step, and Daybreak will borrow your terminal's sign-in instead. It works, but if one of
its background calls refreshes a stale copy of the shared login, Claude signs you out everywhere.)
3. Load the extension. Open chrome://extensions (or edge://, brave://), turn on Developer mode, choose
Load unpacked, and pick the folder install printed. Keep the new-tab page when the browser asks.
4. That's it. If it's a weekday, your first brief shows up within a few minutes; otherwise it arrives on the next
weekday morning. You can also run .venv/bin/daybreak brief and open a new tab.
If the extension says it can't find the helper, run daybreak pair and paste the output into the extension's
settings page.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
