Know where you're building.

For when you and your AI both wonder, WTF did we just vibe code?

VibeCompass keeps a live memory of your repo: what exists, why it was built that way, what changed last session, and what your next model needs to know before it touches the code.

Get started Read docs

Free to start · Live on npm · Local-first files

How it works

Three steps from chaos to a usable handoff.

Point it at your project

Connect a GitHub repo or use the local package to create the project-memory files beside your code.

Let it build the map

VibeCompass turns the messy shape of the repo into domains, features, decisions, and file mappings your model can read.

Start the next chat with context

Claude Code, Codex, and Cursor get the handoff before they start suggesting changes.

Now live on npm

Agent instructions now stay in sync with your project memory

Install @vibecompass/vibecompass and generate Claude, Codex, Cursor, and Copilot instruction files from one local-first source of truth.

See setup

What changes

Make the next session less guesswork

Agent files

Stop maintaining four agent-instruction files by hand

Generate CLAUDE.md, AGENTS.md, .cursorrules, and Copilot instructions from the same project memory, with your own notes preserved outside managed regions.

Project context

Stop re-explaining the repo

Claude Code, Codex, and Cursor can start with the same map of what the app is, how it works, and where the important files live.

Decision trail

Know why the code is this way

When you choose a pattern, defer a cleanup, or settle an architecture question, VibeCompass keeps that reasoning easy to find.

Drift checks

Catch contradictions before they spread

If a later session starts building against old assumptions, VibeCompass helps surface the mismatch before it spreads.

Session handoff

Pick up where you actually left off

Each session leaves behind a usable handoff, so tomorrow's model is not guessing from a cold start.

Before & after

Replace the rituals

Without VibeCompassWith VibeCompass

Mystery folders full of stale notesProject memory kept beside the code

Four agent files drifting apartGenerated instructions from one source

A new model asking the same questionsSessions start with the current map

Copy-pasting context into every chatContext delivered through MCP

Decisions buried in old threadsA decision trail the model can read

Finding drift after it hurtsContradictions surfaced earlier

Give the next model the story so far

Works with Claude Code, Codex, and Cursor. Read the docs, connect a repo, and stop starting every chat from scratch.

Get started — free Read the docs first