workspace
├── repos
│ ├── frontend
│ └── backend
└── .arashi
├── config.json
└── worktrees
├── auth
│ └── repos
│ ├── frontend
│ └── backend
└── logs
└── repos
├── frontend
└── backend
$arashi init
$arashi add git@github.com:acme/backend.git
$arashi add git@github.com:acme/frontend.git
$arashi create logs
$arashi create auth
$arashi switch auth
$arashi switch logs
$arashi switch main
Arashi
Coordinate Git worktrees across every repository in your stack.
嵐 (Arashi) - The eye of the storm for your development workflow
Arashi manages aligned worktrees across multiple repositories within a shared meta-repository. It streamlines creating, switching, and managing changes across your whole stack.
curl -fsSL https://arashi.haphazard.dev/install | bashpowershell -c "irm https://arashi.haphazard.dev/install.ps1 | iex"npm install -g arashiarashi installpnpm add -g arashiarashi installbun add -g arashiarashi installvp i -g arashi@latestarashi installChoose Your Path
Section titled “Choose Your Path”- New to Arashi or setting up a meta-repo? Open Getting Started.
- Need hooks or command defaults? Open Hooks or Config.
- Working with agents in a meta-repo? Open Agents.
- Using VS Code? Open VS Code.
- Using tmux or
sesh? Open tmux and sesh. - Looking for command behavior? Open Commands.
- Contributing to Arashi? Open Contributing.
- Need Arashi temporarily in a project that has not adopted it? Use the Standalone Repository workflow.
Configured mode is preferred whenever it is available—even for one repository—because it supports hooks, defaults, custom paths, and coordination. Standalone mode provides an ad hoc .worktrees/<branch> convention for an otherwise-unconfigured project.