Build with Vector.

01

Install Vector

Download the installer that matches your computer, open it, and move through the operating system's installation flow. Vector is available for Apple silicon and Intel Macs, Windows, and Linux.

02

Open a repository

From Home, choose Open repository and select a local project folder. Vector attaches conversations, browser state, usage, engineering tools, and agent workspaces to that repository.

1. 1
   Open repository

   Select the folder containing the project you want to build.

2. 2
   Create a session

   Start with one clear outcome rather than a list of unrelated ideas.

3. 3
   Choose a model

   Use the provider and model already connected in Vector.

03

Run your first task

Describe the result, the constraints, and how Vector should verify the work. A strong first request is specific enough to test but small enough to review.

04

Vector Agent

The main session can inspect the repository, edit files, run commands, use project tools, and report a reviewable result. Use Plan mode when you want analysis without edits, and switch back to an editing mode when the plan is approved.

05

Agent workspaces

Use another workspace when work can happen independently: one agent can handle the interface while another investigates tests or infrastructure. Vector isolates each agent in a Git worktree or managed project copy so unfinished work does not alter the main files.

1. 1
   Create a workspace

   Name the responsibility and send its first request.

2. 2
   Keep working

   Switch between workspaces while they stream activity independently.

3. 3
   Review and merge

   Inspect the diff and checks before bringing selected work into main.

Two agents should not intentionally edit the same lines at the same time. Split work by responsibility to reduce conflicts and make review easier.

06

Codespace

Open Codespace when you want to work directly. It includes the project tree, editor tabs, syntax-aware editing, file search, diagnostics, and an editor agent connected to the active Vector session.

• Find a fileUse editor search to open project files without leaving Codespace.
• Edit normallyYour changes are written to the active repository or isolated workspace.
• Ask beside the codeUse the editor agent for focused explanations and edits.

07

Controlled browser

The Browser is attached to the current repository and session. Open a local preview or URL, interact manually, or ask Vector to inspect and test the page as part of the engineering task.

08

Terminal and Canvas

The Terminal runs commands inside the active repository. Canvas lets you arrange project tools together so the editor, terminal, browser, cloud view, and notes can stay visible while several threads of work are in motion.

09

Cloud Services

Cloud Services keeps publishing controls with the repository. Connect a supported hosting account, review the detected build settings, add environment values, and publish when the project is ready.

• DeploymentsCreate and inspect project deployments from Vector.
• DomainsOpen and copy the project URL from the deployment view.
• EnvironmentKeep deployment configuration separate from source files.
• DataAttach supported database workflows to the current project.

10

Models and BYOK

Connect a provider in Settings, then select a model in the session composer. Model availability, context limits, pricing, and rate limits come from the provider. Vector's usage view tracks the information returned by those sessions.

11

MCP and connections

MCP servers and project connections give an agent structured access to approved tools. Add only services you trust, confirm the permissions they request, and verify the connection before depending on it in a task.

A listed integration is not automatically connected. It becomes available only after its setup succeeds and Vector reports it as active.

12

Review and recovery

Review changed files before merging or publishing. Checkpoints preserve recoverable project states, while isolated workspace diffs show exactly what an agent wants to bring into the main branch.

13

Troubleshooting

14

Frequently asked questions