Pioneer Onboarding

Welcome to the Vreko Pioneer program. This guide walks you from your referral code to a workspace that Vreko is actively observing.

Get set up

Claim your Pioneer slot

Pioneer access is invite-based. You’ll need a referral code from a current Pioneer or from your Vreko console (Settings → Pioneer). Keep it handy - you enter it during init.

Install the CLI

npm install -g @vreko/cli

Initialize your project

cd your-project
vr init

vr init creates a .vreko/ directory, wires your agent’s rules file, and writes an initial agents.workspace.json. Enter your referral code when prompted to claim your Pioneer slot.

Start Vreko

vr start

This starts the Vreko service in the background. It begins observing your sessions and updating your workspace intelligence.

Confirm it’s running

vr status

A healthy status shows the service running and your intelligence state. That’s it - Vreko is now observing your workspace.

Optional: 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 bundles the CLI, so you can do this in parallel with the steps above - either path gives you the full intelligence layer.

What to Expect

During Your First Week:

Vreko learns which files change together and which churn under AI edits
Your agent starts receiving workspace context on every prompt
You may notice fragility signals on files you edit often

Ongoing:

Each session builds on previous learnings
Vreko adapts to your codebase, surfacing fragile files before your agent touches them

Troubleshooting

Service won’t start

Confirm nothing else is bound to the service socket, then retry vr start.
Check the service logs:
```
vr service logs
```
Re-check status:
```
vr status
```

Nothing is being recorded

Verify the service is running with vr status.
Confirm your .vrekorc isn’t excluding the files you’re editing.
Make a few edits and run vr session to see the current session.

See Troubleshooting for more.

Feedback Loop

You’re here early, so your feedback shapes what ships:

Report bugs - open an issue on GitHub Issues; include your OS, Node version, and steps to reproduce.
Tell us what surprised you - which fragility signals were unexpected vs. obvious, and whether your agent’s behavior changed with Vreko context.
Join the community - Discord to chat with other Pioneers and the Vreko team.

Thank you for being a Pioneer. Every session, bug report, and suggestion directly shapes Vreko’s development.

Need More Help?

Documentation: Full documentation
Discord: Join our Discord
GitHub: View source code