Command Reference
Exhaustive Rover command reference.
$PATH
environment variableThe first step, as happens with the CLI, is to initialize the repository where you want to enable Rover.
If no workspace is open, the initialization guide will suggest you to open a workspace.
After opening a workspace, you will see a button to Initialize Rover
on it.
Now you are ready to create tasks!
You can create a new task by filling the task text field.
After creation, you will see the new task in the list.
The status of the tasks will be automatically refreshed in this listing as they progress.
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.
The task will progress and eventually reach the Completed
status. Here you can see some actions you can perform from the UI, such as:
context.md
, plan.md
, review.md
, summary.md
)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!
Command Reference
Exhaustive Rover command reference.
Overview
Rover Overview.
Quickstart
Experiment hands-on with Rover on your own projects or start with an empty one.
Common Workflows
Read more about common workflows with Rover and how they make you more productive. From initialization all the way down to debugging.