Get Started with Vreko

Install the CLI

npm install -g @vreko/cli

Initialize your project

cd your-project
vr init

vr init scans your codebase and starts the Vreko service:

$ vr init
◇ Scanning workspace…
  ├─ indexing files         ████████████████  1,284 files
  ├─ detecting frameworks   next.js, drizzle, vitest
  └─ wiring agent context   CLAUDE.md
◇ Vreko service started
✓ Workspace ready  -  agents.workspace.json created

Vreko is now watching your codebase. Run your next AI prompt - Vreko is already informing the context.

Install the VS Code extension

Install Vreko from the VS Code Marketplace (extension ID marcelle-labs.vreko) for ambient status-bar signals and file decorations:

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

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 vr status to verify the service is running.


What to Expect

WhenWhat’s Happening
Right awayVreko detects your agent setup and starts writing intelligence into your rules file
First weekVreko observes which files change together and which churn under AI edits; it 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

Connect your AI agent

Vreko delivers intelligence to your agent through your project’s rules file automatically. To let your agent call Vreko’s tools directly, connect the MCP server - see MCP Setup for Claude Code and Cursor.


Where to Go Next