jycd25 / RerouteDay

# RerouteDay
A local-first calendar that plans your week from a baseline and adjusts the day when life interrupts.
You keep one template week, your **baseline**: the task slots and busy slots you want a normal week to have. Every real week starts as a copy of it. When the day goes off plan, you tell the assistant in a chat box next to the calendar, and it moves things with tested scheduling functions instead of guessing. Your data stays in a SQLite file on your machine.
Two messages, no editing by hand. "I'm starting now" is a direct action: the server recognises it and shifts the rest of the day on the spot, without a model call. The second message goes to the assistant, which picks the carve-out tool, splits the thesis block around the pickup, moves what follows, and says exactly what it did.
One week, as it happened, for a made-up grad student with a freelance client. Every change on it came from a sentence to the assistant or a click on a block:
- **Tuesday:** "Busy from 14:00 to 15:30, dentist" carved the hour out and split the client block around it.
- **Wednesday:** "I'm starting now" at 08:40 shifted the rest of the day later, and "I didn't finish Spanish" carried the missed 30 minutes to the first blank gap.
- **Monday and Thursday:** a skipped gym session and a skipped reading block, each with a note the assistant will see next time it plans.
- **Friday:** the thesis block was tracked from Start to Finish and shows the actual time, then an advisor call pushed the afternoon later.
- **Hatched blocks** were never marked and became missed, so the record stays honest.
The week came from this baseline, the template every week starts as:
## Quick start
 [code] 
Or install it once and run `rerouteday` from anywhere:
 [code] 
Your browser opens on http://127.0.0.1:4820 once the server is up (pass `--no-open` or set `REROUTEDAY_OPEN=0` to skip that). Pick an assistant backend in **Settings**: the Claude Code CLI if `claude` is on your PATH, or an Anthropic API key. Needs Node 22.13 or newer.
From source:
 [code] 
Data lives in `~/.rerouteday/data.sqlite`. Set `REROUTEDAY_DB_PATH` to move it and `PORT` to change the port.
## Why
Most planners make you rebuild the week from scratch or let an AI rewrite your calendar freely. RerouteDay does neither:
- The baseline is the source of truth. A week is the baseline applied, then adjusted day by day. Nothing is replanned behind your back.
- The assistant can only act through a fixed set of scheduling tools (shift the day, carve out an hour, carry over unfinished work, apply the baseline). Each tool is pure, deterministic and unit tested. The model picks the tool; the code decides the result.
- Everything is local. The server runs on your machine, the database is a file you own, and the only network call is to the assistant backend you choose.
## What it does
- **Set up in one line.** Import a past week as your baseline from an `.ics` file or a Google Calendar secret iCal address, draw it on the Baseline