I built mokkan: reminders that follow you between Claude Code, Codex and terminal sessions

If you work in a lot of agent sessions, you've probably hit this: you tell Claude "remind me to check the flaky test later", or you create TODO lists in every project and eventually you forget. Every session starts blank, and the model only checks on something if it happens to think of it. I built mokkan as a small fix for that. It's Claude Code Mod and a CLI-tool that keeps one reminder list on a server. Every session asks the server what's due, instead of the model trying to remember. Behold, this isn't an agent-first functionality, but a human one, allowing us, the users to not alt-tab to various note taking apps for a simple TODO, or reminder. The skill teaches the agent to use the tool though :) In Claude Code, /mokkan opens a pane beside the transcript with your stack. A reminder that comes due shows up there as a toast; nothing gets injected into the conversation. Codex checks the same list at the start and end of each task through a skill, and any terminal sees it too. Push a note on your laptop, it's on your desktop a few seconds later. In Claude for Desktop the pane works too, but the platform differs a bit from Claude Code, so the experience is close but not identical. How it works in the CLI mokkan push "check the flaky login test" adds a todo mokkan in 2h "ask Maria about the release notes" schedules a reminder mokkan prints the list, mokkan pop finishes the top one Nothing closes until you say so A reminder stays lit until you acknowledge it, from any session. If a scheduled one comes due and nobody acks it within a few minutes, it's emailed to you. So notes don't silently disappear. How I built it The whole thing was built in Claude Code, with Opus 5.5 and later Fable 5.1. Of the 54 commits in the public repo, 47 are co-authored by Claude. The loop was the same for every feature: I describe what I want, Claude asks me the questions it needs answered, then writes a design spec and a step-by-step implementation pments the plan task by task with tests (vitest for the CLI, claude plugin test for the pane), and I review the diff and try the pane and the terminal UI by hand, since that part doesn't test well automatically. One thing I'd recommend to anyone doing this: Clamd` with every decision it made on its own,numbered and with the reason, separate from the decisions I made explicitly. When something feels off later, I can find the assumption behind it instead of guessing. The pane itself is a Claude Code mod: a small Typruns inside the session, sees its events and draws the pane. So it was built with Claude Code and for Claude Code. Cost The CLI and plugin are open source (MIT). The hosted server runs on prepaid credits: 50 free on signup, then €5 for 500. Adding a note costs 1 credit, an email costs 1 crly sent, and listing or acknowledging is free. You can also point it at your own server. Install /plugin marketplace add vicmpen/mokkan /plugin install mokkan@mokkan or for the terminal: npm install -g @vicmpen/mokkan-cli GitHub: https://github.com/vicmpen/mokkan Site: https://mokkan.dev Happy to answer questions. submitted by /u/Cl33t_Commander [link] [comments]