AI Prompts
VibeControls has a built-in AI hub that lets you create reusable prompt templates, run AI sessions backed by providers installed on your agents, and manage your AI workflows alongside your development environments.
Navigate to AI in the VibeControls sidebar to access the AI hub.
Why AI Prompts in VibeControls?
Your AI tools work best when they have context about your actual environment — which project you are working on, what the codebase looks like, what commands are available. By defining prompts inside VibeControls, you keep that context close to the machine and vibe it belongs to, and you can share prompts with your team as reusable building blocks.
Key Concepts
Contexts
A context is a collection of information you provide to an AI provider before sending a prompt — the project description, relevant files, environment details, or any background the AI needs. Contexts are reusable: define them once and attach them to multiple prompts or sessions.
Prompt Templates
A prompt template is a saved prompt you can run repeatedly, with or without variable substitution. Templates let you standardize how you interact with AI tools and share those patterns with your team.
AI Sessions
An AI session is a running conversation or task with an AI provider installed on one of your agents. Unlike terminal sessions, AI sessions dispatch prompts to the provider and capture the responses.
Creating a Prompt Template
- Navigate to AI in the sidebar
- Click the Prompts tab
- Click New Prompt
- Fill in:
- Name — a short descriptive title
- Description (optional) — explain when this prompt should be used
- Template content — the prompt text, optionally using
{{variable}}placeholders - Context (optional) — attach a saved context to be prepended
- Tags (optional) — for organization and search
- Click Save
Using Variables in Templates
Prompt templates support simple {{variable}} placeholders. When you run the prompt, VibeControls will ask you to fill in the values before dispatching.
Example template content:
Review the following {{language}} code for security vulnerabilities.
Focus on {{concern}} issues. Be concise.
Code:
{{code}}
When you run this template, a form will appear asking for language, concern, and code.
Creating a Context
A context is background information you want the AI to have before seeing your prompt.
- Navigate to AI → Contexts
- Click New Context
- Fill in:
- Name — identifies this context
- Content — the background text, instructions, or data you want the AI to have
- Description (optional)
- Click Save
Contexts can be attached to prompt templates or AI sessions. A common pattern is to create a context per vibe that includes the project's readme, tech stack, and coding standards.
Running a Prompt in a Session
To dispatch a prompt to an AI provider:
- Navigate to AI → Sessions
- Click New AI Session
- Choose:
- Agent — which machine the AI provider runs on
- Provider — the AI provider plugin installed on that agent (Claude, Codex, Gemini, Copilot, OpenCode, etc.)
- Context (optional) — attach a saved context
- Click Start Session
- In the session view, find the prompt template you want to use in the Prompts panel
- Click Run next to the template (or click New Prompt to type a one-off message)
- Fill in any template variables
- Click Dispatch
The prompt is sent to the provider on your agent. The response streams back into the session view in real time.
Using Prompts with Sessions
Prompts are also accessible directly from within an AI session:
- Open an active AI session
- Use the Prompt library panel on the right side of the session view
- Search or browse your saved templates
- Click Insert to place the template text in the message input
- Fill in any variables
- Send the message
This workflow keeps your saved templates within reach while you are actively working in a session.
Managing the Prompt Library
From AI → Prompts, you can:
- Search templates by name, content, or tag
- Filter by tag to find prompts for specific use cases
- Duplicate a template to create a variation
- Edit existing templates
- Delete templates you no longer need
AI Session Logs and History
Every AI session keeps a full log of the conversation — prompts sent and responses received. To review session history:
- Open an AI session (active or past)
- Scroll through the conversation thread, or
- Click Export to download the full conversation as JSON or text
Session logs are useful for:
- Reviewing what an automated prompt produced
- Sharing a conversation thread with a teammate
- Auditing AI usage in your workspace
Queue and Scheduling
For workflows that do not need an immediate response, you can dispatch prompts to the queue rather than sending them directly:
- In the session view, click the Queue button instead of Dispatch
- Optionally set a scheduled run time
- The prompt is held in the queue and dispatched when the agent and provider are available
The AI → Queue tab shows pending and completed queue items with their status and results.
Provider Stats
The AI → Stats tab shows usage metrics for AI sessions in your workspace:
- Number of prompts dispatched per provider
- Average response times
- Session counts over time
- Provider availability status
This is useful for understanding which AI tools your team uses most and where latency is highest.
Tips
- Build a library of common prompts for your team: code review templates, documentation drafts, test generation, commit message writing. One well-crafted template saves hours across the team.
- Attach a vibe-specific context to prompts that need project knowledge — it is much more effective than pasting the same background information into every message.
- Use the queue for long-running AI tasks (large refactors, bulk documentation) so you can kick them off and check results later without waiting for a response.
- Providers are installed as plugins on individual agents — make sure the agent you select has the provider you want installed. See Agents for how to manage agent plugins.