[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-72188":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":16,"starSnapshotCount":16,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},72188,"mistral-vibe","mistralai\u002Fmistral-vibe","mistralai","Minimal CLI coding agent by Mistral","",null,"Python",4435,525,18,154,0,25,82,283,75,30.16,"Apache License 2.0",false,"main",true,[],"2026-06-12 02:02:59","# Mistral Vibe\n\n[![PyPI Version](https:\u002F\u002Fimg.shields.io\u002Fpypi\u002Fv\u002Fmistral-vibe)](https:\u002F\u002Fpypi.org\u002Fproject\u002Fmistral-vibe)\n[![Python Version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fpython-3.12%2B-blue)](https:\u002F\u002Fwww.python.org\u002Fdownloads\u002Frelease\u002Fpython-3120\u002F)\n[![CI Status](https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Factions\u002Fworkflows\u002Fci.yml)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fmistralai\u002Fmistral-vibe)](https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002FLICENSE)\n\n```\n██████████████████░░\n██████████████████░░\n████  ██████  ████░░\n████    ██    ████░░\n████          ████░░\n████  ██  ██  ████░░\n██      ██      ██░░\n██████████████████░░\n██████████████████░░\n```\n\n**Mistral's open-source CLI coding assistant.**\n\nMistral Vibe is a command-line coding assistant powered by Mistral's models. It provides a conversational interface to your codebase, allowing you to use natural language to explore, modify, and interact with your projects through a powerful set of tools.\n\n> [!WARNING]\n> Mistral Vibe works on Windows, but we officially support and target UNIX environments.\n\n### One-line install (recommended)\n\n**Linux and macOS**\n\n```bash\ncurl -LsSf https:\u002F\u002Fmistral.ai\u002Fvibe\u002Finstall.sh | bash\n```\n\n**Windows**\n\nFirst, install uv\n\n```bash\npowershell -ExecutionPolicy ByPass -c \"irm https:\u002F\u002Fastral.sh\u002Fuv\u002Finstall.ps1 | iex\"\n```\n\nThen, use uv command below.\n\n### Using uv\n\n```bash\nuv tool install mistral-vibe\n```\n\n### Using pip\n\n```bash\npip install mistral-vibe\n```\n\n## Table of Contents\n\n- [Features](#features)\n  - [Built-in Agents](#built-in-agents)\n  - [Subagents and Task Delegation](#subagents-and-task-delegation)\n  - [Interactive User Questions](#interactive-user-questions)\n- [Terminal Requirements](#terminal-requirements)\n- [Quick Start](#quick-start)\n- [Usage](#usage)\n  - [Interactive Mode](#interactive-mode)\n  - [Trust Folder System](#trust-folder-system)\n  - [Programmatic Mode](#programmatic-mode)\n- [Voice Mode](#voice-mode)\n- [Slash Commands](#slash-commands)\n  - [Built-in Slash Commands](#built-in-slash-commands)\n  - [Custom Slash Commands via Skills](#custom-slash-commands-via-skills)\n- [Skills System](#skills-system)\n  - [Creating Skills](#creating-skills)\n  - [Skill Discovery](#skill-discovery)\n  - [Managing Skills](#managing-skills)\n- [Configuration](#configuration)\n  - [Configuration File Location](#configuration-file-location)\n  - [API Key Configuration](#api-key-configuration)\n  - [Custom System Prompts](#custom-system-prompts)\n  - [Custom Agent Configurations](#custom-agent-configurations)\n  - [Tool Management](#tool-management)\n  - [MCP Server Configuration](#mcp-server-configuration)\n  - [Session Management](#session-management)\n  - [Update Settings](#update-settings)\n  - [Custom Vibe Home Directory](#custom-vibe-home-directory)\n- [Editors\u002FIDEs](#editorsides)\n- [Resources](#resources)\n- [Data collection & usage](#data-collection--usage)\n- [License](#license)\n\n## Features\n\n- **Interactive Chat**: A conversational AI agent that understands your requests and breaks down complex tasks.\n- **Powerful Toolset**: A suite of tools for file manipulation, code searching, version control, and command execution, right from the chat prompt.\n  - Read, write, and patch files (`read_file`, `write_file`, `search_replace`).\n  - Execute shell commands in a stateful terminal (`bash`).\n  - Recursively search code with `grep` (with `ripgrep` support).\n  - Manage a `todo` list to track the agent's work.\n  - Ask interactive questions to gather user input (`ask_user_question`).\n  - Delegate tasks to subagents for parallel work (`task`).\n- **Project-Aware Context**: Vibe automatically scans your project's file structure and Git status to provide relevant context to the agent, improving its understanding of your codebase.\n- **Advanced CLI Experience**: Built with modern libraries for a smooth and efficient workflow.\n  - Autocompletion for slash commands (`\u002F`) and file paths (`@`).\n  - Persistent command history.\n  - Beautiful Themes.\n- **Highly Configurable**: Customize models, providers, tool permissions, and UI preferences through a simple `config.toml` file.\n- **Safety First**: Features tool execution approval.\n- **Multiple Built-in Agents**: Choose from different agent profiles tailored for specific workflows.\n\n### Built-in Agents\n\nVibe comes with several built-in agent profiles, each designed for different use cases:\n\n- **`default`**: Standard agent that requires approval for tool executions. Best for general use.\n- **`plan`**: Read-only agent for exploration and planning. Auto-approves safe tools like `grep` and `read_file`.\n- **`accept-edits`**: Auto-approves file edits only (`write_file`, `search_replace`). Useful for code refactoring.\n- **`auto-approve`**: Auto-approves all tool executions. Use with caution.\n\nUse the `--agent` flag to select a different agent:\n\n```bash\nvibe --agent plan\n```\n\nTo change the default agent used when `--agent` is not passed, set\n`default_agent` in your `config.toml`:\n\n```toml\ndefault_agent = \"plan\"\n```\n\nValid values are `default`, `plan`, `accept-edits`, `auto-approve`,\n`lean` (only when listed in `installed_agents`), or the name of any\ncustom agent file in `~\u002F.vibe\u002Fagents\u002F` or the project's `.vibe\u002Fagents\u002F`\ndirectory. Subagents such as `explore` are not accepted.\n\n> Note: `default_agent` only applies to interactive sessions. In\n> programmatic mode (`-p` \u002F `--prompt`), Vibe falls back to `auto-approve`\n> when `--agent` is not provided, so `default_agent` is ignored.\n\n### Subagents and Task Delegation\n\nVibe supports subagents for delegating tasks. Subagents run independently and can perform specialized work without user interaction, preventing the context from being overloaded.\n\nThe `task` tool allows the agent to delegate work to subagents:\n\n```\n> Can you explore the codebase structure while I work on something else?\n\n🤖 I'll use the task tool to delegate this to the explore subagent.\n\n> task(task=\"Analyze the project structure and architecture\", agent=\"explore\")\n```\n\nCreate custom subagents by adding `agent_type = \"subagent\"` to your agent configuration. Vibe comes with a built-in subagent called `explore`, a read-only subagent for codebase exploration used internally for delegation.\n\n### Interactive User Questions\n\nThe `ask_user_question` tool allows the agent to ask you clarifying questions during its work. This enables more interactive and collaborative workflows.\n\n```\n> Can you help me refactor this function?\n\n🤖 I need to understand your requirements better before proceeding.\n\n> ask_user_question(questions=[{\n    \"question\": \"What's the main goal of this refactoring?\",\n    \"options\": [\n        {\"label\": \"Performance\", \"description\": \"Make it run faster\"},\n        {\"label\": \"Readability\", \"description\": \"Make it easier to understand\"},\n        {\"label\": \"Maintainability\", \"description\": \"Make it easier to modify\"}\n    ]\n}])\n```\n\nThe agent can ask multiple questions at once, displayed as tabs. Each question supports 2-4 options plus an automatic \"Other\" option for free text responses.\n\n## Terminal Requirements\n\nVibe's interactive interface requires a modern terminal emulator. Recommended terminal emulators include:\n\n- **WezTerm** (cross-platform)\n- **Alacritty** (cross-platform)\n- **Ghostty** (Linux and macOS)\n- **Kitty** (Linux and macOS)\n\nMost modern terminals should work, but older or minimal terminal emulators may have display issues.\n\n## Quick Start\n\n1. Navigate to your project's root directory:\n\n   ```bash\n   cd \u002Fpath\u002Fto\u002Fyour\u002Fproject\n   ```\n\n2. Run Vibe:\n\n   ```bash\n   vibe\n   ```\n\n3. If this is your first time running Vibe, it will:\n   - Create a default configuration file at `~\u002F.vibe\u002Fconfig.toml`\n   - Prompt you to enter your API key if it's not already configured\n   - Save your API key to `~\u002F.vibe\u002F.env` for future use\n\n   Alternatively, you can configure your API key separately using `vibe --setup`.\n\n4. Start interacting with the agent!\n\n   ```\n   > Can you find all instances of the word \"TODO\" in the project?\n\n   🤖 The user wants to find all instances of \"TODO\". The `grep` tool is perfect for this. I will use it to search the current directory.\n\n   > grep(pattern=\"TODO\", path=\".\")\n\n   ... (grep tool output) ...\n\n   🤖 I found the following \"TODO\" comments in your project.\n   ```\n\n## Usage\n\n### Interactive Mode\n\nSimply run `vibe` to enter the interactive chat loop.\n\n- **Multi-line Input**: Press `Ctrl+J` or `Shift+Enter` for select terminals to insert a newline.\n- **File Paths**: Reference files in your prompt using the `@` symbol for smart autocompletion (e.g., `> Read the file @src\u002Fagent.py`).\n- **Shell Commands**: Prefix any command with `!` to execute it directly in your shell, bypassing the agent (e.g., `> !ls -l`).\n- **External Editor**: Press `Ctrl+G` to edit your current input in an external editor.\n- **Tool Output Toggle**: Press `Ctrl+O` to toggle the tool output view.\n- **Todo View Toggle**: Press `Ctrl+T` to toggle the todo list view.\n- **Debug Console**: Press `Ctrl+\\` to toggle the debug console.\n- **Agent Selection**: Press `Shift+Tab` to cycle through agents (default, plan, ...).\n\nYou can start Vibe with a prompt using the following command:\n\n```bash\nvibe \"Refactor the main function in cli\u002Fmain.py to be more modular.\"\n```\n\n### Trust Folder System\n\nVibe includes a trust folder system to ensure you only run the agent in directories you trust. When you first run Vibe in a new directory which contains a `.vibe` subfolder, it may ask you to confirm whether you trust the folder.\n\nTrusted folders are remembered for future sessions. You can manage trusted folders through its configuration file `~\u002F.vibe\u002Ftrusted_folders.toml`.\n\nThis safety feature helps prevent accidental execution in sensitive directories.\n\n### Programmatic Mode\n\nYou can run Vibe non-interactively by piping input or using the `--prompt` flag. This is useful for scripting.\n\n```bash\nvibe --prompt \"Refactor the main function in cli\u002Fmain.py to be more modular.\"\n```\n\nBy default, it uses `auto-approve` mode.\n\n#### Programmatic Mode Options\n\nWhen using `--prompt`, you can specify additional options:\n\n- **`--max-turns N`**: Limit the maximum number of assistant turns. The session will stop after N turns.\n- **`--max-price DOLLARS`**: Set a maximum cost limit in dollars. The session will be interrupted if the cost exceeds this limit.\n- **`--enabled-tools TOOL`**: Enable specific tools. In programmatic mode, this disables all other tools. Can be specified multiple times. Supports exact names, glob patterns (e.g., `bash*`), or regex with `re:` prefix (e.g., `re:^serena_.*$`).\n- **`--output FORMAT`**: Set the output format. Options:\n  - `text` (default): Human-readable text output\n  - `json`: All messages as JSON at the end\n  - `streaming`: Newline-delimited JSON per message\n\nExample:\n\n```bash\nvibe --prompt \"Analyze the codebase\" --max-turns 5 --max-price 1.0 --output json\n```\n\n## Voice Mode\n\n> [!WARNING]\n> Voice mode is experimental and may change in future releases.\n\nVoice mode allows you to dictate input using your microphone instead of typing.\n\n### Activating Voice Mode\n\nToggle voice mode on or off with the `\u002Fvoice` slash command:\n\n```\n> \u002Fvoice\n```\n\n### Recording Shortcuts\n\n| Shortcut | Action           |\n| -------- | ---------------- |\n| `Ctrl+R` | Start recording  |\n| Any key  | Stop recording   |\n| `Escape` | Cancel recording |\n| `Ctrl+C` | Cancel recording |\n\n## Slash Commands\n\nUse slash commands for meta-actions and configuration changes during a session.\n\n### Built-in Slash Commands\n\nVibe provides several built-in slash commands. Use slash commands by typing them in the input box:\n\n```\n> \u002Fhelp\n```\n\n### Custom Slash Commands via Skills\n\nYou can define your own slash commands through the skills system. Skills are reusable components that extend Vibe's functionality.\n\nTo create a custom slash command:\n\n1. Create a skill directory with a `SKILL.md` file\n2. Set `user-invocable = true` in the skill metadata\n3. Define the command logic in your skill\n\nExample skill metadata:\n\n```markdown\n---\nname: my-skill\ndescription: My custom skill with slash commands\nuser-invocable: true\n---\n```\n\nCustom slash commands appear in the autocompletion menu alongside built-in commands.\n\n## Skills System\n\nVibe's skills system allows you to extend functionality through reusable components. Skills can add new tools, slash commands, and specialized behaviors.\n\nVibe follows the [Agent Skills specification](https:\u002F\u002Fagentskills.io\u002Fspecification) for skill format and structure.\n\n### Creating Skills\n\nSkills are defined in directories with a `SKILL.md` file containing metadata in YAML frontmatter. For example, `~\u002F.vibe\u002Fskills\u002Fcode-review\u002FSKILL.md`:\n\n```markdown\n---\nname: code-review\ndescription: Perform automated code reviews\nlicense: MIT\ncompatibility: Python 3.12+\nuser-invocable: true\nallowed-tools:\n  - read_file\n  - grep\n  - ask_user_question\n---\n\n# Code Review Skill\n\nThis skill helps analyze code quality and suggest improvements.\n```\n\n### Skill Discovery\n\nVibe discovers skills from multiple locations:\n\n1. **Custom paths**: Configured in `config.toml` via `skill_paths`\n2. **Standard Agent Skills path** (project root, trusted folders only): `.agents\u002Fskills\u002F` — [Agent Skills](https:\u002F\u002Fagentskills.io) standard\n3. **Local project skills** (project root, trusted folders only): `.vibe\u002Fskills\u002F` in your project\n4. **Global skills directory**: `~\u002F.vibe\u002Fskills\u002F`\n\n```toml\nskill_paths = [\"\u002Fpath\u002Fto\u002Fcustom\u002Fskills\"]\n```\n\n### Managing Skills\n\nEnable or disable skills using patterns in your configuration:\n\n```toml\n# Enable specific skills\nenabled_skills = [\"code-review\", \"test-*\"]\n\n# Disable specific skills\ndisabled_skills = [\"experimental-*\"]\n```\n\nSkills support the same pattern matching as tools (exact names, glob patterns, and regex).\n\n## Configuration\n\n### Configuration File Location\n\nVibe is configured via a `config.toml` file. It looks for this file first in `.\u002F.vibe\u002Fconfig.toml` and then falls back to `~\u002F.vibe\u002Fconfig.toml`.\n\n### API Key Configuration\n\nTo use Vibe, you'll need a Mistral API key. You can obtain one by signing up at [https:\u002F\u002Fconsole.mistral.ai](https:\u002F\u002Fconsole.mistral.ai).\n\nYou can configure your API key using `vibe --setup`, or through one of the methods below.\n\nVibe supports multiple ways to configure your API keys:\n\n1. **Interactive Setup (Recommended for first-time users)**: When you run Vibe for the first time or if your API key is missing, Vibe will prompt you to enter it. The key will be securely saved to `~\u002F.vibe\u002F.env` for future sessions.\n\n2. **Environment Variables**: Set your API key as an environment variable:\n\n   ```bash\n   export MISTRAL_API_KEY=\"your_mistral_api_key\"\n   ```\n\n3. **`.env` File**: Create a `.env` file in `~\u002F.vibe\u002F` and add your API keys:\n\n   ```bash\n   MISTRAL_API_KEY=your_mistral_api_key\n   ```\n\n   Vibe automatically loads API keys from `~\u002F.vibe\u002F.env` on startup. Environment variables take precedence over the `.env` file if both are set.\n\n**Note**: The `.env` file is specifically for API keys and other provider credentials. General Vibe configuration should be done in `config.toml`.\n\n### Custom System Prompts\n\nYou can create `AGENTS.md` files to add custom instructions. You can also replace the entire system prompt.\n\nPlace `AGENTS.md` files in:\n- `~\u002F.vibe\u002FAGENTS.md` — user-level instructions for all projects\n- Project directories — project-specific instructions, loaded from cwd up to the trust root\n\nPriority: closer directories override more distant ones. Instructions in `AGENTS.md` override the default system prompt. Files are only loaded for trusted folders.\n\nCustom system prompts entirely replace the default one (`prompts\u002Fcli.md`). Create a markdown file in the `~\u002F.vibe\u002Fprompts\u002F` directory with your custom prompt content.\n\nTo use a custom system prompt, set the `system_prompt_id` in your configuration to match the filename (without the `.md` extension):\n\n```toml\n# Use a custom system prompt\nsystem_prompt_id = \"my_custom_prompt\"\n```\n\nThis will load the prompt from `~\u002F.vibe\u002Fprompts\u002Fmy_custom_prompt.md`.\n\n### Custom Agent Configurations\n\nYou can create custom agent configurations for specific use cases (e.g., red-teaming, specialized tasks) by adding agent-specific TOML files in the `~\u002F.vibe\u002Fagents\u002F` directory.\n\nTo use a custom agent, run Vibe with the `--agent` flag:\n\n```bash\nvibe --agent my_custom_agent\n```\n\nVibe will look for a file named `my_custom_agent.toml` in the agents directory and apply its configuration.\n\nExample custom agent configuration (`~\u002F.vibe\u002Fagents\u002Fredteam.toml`):\n\n```toml\n# Custom agent configuration for red-teaming\nactive_model = \"mistral-medium-3.5\"\nsystem_prompt_id = \"redteam\"\n\n# Disable some tools for this agent\ndisabled_tools = [\"search_replace\", \"write_file\"]\n\n# Override tool permissions for this agent\n[tools.bash]\npermission = \"always\"\n\n[tools.read_file]\npermission = \"always\"\n```\n\nNote: This implies that you have set up a redteam prompt named `~\u002F.vibe\u002Fprompts\u002Fredteam.md`.\n\n### Tool Management\n\n#### Enable\u002FDisable Tools with Patterns\n\nYou can control which tools are active using `enabled_tools` and `disabled_tools`.\nThese fields support exact names, glob patterns, and regular expressions.\n\nExamples:\n\n```toml\n# Only enable tools that start with \"serena_\" (glob)\nenabled_tools = [\"serena_*\"]\n\n# Regex (prefix with re:) — matches full tool name (case-insensitive)\nenabled_tools = [\"re:^serena_.*$\"]\n\n# Disable a group with glob; everything else stays enabled\ndisabled_tools = [\"mcp_*\", \"grep\"]\n```\n\nNotes:\n\n- MCP tool names use underscores, e.g., `serena_list` not `serena.list`.\n- Regex patterns are matched against the full tool name using fullmatch.\n\n### MCP Server Configuration\n\nYou can configure MCP (Model Context Protocol) servers to extend Vibe's capabilities. Add MCP server configurations under the `mcp_servers` section:\n\n```toml\n# Example MCP server configurations\n[[mcp_servers]]\nname = \"my_http_server\"\ntransport = \"http\"\nurl = \"http:\u002F\u002Flocalhost:8000\"\nheaders = { \"Authorization\" = \"Bearer my_token\" }\napi_key_env = \"MY_API_KEY_ENV_VAR\"\napi_key_header = \"Authorization\"\napi_key_format = \"Bearer {token}\"\n\n[[mcp_servers]]\nname = \"my_streamable_server\"\ntransport = \"streamable-http\"\nurl = \"http:\u002F\u002Flocalhost:8001\"\nheaders = { \"X-API-Key\" = \"my_api_key\" }\n\n[[mcp_servers]]\nname = \"fetch_server\"\ntransport = \"stdio\"\ncommand = \"uvx\"\nargs = [\"mcp-server-fetch\"]\nenv = { \"DEBUG\" = \"1\", \"LOG_LEVEL\" = \"info\" }\n```\n\nSupported transports:\n\n- `http`: Standard HTTP transport\n- `streamable-http`: HTTP transport with streaming support\n- `stdio`: Standard input\u002Foutput transport (for local processes)\n\nKey fields:\n\n- `name`: A short alias for the server (used in tool names)\n- `transport`: The transport type\n- `url`: Base URL for HTTP transports\n- `headers`: Additional HTTP headers\n- `api_key_env`: Environment variable containing the API key\n- `command`: Command to run for stdio transport\n- `args`: Additional arguments for stdio transport\n- `startup_timeout_sec`: Timeout in seconds for the server to start and initialize (default 10s)\n- `tool_timeout_sec`: Timeout in seconds for tool execution (default 60s)\n- `env`: Environment variables to set for the MCP server of transport type stdio\n\nMCP tools are named using the pattern `{server_name}_{tool_name}` and can be configured with permissions like built-in tools:\n\n```toml\n# Configure permissions for specific MCP tools\n[tools.fetch_server_get]\npermission = \"always\"\n\n[tools.my_http_server_query]\npermission = \"ask\"\n```\n\nMCP server configurations support additional features:\n\n- **Environment variables**: Set environment variables for MCP servers\n- **Custom timeouts**: Configure startup and tool execution timeouts\n\nExample with environment variables and timeouts:\n\n```toml\n[[mcp_servers]]\nname = \"my_server\"\ntransport = \"http\"\nurl = \"http:\u002F\u002Flocalhost:8000\"\nenv = { \"DEBUG\" = \"1\", \"LOG_LEVEL\" = \"info\" }\nstartup_timeout_sec = 15\ntool_timeout_sec = 120\n```\n\n### Session Management\n\n#### Session Continuation and Resumption\n\nVibe supports continuing from previous sessions:\n\n- **`--continue`** or **`-c`**: Continue from the most recent saved session\n- **`--resume SESSION_ID`**: Resume a specific session by ID (supports partial matching)\n\n```bash\n# Continue from last session\nvibe --continue\n\n# Resume specific session\nvibe --resume abc123\n```\n\nSession logging must be enabled in your configuration for these features to work.\n\n#### Working Directory Control\n\nUse the `--workdir` option to specify a working directory:\n\n```bash\nvibe --workdir \u002Fpath\u002Fto\u002Fproject\n```\n\nThis is useful when you want to run Vibe from a different location than your current directory.\n\n### Update Settings\n\n#### Auto-Update\n\nVibe includes an automatic update feature that keeps your installation current. This is enabled by default.\n\nTo disable auto-updates, add this to your `config.toml`:\n\n```toml\nenable_auto_update = false\n```\n\n### Notification Settings\n\nVibe can notify you when the agent needs your attention (awaiting approval, asking a question, or task complete). This is useful when you switch to another window while the agent works.\n\nTo disable notifications:\n\n```toml\nenable_notifications = false\n```\n\n### Custom Vibe Home Directory\n\nBy default, Vibe stores its configuration in `~\u002F.vibe\u002F`. You can override this by setting the `VIBE_HOME` environment variable:\n\n```bash\nexport VIBE_HOME=\"\u002Fpath\u002Fto\u002Fcustom\u002Fvibe\u002Fhome\"\n```\n\nThis affects where Vibe looks for:\n\n- `config.toml` - Main configuration\n- `.env` - API keys\n- `agents\u002F` - Custom agent configurations\n- `prompts\u002F` - Custom system prompts\n- `tools\u002F` - Custom tools\n- `logs\u002F` - Session logs\n\n## Editors\u002FIDEs\n\nMistral Vibe can be used in text editors and IDEs that support [Agent Client Protocol](https:\u002F\u002Fagentclientprotocol.com\u002Foverview\u002Fclients). See the [ACP Setup documentation](docs\u002Facp-setup.md) for setup instructions for various editors and IDEs.\n\n## Resources\n\n- [CHANGELOG](CHANGELOG.md) - See what's new in each version\n- [CONTRIBUTING](CONTRIBUTING.md) - Guidelines for feature requests, feedback and bug reports\n\n## Data collection & usage\n\nUse of Vibe is subject to our [Privacy Policy](https:\u002F\u002Flegal.mistral.ai\u002Fterms\u002Fprivacy-policy) and may include the collection and processing of data related to your use of the service, such as usage data, to operate, maintain, and improve Vibe. You can disable telemetry in your `config.toml` by setting `enable_telemetry = false`.\n\n\n## License\n\nCopyright 2025 Mistral AI\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n    http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the [LICENSE](LICENSE) file for the full license text.\n","Mistral Vibe 是一个由 Mistral 提供支持的开源命令行编码助手。它通过自然语言处理技术，让用户能够以对话的方式探索、修改和与代码库互动。核心功能包括内置代理、子代理任务委派以及交互式用户问答等，极大提升了开发者的工作效率。此外，Mistral Vibe 还引入了语音模式和支持自定义技能系统，进一步增强了其灵活性和实用性。此工具特别适合于需要频繁进行代码审查、调试或快速原型设计的开发场景中使用，尤其对熟悉UNIX环境下的Linux和macOS用户更为友好。",2,"2026-06-11 03:40:46","high_star"]