Vreko

Get Started with Vreko

Install the Vreko CLI:

npm install -g @vreko/cli

Initialize in your project:

cd your-project
vreko init

Vreko is now watching your codebase. Run your next AI prompt β€” Vreko is already informing the context.

What just happened

Vreko detected your agent setup automatically. A pointer to .vreko/docs/INTELLIGENCE.md has been added to your CLAUDE.md, .cursorrules, or project instructions file β€” that’s what your agent reads on every prompt now.

It’s probably short right now. Vreko is still learning your codebase. Over the next few weeks it will surface fragile files, AI drift zones, and co-change patterns specific to your code.

If the block is empty or missing after a few sessions, run vreko status to verify the service is running.

Optional: VS Code Extension

Want ambient signals in your editor? The extension adds status bar indicators and file decorations.

The extension is optional β€” the CLI alone gives you the full intelligence layer and automatic agent delivery.


What to Expect

WhenWhat’s Happening
Right awayVreko detects your agent setup and starts writing intelligence into your rules file
First weekAI-attributed changes above the risk threshold are snapshotted; Vreko starts building a picture of your codebase
Day 30Patterns emerge. Vreko starts knowing your codebase, not just watching it
Day 90Your agent sees fragile files before it touches them β€” delivered automatically on every prompt

Advanced Integrations

Once your agent is seeing Vreko’s intelligence via rules-file delivery, you can add:

  • Pre-tool-use hooks β€” Claude Code and emerging tools intercept tool calls before they execute
  • MCP β€” for Claude Desktop and other MCP-native clients
  • CLI in agent harnesses β€” vreko context for custom orchestration
# Configure MCP for Claude Desktop
vreko mcp configure --tool claude-code

# Configure for Cursor
vreko mcp configure --tool cursor

Where to Go Next