mistralai/mistral-vibe

Minimal CLI coding agent by Mistral

Owned by Mistral AI

View on GitHub ↗Jump to charts ↓Open shareable report →

mistralai/mistral-vibe has 5k+ stars and 700+ forks on GitHub, is written in Python, and was last pushed on Oct 9, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 14th, 2026
Created on December 8th, 2025
Open Issues & Pull Requests: 412 (+0)
GitHub issues: Enabled
Number of forks: 737
Total Stargazers: 5,142 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 39.6 hours
Mean response time: 22.7 days
90th percentile: 74.4 days
Tracked items: 436

Maintainer activity

21 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "ACP" is answered fastest, typically in about 28 hours, while "linear-sync" waits about 10 days. Almost all tracked open issues have seen activity in the last three months. 63% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 211
New in 7 days: 37
Closed in 7 days: 4
Avg open age: 64 days
Stale 30+ days: 109
Stale 90+ days: 0

Recent activity

Opened in 7 days: 32
Closed in 7 days: 4
Comments in 7 days: 20
Events in 7 days: 41

Top labels

  • bug (318)
  • CLI (286)
  • linear-sync (184)
  • enhancement (27)
  • VS Code Extension (26)
  • ACP (19)
  • Engineering and Automation (19)
  • Local runtime (17)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Mistral Vibe is a CLI coding agent powered by Mistral's language models that provides a conversational interface to your codebase.

The tool solves the problem of interacting with code through natural language by offering a command-line assistant that can explore, modify, and work with projects. It works through a conversational interface backed by Mistral's models, with access to a set of built-in tools. The agent supports multiple interaction modes including interactive conversation, voice input, and programmatic access. It includes a skills system that allows custom slash commands to be defined and discovered, and integrates with MCP servers for extended tool management. A trust folder system governs which directories the agent can access, and the tool supports custom system prompts and agent configurations.

Developers targeting UNIX environments should note that while the tool runs on Windows, official support focuses on Linux and macOS. The project can be installed via uv or pip. It suits developers who want to interact with their codebase conversationally and who are comfortable with command-line workflows. The tool's extensibility through skills and MCP server integration makes it suitable for teams wanting to customize agent behavior beyond the built-in capabilities. Session management and OpenTelemetry tracing support are available for those needing to track or persist interactions.

The project shows active development with regular updates to its feature set. The codebase demonstrates ongoing refinement of the agent architecture and tool integration systems. Documentation is comprehensive, covering configuration options, skill creation, and multiple usage patterns. The maintainers have invested in making the tool accessible through multiple installation methods and interaction modes, suggesting attention to developer experience across different workflows.