Plancia
Claude Code and Codex already write down everything they do, in files on your
disk. Nothing reads them together. Plancia does: one row per project tells
you what to do next, Resume reopens the conversation that wrote the task, and
a spoken recap of the day closes with what is worth doing. The rest stays
folded, one click away.
Website: plancia.
Local-first: no telemetry, no account, no server of ours. The only thing that
goes out is the work you explicitly hand to an agent, and it goes through the
claude or codex command already on your machine, under your own
subscription. No dependencies to install: Python 3 and its standard library,
Swift for the app.
Italiano
Every screenshot in this README is the app running on the demonstration archive
(tools/demo-data.py), never on anyone's real data.
The Mac app
Plancia 2.0 is a native SwiftUI app for macOS 26 or later: the system controls and the
Liquid Glass materials, a sidebar with six sections, the system search field in the
toolbar and an inspector on the right. No logo, no web page inside a window.
Memory as a map. Every note is a node, coloured by kind, and every project (or kind
of note, for the ones that belong to none) is an island with its name on the edge. The
links between islands are drawn as ribbons, so you see at a glance which projects share
what you know. Hover lights a note and its neighbours, drag a node and its island follows,
pinch or scroll to zoom. The physics runs off the main thread and stops by itself when
the picture is still.
Zoom in and the nodes carry a short human title instead of their file name:
Wood. Settings has a Style: System, or Wood, a modern take on the skeuomorphic dashboard
of the app icon. Mahogany boards in the sidebar and under the toolbar, solid brass for the
selection, warm paper for the content. Controls and glass stay the system's.
Light and dark, and text size on ⌘+, ⌘- and ⌘0:
The sections have their own pictures further down: Search,
Jarvis, All tasks and Projects.
What it reads
| source | where | what it gets |
|---|
| Claude Code sessions | ~/.claude/projects/**/*.jsonl | date, project, opening prompt, turns, tools, tokens |
| Claude memory | ~/.claude/projects/*/memory/*.md | project descriptions, [[wiki]] links |
| skills, plugins, routines | ~/.claude/skills, plugins, scheduled-tasks | what your Claude Code can do |
| GitHub | gh repo list, recent commits | repos, commits, real material for posts |
| local git | your code roots | branch, uncommitted changes |
| Codex sessions and goals | ~/.codex/sessions, goals_1.sqlite | the same, plus what Codex is stuck on |
| Claude Code task lists | ~/.claude/tasks/<session>/*.json | what is open right now, per session |
| session hooks | SessionStart, SessionEnd | which sessions are open right now |
Sources are never modified. Plancia reads them and stays out of the way.
See docs/NOVITA.md for what changed recently and why.
Install
The Claude Code plugin
One line connects Claude Code to Plancia:
claude plugin marketplace add nerln/plancia && claude plugin install plancia@plancia
Inside Claude Code the same is /plugin marketplace add nerln/plancia and then
/plugin install plancia@plancia. New sessions pick it up. The archive is
~/.plancia/plancia.db, created on first use. The plugin needs Python 3.9+ as
python3, on macOS or Linux; on Windows plancia install (below) stays the way in.
What it brings:
- The MCP server, behind a sentinel. Claude Code talks to a small process
that never touches the database. The real server runs behind it: if it crashes
or hangs, the sentinel starts a new one at the next call and repeats a read
that was cut off. A write that was cut off comes back as an error that says to
check before retrying, so a task is never written twice. Restarts go to
~/.plancia/sentinella-mcp.log.
- The briefing when a session starts, plus one line of warning only when
something is wrong: the archive cannot be read, the dashboard stopped (on
macOS it is restarted), the server fell over more than once in the last hour.
- The
plancia and riepilogo skills.
/plancia:briefing [project] links the folder you are working in, and the
session, to its project, then gives that project's briefing. For a folder
Plancia has never seen it lists the likely projects (from the git remote, then
from the words of the path) and links nothing until one is picked. A container
such as ~/dev is never linked./plancia:doctor reads the archive, starts the MCP server once and times
it, reads the sentinel's log, and repairs what it can.
Coming from plancia install: run /plancia:doctor. It finds the old
registrations (the plancia server in ~/.claude.json, the hooks in
settings.json) and, once you say yes, removes them and keeps a dated copy of
each file. If you work on Plancia itself, set codice in
~/.plancia/config.json to the path of your checkout and the plugin runs that
code, the same the dashboard runs.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
