VSCode extension
Installation
Section titled “Installation”- Install the Rover CLI. It needs to be available in your
$PATHenvironment variable - Install Rover from the official extension marketplace
Initialization
Section titled “Initialization”The first step, as happens with the CLI, is to initialize the repository where you want to enable Rover.
Rover Initialization
- 1
If no workspace is open, the initialization guide will suggest you to open a workspace.

- 2
After opening a workspace, you will see a button to
Initialize Roveron it.
- 3
Now you are ready to create tasks!

Task management
Section titled “Task management”Rover task management
- 1
You can create a new task by filling the task text field.

- 2
After creation, you will see the new task in the list.

- 3
The status of the tasks will be automatically refreshed in this listing as they progress.

- 4
Both the Rover CLI and the extension use the same single source of truth, so that you can use both tools as it best fits your needs and workflows.

- 5
The task will progress and eventually reach the
Completedstatus. Here you can see some actions you can perform from the UI, such as:- View task logs
- Inspect iteration files (
context.md,plan.md,review.md,summary.md) - Compare the changes
- Open a shell in the git worktree of the task
- Merge the task branch
- Push the task branch
- Open a new VSCode instance in the workspace of the task
- Create a new iteration
- Delete the task


Task workspace
Section titled “Task workspace”One of the core actions with the Rover VSCode extension is to open the worktree of the change in a new VSCode instance, in its own workspace. This ensures that your context (as a human) changes, and that you are working in the changes proposed by the agent.

Here, you can improve the changes that the agent proposed, and continue working as you’d do normally, committing changes, being able to push or merge those changes on another branch.
Your workflow does not have to change, Rover and the Rover VSCode extension will accomodate your workflow instead!