Skip to content
Arashi logoArashi

Workflows

Use this section when you want outcome-focused guidance instead of a command-by-command reference. Arashi’s primary workflow coordinates worktrees across the repositories in a configured meta-repo.

Choose a Workflow

Section titled “Choose a Workflow”
  • Config for workspace layout, repositories, worktree behavior, and command defaults.
  • Hooks for lifecycle automation around create and remove.
  • Agents and Automation for implementation boundaries, handoffs, and machine-readable command use.
  • VS Code for editor-first worktree management.
  • Launch disposition for default independent windows/sessions, one-invocation --tab, precedence, and terminal support.
  • tmux and sesh for terminal-native switching and session workflows.
  • Herdr for persistent workspace focus/reuse while Arashi retains Git worktree ownership.
  • cmux for automatic workspace creation and focus from cmux-managed terminals.
  • Kitty for automatic exact worktree-window reuse and live Kitty session ownership.
  • delete for configured dependency deletion; remove remains for branch worktrees.
  • Standalone Repository for ad hoc use in a project that has not adopted Arashi configuration.
Section titled “Recommended Path After aw init”
  1. Confirm the repository-local managed ignore default or deliberately select tracked or none for this clone.
  2. Configure root and repository base branches when create and clone need stable integration ancestry, then set defaults.create and defaults.switch for launch behavior.
  3. Add lifecycle hooks if you need setup or cleanup automation around create and remove.
  4. Choose how you want to open worktrees: VS Code, Herdr workspace reuse, automatic cmux or Kitty contexts, terminal-native tmux flows, or sesh-driven session switching.
  5. If you work with agents, keep code changes in the affected project repo and shared context in the meta-repo.
Section titled “Related Commands”