Planner, issues, docs, chat and a virtual office — folded into a single keyboard-first workspace. Local-first, so every action lands the instant you make it. Nothing to tab between.
Drag an issue onto the calendar and it becomes a block of real time. The ember line is now — everything above it already happened.
Every column, filter and status is one keystroke away. No modals, no save buttons, no spinner between you and the change.
Every issue, document and meeting has a thread. Nothing gets buried three channels deep in a tool that doesn't know what you're building.
Real-time cursors, history on every keystroke, and links that resolve into live issue previews as you type them.
Walk your avatar across the room and audio fades up as you get close — the way it works in a real office. Drag yourself around and see.
Mentions, review requests, assignments and calendar changes land in a single queue you can actually finish.
Pushed the fix for the scheduler drift — we were rounding now() to the minute before the diff.
That explains the off-by-one on ENG-214. It's blocking my planner work — can I pull it into today?
Take it. I moved the review to 15:00 and dropped a block on your calendar.
✅ 2RFC-018 · Jules Rey, Mika Kern · Draft
The planner must produce the same layout for the same inputs on every machine. Today it does not: we sort blocks by insertion order, so two clients that receive events out of order render different days.
Proposal: sort by (start, duration, id) and resolve collisions with a stable lane assignment. This removes the last source of non-determinism in the day view.
Open question — keep the optimistic local write, or wait for the server tick? See ENG-214 for the measured cost of each.
MikaAnaScheduler drifts by one tick under load — blocking the planner rollout
Deterministic scheduling — Jules added a lane-assignment section
“…that explains the off-by-one, want to pair on it?”
Jules Rey rescheduled · 45 min · Studio
fix(scheduler): stable lane assignment for overlapping blocks
Meridian writes to a local database first and reconciles in the background, so nothing waits on a round-trip. The numbers on the right are being measured on this page, in your browser, right now.
Close an issue in Meridian, it closes on GitHub. Move a milestone on GitHub, it moves here. The sync is bidirectional and it does not lose your comments.
Open source, free for teams under ten. Bring your GitHub, keep your data, host it yourself if you want to.