|
|
1 week ago | |
|---|---|---|
| .. | ||
| README.md | 1 week ago | |
Mistral Vibe uses two files per agent:
~/.vibe/agents/<slug>.toml)~/.vibe/prompts/<slug>.md)The generated files come from scripts/convert.sh --tool vibe, which writes
one TOML agent configuration and one Markdown prompt file per agency agent
into integrations/vibe/agents/ and integrations/vibe/prompts/ respectively.
From the repository root:
./scripts/convert.sh --tool vibe
Run the installer from your target directory:
cd /your/project && /path/to/agency-agents/scripts/install.sh --tool vibe
This copies the generated files into:
~/.vibe/agents/<slug>.toml
~/.vibe/prompts/<slug>.md
You can override the destination using the VIBE_HOME environment variable:
VIBE_HOME=~/.config/vibe ./scripts/install.sh --tool vibe
Each generated agent pair lives in:
integrations/vibe/agents/<slug>.toml
integrations/vibe/prompts/<slug>.md
The minimal Vibe agent configuration:
agent_type = "agent"
system_prompt_id = "<slug>"
Users can specify active_model in their agent TOML files or rely on their
Vibe configuration default model.
The prompt file contains:
After installation, reference agents in Mistral Vibe by their system prompt ID (which matches the filename slug).
Example:
Use the Code Reviewer agent to analyze this pull request.
Install only specific divisions or agents:
# Install only agents from Division 1
./scripts/install.sh --tool vibe --division 1
# Install only the code-reviewer agent
./scripts/install.sh --tool vibe --agent code-reviewer
After modifying source agents:
./scripts/convert.sh --tool vibe
./scripts/install.sh --tool vibe
Make sure vibe is in your PATH, or that ~/.vibe/ already exists:
which vibe
vibe --version
Generate the Vibe artifacts before installing:
./scripts/convert.sh --tool vibe