Turn what you just debugged into reusable AI context

The most valuable context your team has is created during debugging and then thrown away. The command that finally reproduced the bug, the API call that returned the surprising payload, the paragraph of explanation you typed into a chat window — all of it lives in scrollback until the scrollback is gone.

VibeControls makes that context a workspace object. An AI Context has a type — git repo, API call, markdown doc, command, plain text, file or URL — plus tags, a status of active or archived, and optional provenance: the session it was authored against and the Vibe it belongs to. Vibe-linked contexts carry a visibility of private or shared-with-vibe, so a note you make while debugging can stay yours or become the project's.

Prompts work the same way but add structure. Each one is a template with {{variable}} placeholders, filed under a category — coding, debugging, review, documentation, testing, deployment, runbook or general — with a draft/active/archived lifecycle. Rendering happens on the server, so filling the variables produces exactly the same text for everyone. Usage is counted and the last-used time recorded, which makes it obvious which templates the team actually relies on and which were written once and forgotten.

Using them is deliberately close to the work. In the AI workbench, the composer's insert picker lists your prompts and contexts, renders a prompt's variables inline, and drops the result into the message. On a session detail page, the workbench drawer opens beside the terminal with notes, prompts and history tabs, so a runbook prompt is one click from the shell you are already in. Files can be pulled off the agent straight into a context, and instruction files can be pushed down to the agent's working directory so the harness reads them on its next run.

One honest characteristic: this is curated retrieval, not a vector index. There is no embedding store quietly deciding what the model sees — you choose, and what you chose is inspectable afterwards. That is cheaper and far easier to audit, and it is exactly why the separate signed per-Vibe context URL exists for the cases where an external tool needs a defined slice of the project instead.