The quality of an AI coding agent is only as good as the instructions steering it. Yet those instructions — AGENTS.md, CLAUDE.md, GEMINI.md, a hand-tuned .cursorrules — usually live as loose files copied from machine to machine, drifting out of sync the moment one person edits their copy. Two engineers on the same project end up with two subtly different sets of house rules, and their agents behave differently.
VibeControls turns instruction files into managed, first-class entities. Open the Instructions tab on a Vibe, click New, and pick the filename type — AGENTS_MD, CLAUDE_MD, GEMINI_MD, or CUSTOM for anything else (name it ".cursorrules" and that is exactly what lands on disk). Paste in your standards — architecture notes, coding conventions, the commands the agent may and may not run — and save. The content is stored centrally, and its real on-disk filename is derived automatically from the type you chose.
Scope decides reach. An AGENT-scoped file applies to a single machine; a VIBE-scoped file follows the whole project, so every agent that picks up that Vibe writes the same rules to its working directory. Change the canonical file once and the update propagates instead of stranding stale copies on individual laptops.
Sharing is built in. Grant a teammate access to an instruction file, or mint a share link, and they inherit the exact same steering — governed by the same workspace RBAC that protects every other resource. Edits are attributed and timestamped, so you always know who changed the house rules and when.
The result is a single source of truth for how your agents should behave. Instead of hoping everyone remembered to update their local CLAUDE.md, you author the instructions once in VibeControls, scope them, share them, and let every coding agent — Claude Code, Cursor, Gemini, or your own — read from the same page.
Do it yourself
Author an AGENTS.md or .cursorrules once inside VibeControls, scope it to a Vibe so every agent writes the same rules to its working directory, and share it with the team.
Go to Vibes, open the project Vibe you want to steer, and switch to the Instructions tab.
You should see: You see the instruction files currently attached to this Vibe (empty on a new Vibe).
Ready to make this your story?
