Skip to content
Arashi logo Arashi

VS Code

Use this guide when VS Code or a VS Code-based editor is your primary destination for opening and managing Arashi worktrees.

Cursor and Kiro are VS Code forks, so the same editor-first workflow generally applies there as well. This page focuses on VS Code because the Arashi extension is published through the standard VS Code extension ecosystems.

Open a Worktree in VS Code

Use the CLI when you are already in the terminal and want to open a specific worktree immediately.

Terminal window
arashi switch --vscode feature-auth
  • Best for editor-first workflows where the terminal is secondary.
  • Good default when your team reviews changes primarily inside VS Code.
  • Useful when you want a one-off editor launch without changing workspace defaults.

Install the VS Code Extension

Install the Arashi extension when you want Arashi controls inside the editor, not just a one-off CLI launch.

With the extension installed, you can:

  • run core Arashi commands from the command palette, including init, add, clone, create, pull, sync, switch, and remove
  • browse available worktrees in the Arashi Worktrees explorer view, including repo, branch, path, and change status
  • use inline worktree actions to switch, remove, or add repositories without leaving the editor
  • review command diagnostics in the Arashi output channel when setup or command execution fails
  • respond to startup warnings in-editor, including a shortcut to run Arashi: Init Workspace
  • Use arashi switch --vscode <branch> when you are already in the terminal and want VS Code to open a specific worktree immediately.
  • Use the extension when VS Code is your primary shell for day-to-day worktree management and you want a persistent worktree panel.
  • Set arashi.binaryPath, arashi.workspaceRoot, or arashi.commandTimeoutMs in VS Code settings when the editor should target a specific binary or workspace root.
  • Use --cursor or --kiro when you want the same VS Code-style workflow in those editors.