> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/integration-and-plugins/visual-code-extension.md).

# VS Code Extension

### About Visual Studio Code Extension

AutoRABIT offers a suite of products to automate CI/CD and data and metadata backup processes for Salesforce. The [Automated Release Management (ARM)](https://www.autorabit.com/products/automated-release-management/) suite for Salesforce allows teams to configure, build, test, and manage development environments and deployments on their Salesforce instance.

This will help Salesforce developers, admins, analysts, and release managers with out-of-the-box automation of version control.

### Purpose

VS Code extension allows our developers to commit code via a pre-validation framework, thereby boosting team productivity.

### Prerequisites

Before you get started working with the VS Code Extension, you need to:

1. Download the [Visual Studio Code installer](https://code.visualstudio.com/download) for your platform.
2. Install the [AutoRABIT Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=autorabit-dev.autorabit) on your system.
3. Have GIT installed on your local computer. Even if it is already installed, it is probably a good idea to update to the latest version. To install GIT, click [HERE](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). 
4. Create an API token in AutoRABIT to connect to the extension. If you’re not aware of how to create an API token, refer to the documentation: [Create API Token](/product-guides/arm-1/troubleshoot/how-tos/create-api-token.md).
5. Have a Version Control repo/branch registered within AutoRABIT.
6. Have a Salesforce Org configured within AutoRABIT.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/integration-and-plugins/visual-code-extension.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.