Get VIBES Running in 5 Minutes

Add AI transparency to your workflow — track every line of code AI writes and every decision agents make. Pick your tool, install, and you're done.

Choose Your Tool

VIBES instrumentation works with the AI tools you already use. Pick your tool below to add tracking for both code generation and agent actions.

💻

Claude Code

Available

Add VIBES tracking to Claude Code sessions. Records code it writes, decisions it makes, and reasoning it uses.

npx vibecheck init --tool claude-code

Gemini

Available

Instrument Gemini for full VIBES tracking. Captures code generation, tool use, and agent operations.

npx vibecheck init --tool gemini
🤖

Codex (OpenAI)

Available

Add VIBES to OpenAI Codex workflows. Tracks code output, API calls, and autonomous agent actions.

npx vibecheck init --tool codex
🚧

Cursor / Windsurf / Copilot

Coming Soon

Instrumentation for IDE-integrated tools is in development. Join the waitlist to be notified when support ships.

Don't see your tool? Check the full tooling page for the latest provider support, or ask your provider to add VIBES support.

Or Use Maestro

Want the full VIBES ecosystem without any setup? Maestro comes with everything built in — tracking for code and agent decisions, verification, risk scoring, and governance — ready out of the box.

Maestro — The Easiest Way to Start

Maestro is a full implementation of the VIBES ecosystem. No manual instrumentation, no configuration — just start working and everything gets tracked automatically. Code generation, agent decisions, delegation chains — all of it.

VIBES VERIFY PRISM EVOLVE

Full audit trail + cryptographic signing + risk scoring + agent governance

Get started at runmaestro.ai →

What Happens Next

Once you install VIBES instrumentation (or start using Maestro), here's what happens in your project — for both code generation and agent operations.

1

A .ai-audit/ folder appears in your project

This is where all VIBES data lives. It's a normal folder in your repository — committed to git, versioned alongside your code, and portable across any system.

2

Every AI action gets recorded automatically

When AI writes code, VIBES records what it wrote and what it was asked. When an agent makes a decision — approving a PR, scaling infrastructure, modifying a pipeline — VIBES captures the decision and reasoning. No manual work required.

3

View reports with vibecheck report

Run a single command to see a summary of all AI involvement in your project — which models touched which files, what decisions agents made, risk scores, and trends over time.

4

Query your audit data anytime

Need to find everything a specific model wrote? Or every decision an agent made last week? Use vibecheck query to search your audit trail — instant answers, no guesswork.

Add a Badge

Show that your project tracks AI involvement. Add a VIBES badge to your README — it tells contributors and users that every AI action in your project is recorded and auditable.

✅ VIBES Tracked

Add this to your README.md:

<!-- VIBES Badge --> [![VIBES Tracked](https://img.shields.io/badge/VIBES-tracked-00c8d4)](https://itsavibe.ai) # Or if your project is in the registry: [![VIBES Tracked](https://itsavibe.ai/api/badge/YOUR-PROJECT)](https://itsavibe.ai/registry)

See all badge options and customization → · Trust-tier attestation badges →

Spread the Word

VIBES gets stronger as more tools and teams adopt it. Here's how you can help make AI transparency the default — for code generation and agent operations alike.

Ready to Go?

You've got everything you need. Pick a path and start tracking what AI does in your workflow today.

Get Instrumented

Run the install command above for your tool. You'll be tracking AI code and agent decisions in under 5 minutes.

Back to top →

Explore the Ecosystem

Learn how VERIFY, PRISM, and EVOLVE extend VIBES with signing, risk scoring, and agent governance.

The full ecosystem →

Try Maestro

Full VIBES ecosystem — VIBES, VERIFY, PRISM, and EVOLVE — built in and ready to go.

runmaestro.ai →

Want the full implementation guide? Read the Implementor’s Reference →