Follow and inspect work
Once you have started a task, use the conversation to follow the agent's investigation and the panels to inspect its evidence. Keep files, command output, and reference pages beside the work instead of switching applications.
Read progress and respond
The conversation shows the agent's file edits, commands, and results. Read its questions and approval requests before answering. If the work drifts from your request, interrupt the agent and explain what needs to change.
An agent's summary is not the same as a command result. Check the actual output when you need to know whether a test, build, or other command succeeded.
Select the right conversation
The right panel belongs to the selected conversation. Its browser pages, terminal, file viewer, background processes, and pull request views are session-specific, including for nested sub-sessions.
Select the conversation that owns the work before opening a file, running a command, stopping a process, or inspecting a PR. Switching conversations changes the panel context.
Separate session environments do not automatically mean separate Git checkouts. Two local conversations in the same checkout still share files. Use worktrees when tasks need file isolation.
Inspect repository files
Open + → Files from the upper-right controls:
- Expand folders in the repository's file tree to locate a file.
- Select the file to open its contents in the viewer.
- Check the file name, repository path, and line numbers for text files.
Files appear as tabs in the panel. Keep several files open, switch between them, or close a tab with its close control. You can also keep a file beside a background command's output.
Use this view to explore the code before prompting or inspect a file the agent changed. To read a web page rather than a repository file, use the browser. To inspect the diff, continue with Review changes.
Run your own commands
Open + → Terminal from the upper-right controls to run commands alongside the conversation. In a local session, commands run in your local development environment. Check the selected conversation, repository, and working directory first, especially if the task uses a worktree.
Use the terminal to reproduce a failure, run a project's tests, or inspect the result independently. Choose the command appropriate to your project rather than assuming every repository uses the same tools.
Follow background commands
Builds, development servers, and file watchers can keep running while the conversation continues. Ask Vibe to start a command in the background when other steps can proceed independently. For a project that uses pnpm build, for example:
Start pnpm build in the background. While it runs, review the changes,
then check the build output and report the result.The conversation shows a Started a background process entry with the command name. Click the command to open its output in a panel tab.
You can also open + → Background processes to find commands and their current status. Select a process to inspect its live output. While it is running, its output panel includes a Stop button.
Interrupting the conversation and stopping a background process are different actions. Use the process panel's Stop control to stop that command, then check its status. Do not assume it finished because the agent moved on.
Keep reference pages beside the work
Click the globe icon in the upper-right controls to open the integrated browser. Use it for documentation, issues, dashboards, or other reference pages while the agent works.
The browser shows the page's address and back, forward, and reload controls. Browser pages can stay open as panel tabs beside source files and command output. Select a PR from the merge icon's list to open it here; see Open a pull request in the browser for private-repository access guidance.
Open a page in an external browser
To continue reading a page outside Vibe:
- Click the Open in external browser button to the right of the address bar. Its icon is an arrow pointing out of a square.
- In the Open in external browser? dialog, check the URL. The dialog explains that the page will open outside Vibe.
- Click Open to open the page in your external browser, or Cancel to leave it in Vibe.
Select Always open links externally in the dialog if you want links to open externally by default.
Opening a page externally does not grant repository access or transfer your sign-in from the integrated browser. For a private PR, use an account with access in the browser where you open it.
Find your way around
| Area | Use it to |
|---|---|
| Left sidebar | Navigate projects and conversations. |
| Main chat view | Send prompts, follow progress, and answer questions or approval requests. |
| Bottom panel | Work in the integrated terminal alongside the conversation. |
| Side panels | Inspect files, reference pages, and command output. |
| Upper-right controls | Open the panels listed below. |
Panel reference
These controls apply to the selected session or sub-session:
| Feature | Where to open it | Use it to |
|---|---|---|
| Pull requests | Merge icon | Find a PR and read its displayed status. |
| Browser | Globe icon | Open reference pages in the app. |
| Files | + → Files | Browse repository files and read their contents. |
| Git Changes | + → Git Changes | Inspect the Git changes for the selected session. |
| Terminal | + → Terminal | Run your own commands. |
| Debug | + → Debug | Open the Debug panel. |
| Background processes | + → Background processes | Find running commands and inspect their output. |
Review what changed
When the task is ready, move from watching progress to reviewing changes and test results. If you need another task to run independently, see Work on parallel tasks.