7repos it can see
- kirvo-app-finaltoday
- marlow-mainyesterday
- not here
- waypoint-web-v23d ago
- nimbus-cli6d ago
- gridwork-templates2w ago
- not here
- shopwell-shopify-theme1mo ago
- kirvo-sync1mo ago
- not here
- not here
- not here
Close your laptop and walk away. Panoma is the front door to every project on your disk — and it knows which one you were in, which one is broken and which one you never pushed.
Panoma · the local catalog of your projects — intelligent, always learning, for you and your agents
$ npx panoma up ~/Desktopany folder · Desktop in this example · ready at localhost:4173
$ npx panoma up ~all your projects
One question
What's the front door to your projects?
Answer it out loud before you read on.
Five seconds looking for an answer you didn't have.
GitHub only opens what you pushed. Your editor opens one project. Panoma opens all of them — and tells you which one you were in, which one is broken and which one never left this disk.
A superintelligent front door. That's panoma.
Ten seconds
Panoma featureProject memory
The most advanced memory for your projects.Panoma has it.
It updates live and your agents read it.
Panoma's brain creates five independent project memories. Then Claude Code, Codex and Cursor fly through the network on different paths and connect to every project.
Panoma featureTwin
Twin learns how you decide.And guides all your agents.
The obvious substitute
GitHub only knows what you pushed.Panoma knows everything you've built.
12projects you actually have
- KirvoTypeScript94
- MarlowGo88
- kirvo-landingReactnever left this disk
- WaypointReact79
- NimbusPython71
- GridworkTypeScript66
- marlow-panelReactnever left this disk
- ShopwellJavaScript38
- kirvo-syncGo61
- trace89Pythonnever left this disk
- appstore_screens_v3JavaScriptnever left this disk
- harbor-tempRustnever left this disk
healthstackwho touched itunpushed work
5
invisible to GitHubNot because you hid them. Because you never pushed them.
sample data · yours come from your own disk
Panoma featureAgent context
Your agents read AGENTS.md, CLAUDE.md, GEMINI.md or copilot-instructions.md before anything else. Panoma keeps what they read true.
Codex, Cursor and the rest
AGENTS.md1,240 tokens · read at the start of every session
# Project guide
Deploy with npm run deployscript removed in March
Auth lives in src/auth/session.tsfile no longer exists
Start with pnpm dev
kept fresh by panoma
<!-- panoma:begin -->
stack: React · TypeScript · Postgres
commands: install pnpm install · start pnpm dev
dependencies: 12 direct · 2 with security advisories
open tasks: 3 — claim them over MCP
<!-- panoma:end -->
Cursor added 3 lines yesterday. Panoma noticed and told you.
- It catches the instructions that stopped being trueAGENTS.md says
scripts/deploy.sh; that script vanished in March. Panoma checks the real project and flags the stale line. - It keeps the context current without you touching it
panoma md initkeeps stack, commands, advisories and open tasks current. Your own writing stays untouched. - You know which agent changed the rulesWhen an agent signs an AGENTS.md change, Panoma records its name and date on the project page — no git archaeology.
With several agents, Panoma is their shared memory: claimed work locks, the log travels to whoever arrives next, and the facts you approve reach every agent's first turn.
Panoma foundationLocal by design
Where your data lives
All of this happens inside your computer.Panoma has no server to send anything to — everything below follows from that.
This machinestays here
There's no account to create.Panoma runs on your machine and keeps what it learns in a file inside your home folder. There's nobody to sign up with, because there's nobody on the other end.~/.panomaThis diskstays here
The scan never touches the network.It reads the folders and the git history already sitting on your disk. That's why it works exactly the same on a plane.folders · git historyThe index cardstays here
Your code and your credentials stay where they are.Panoma keeps the project's index card — where it lives, what it's written in, when you last touched it, what is broken — not its contents. What's inside only moves if you connect a model and ask it to.path · stack · last touch · what's brokenThe packetscan leave
Connect nothing and the only thing that leaves is public package names.To find out whether your react is current, someone has to ask npm about “react”. That happens when you ask for it, and once every twelve hours so you don't have to. Nothing of yours travels in that question.npm · “react”If you connect a modelcan leave
Whatever you ask it to describe travels to that provider.Panoma brings no model of its own: it uses yours, with your key. When you ask it to describe a project, that project's README and commit subjects go to Anthropic, OpenAI or whoever you set up. Nobody turns it on for you: connect nothing and it never happens.your key · the project you pick
Prove itSee for yourself: pull the wifi and scan again. Same result.wifi off · same catalog
What's the front door to your projects?
Now you have an answer. And it's one command away.
Start with one folder: the catalog comes up, fills itself with what it finds — what's there, what's broken, what you never pushed — and waits in your browser. Nothing gets installed and nothing of yours leaves the disk. From then on the next git clone shows up on its own.
$ npx panoma up ~/Desktopjust the Desktop
$ npx panoma up ~your whole disk