rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Provenance tree for coding agents: where you are, why, and what was already decided
Originaltext des Herstellers
Skills, die der KI diese Art Arbeit beibringen; sie funktionieren zusammen mit diesem
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Listen sind nach einem Nutzungswert (von 100) aus diesen Teilen sortiert
| Beliebtheit | 4/80 | GitHub-Sterne oder wöchentliche Downloads: der größere Wert zählt 60, der kleinere 20 |
|---|---|---|
| Aktualität | 12/12 | Volle Punkte für Release oder Codeänderung in 30 Tagen |
| Antwortet noch | 0/8 | Der Cloud-Endpoint antwortete bei der letzten Prüfung |
| Nutzungswert | 16/100 |
Qualität: 3/3 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung) · Schwung: Noch keine Daten (Nur im Tab Im Trend verwendet)
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
3/3 Prüfungen bestanden · Läuft auf deinem Computer
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Claude kann vivac noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
ChatGPT kann vivac noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
B · Andere in Entwicklertools, die mit ChatGPT funktionieren
Aus den meistgenutzten derselben Kategorie, nur solche, die per Adresse ohne Schlüssel verbinden
Claude Code kann vivac noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
Cursor kann vivac noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
VS Code kann vivac noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.
Laufen auf deinem Computer in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 20. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto JAAvila-Of bestätigt, dem das Repo gehört
Code zuletzt geändert: vor 12 Tagen
Nutzt Apache-2.0
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Nicht geprüft: nur npm- und PyPI-Pakete mit Version lassen sich prüfen
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/servers/jaavila-of-vivac)Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Noch keine Bewertungen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt vor 12 Tagen geändert, und die neueste Version (0.22.1) kam vor 16 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Rust auf deinem Computer.
In derselben Kategorie: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Dieser vivac | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Läuft wo | Wird auf deinem Rechner installiert | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | In der Cloud oder auf deinem Rechner |
| Braucht Schlüssel | Nein | Nein | Nein | Nein | Nein | Nein |
| Mit + in Claude hinzufügen | Nein | Nein | Nein | Ja | Nein | Nein |
| Basisprüfungen | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Lizenz | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Preis | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register |
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
A tree where every node knows which node it was born from.
*So that months later something can still answer “why are we here?”*
$ vivac why 4
Why we are here -> t4
g1 Ship the 2.0 API the first customer is waiting on it (4 open / 1 closed below) | v t2 Replace the cache adapter the session bug traces back to it (3 open / 1 closed below) | v t4 No test for expiry [closed] no way to reproduce the session bug ! the corpus run is what settled it = reproduced: sessions expire at 300s, not 3600
^^^ you are here
In parallel, still open (3): t3 Rate limiting is undecided d5 Retry policy: three tries, then fail loudly t6 Migrate the callers
t2 does not close until these close (1): t6 Migrate the callers
[What you get](#what-you-get) · [See it](#see-it) · [Install](#install) · [First five minutes](#the-first-five-minutes) · [Why one map](#one-map) · [Bring a project in](docs/MIGRATING.md)
I run eight projects in parallel — open source, work and my own — and five of them are large. Every time I came back to one I had to piece together what had been decided in it, and more than once I watched the agent change something we had already settled, because both of us had forgotten we had. What I had against that was manual: ending each stretch of work by asking the model for *a safepoint, so we can pick this up later*, or keeping a where_are_we.txt at the root of the project.
vivac is what replaced them, and it is still measured on those projects. That is the whole of its pedigree, and it shows in what got built: every mechanism here came out of a defect that had already cost me days, and every number on this page came off a real tree rather than a benchmark written to make a README look good.
The tree this project keeps of itself, 23 days in: 695 nodes, 315 of them closed, 176 standing decisions, 16 levels deep.
Three of those defects, and what each one turned into:
vivac done refuses, and says what is missing.open answers *what is waiting on you*, in that order, and stops at ten.--help.What I would not give up now is no single feature. It is looking at the tree of what was decided and why; picking a project back up with whichever model is at hand and having it know what the last one settled; and knowing where the work stands at any moment. In my experience that is worth more than anything else here, and I hope it serves you as well.
Issues are open, and I want to hear where it fails you. Pull requests are not open yet; CONTRIBUTING.md says why.
When you develop with an agentic AI, work spawns more work. Three hops in, you have lost the thread of what you originally set out to do.
It is not a memory problem: usually everything is written down. It is a provenance problem. What is written does not say what it was born *from*, and without that edge there is no way to reconstruct why you are where you are.
Measured on a real compiler: the path between the goal and the day's work
was six levels deep, spread across a chronologically ordered 8,853-line
tracker, 52 planning documents and 21 issues. The structure was temporal,
which is exactly the opposite of provenance.
Logbooks, decision records, issue trackers and session memory for agents all store the node. Where one of them stores the edge as well, it is a link somebody has to remember to add — so it is missing on exactly the node where nobody thought it would matter. Where it sits goes through them category by category, and says where each one is better than this.
The agent starts oriented, and nobody has to ask it to. A hook runs vivac session start when a session opens, so the first thing in its context is where you are, what has already been decided, and what not to touch:
$ vivac brief
vivac · project: demo · lane: main · 2026-09-21
GOAL g1 Ship the 2.0 API | |-- t2 Replace the cache adapter | why: the session bug traces back to it | `-- t6 Migrate the callers <== HERE why: the old adapter had a different signature
STANDING DECISIONS d5 Retry policy: three tries, then fail loudly
LAST VIVAC v5 · push · 2026-09-21 · bcdba21 you were about to: Migrate the callers
143 tokens · depth 3 · 0 parked
In tokens, that is the whole argument. A project keeping its state in three places was asked to pick up where it left off. A hand-written plan answered in 9,252 tokens. A memory system answered *“maybe”* in about 12,720, depending on which of two names for the project it resolved. The tree answered in 100. The brief carries a token budget because a context window is the one resource every session spends.
Nothing closes over what is still open. The one operation in the model that rejects, and it earns it: a run marked done over open findings took 26 days to be spotted once.
$ vivac done 2
t2 CANNOT close: 1 open closure condition(s)
t6 Migrate the callers
A run closes with its findings, not with its report. Closing it anyway leaves a trace: vivac done 2 --force
Every decision keeps what it turned down, and what it was judged against. --alternative holds the option rejected, --supersedes links a reversal to what it reverses, and --against records the rule or pillar that decided it — so a decision can be argued with a year later instead of guessed at. This project's own tree carries 176 of them.
An assumption that falls does not take its children with it. abandon marks the premise refuted and everything under it goes with it, except what you rescue — and what is rescued still hangs where it was born, because being born somewhere is not undone by that place turning out to be wrong.
It saves tokens, not all of them. Picking a project up took the tree 100 tokens where a hand-written plan took 9,252, and that difference comes back every time a session opens. The agent still reads files, still reasons and still explains itself, and none of that gets cheaper.
It does not make sure nothing is ever forgotten. No memory system can, this one included, because every one of them still runs on the model's judgement: *should I save this? is this a finding? do I need to read the tree again before I answer?* The best skill in the world, a hundred subagents or a hundred daemons move where that judgement happens, and none of them removes it. vivac hangs capture off the seams of the work rather than off that judgement, and still measures where it slips.
What is left over after that is why the tree is built to be looked at.
vivac web
The agent writes the tree, and you can read it at any moment without asking the agent anything. vivac web opens every project on this machine in a browser: which one moved and which has been sitting still, what changed in one while you were away, a node's whole lineage, and the whole tree. Its Agents page compares native versions across harnesses and applies an explicitly reviewed synchronization plan through the same operations as vivac agents sync. It is also where the Artifacts page connects retained deliveries to their producer and decisions referencing exact revisions. Checks, capture and restore use the artifact engine; downloads verify the selected revision before sending it as an attachment. Static HTML, CSS and JavaScript bundles retain all declared members as one revision and restore into a new directory. HTML revisions and bundles can open in a restricted browser preview separate from the Vivac session. See Artifact custody. This is where you see the state of each item for yourself, and where you catch what the agent let pass.
Four example projects, written by real vivac commands with tools/web-screenshots.py, which takes these pictures again whenever the pages change.
A server you start and that dies when you close it, bound to 127.0.0.1, reachable through a one-time key it prints. It has no functions of its own: anything a page needs is built on the command line first. → What the web is, and is not
**vivac was not