Your first coding task
Start with a small change you can verify: fix one failing test in a repository on your machine. This walkthrough takes you from opening a conversation to reviewing the result. A worktree, delegated agent, or pull request is not required for this first task.
Open your repository
- Install Vibe Desktop for macOS or Windows and sign in with your Mistral account.
- Switch to Code.
- Start a local session against the repository you want to work on.
The agent reads and edits files in that checkout and runs commands in your development environment. You do not need to install the Vibe CLI: Desktop and the CLI share a core agent engine and session logs, but Desktop does not embed or launch the CLI application. Tools, tool implementations, and prompts can differ.
If you do not have a local checkout, choose a cloud session instead. See Choose where to work and the cloud-session setup. The example below uses a local session.
Projects group related work together, helping you organize sessions for a repository or task.
Describe the failing test
Choose a real failing test from your project. Include its name, file path, error output, and test command when you know them. For example, adapt this prompt to your repository:
The authentication test rejects a valid login. Reproduce the failure
with the project's test command, identify the cause, and make the
smallest fix. Do not weaken the test or change unrelated behavior.
Run the relevant tests and explain the result. Leave the changes
uncommitted for me to review.Paste the actual failure below your prompt. A specific problem gives the agent a clear starting point and gives you a way to check whether the change solves it.
Follow the investigation
Read the file edits, commands, and results in the conversation. Respond to approval requests and questions; the agent may need you to clarify expected behavior or approve a command.
If it starts changing unrelated code, interrupt it and redirect the task. For example:
Keep this change limited to the failing authentication test and its
cause. Explain why any additional file needs to change before editing it.To inspect a file or run your own command, see Follow and inspect work. Check which conversation is selected before using its panels.
Review the result
- Read the agent's explanation of the failure and its fix.
- Open + → Git Changes to inspect the diff, and + → Files to read the changed files.
- Confirm the change addresses the expected behavior without weakening the test or including unrelated edits.
- Check the test command and its output. Run the relevant tests yourself in + → Terminal if needed.
A successful test run is evidence for the fix, not a substitute for reviewing it. If a test could not run, ask what prevented it and resolve that limitation before treating the change as ready.
You now have a reviewed local change. Commit it when you are satisfied; create a pull request only if your workflow calls for one. Continue with Review changes and pull requests for delivery and PR review.
What to do next
- Follow and inspect work when you need files, terminal output, or reference pages beside the conversation.
- Work on parallel tasks when another task needs its own checkout or delegated conversation.
- Organize your conversations as your ongoing work grows.