workspacer

workspacer

A CLI tool (ws) for managing related git worktrees in a dedicated workspace folder. Uses worktrunk (wt) to create and manage worktrees across multiple repos.

Prerequisites

• worktrunk must be installed and available as wt in your PATH.

Installation

Homebrew (macOS / Linux)

brew install seakayone/tap/workspacer

From source

cargo install --path .

From GitHub

cargo install --git https://github.com/seakayone/workspacer

This installs the ws binary into your Cargo bin directory (usually ~/.cargo/bin/).

Releasing

# Bump version in Cargo.toml, then:
git commit -am "Release vX.Y.Z"
git tag vX.Y.Z
git push origin main --tags

CI automatically builds binaries for macOS (ARM + Intel) and Linux, creates a GitHub Release, and updates the Homebrew tap.

During development you can also run it via:

cargo run -- <command>

Shell integration

Add this to your ~/.zshrc (or ~/.bashrc) so that ws switch changes your shell's directory:

eval "$(ws shell-init)"

Setup

Create a template that defines which repos belong together:

ws template add my-project --repo /path/to/repo-a --repo /path/to/repo-b

Optionally set a custom workspace directory (defaults to ~/workspaces):

ws config --workspace-dir /path/to/workspaces

Usage

ws new <name> [-t <template>]     # Create worktrees via `wt switch --create`
ws switch [name]                  # Switch to a workspace (TUI picker if name omitted)
ws list                           # List all workspaces
ws remove <name> [-t <template>]  # Remove worktrees via `wt remove` and clean up
ws repo add <path>                # Add a repo worktree to the current workspace
ws repo remove <name>             # Remove a repo worktree from the current workspace

If only one template exists, it is used automatically. Otherwise pass -t <template>.

How it works

When creating a workspace, ws overrides worktrunk's worktree-path via the WORKTRUNK_WORKTREE_PATH environment variable so that all worktrees are placed inside the workspace directory:

<workspace_dir>/<workspace>/<repo>/

This does not change your worktrunk user config.

Managing repos in a workspace

ws repo add <path>      # Add a repo worktree (must be inside a workspace)
ws repo remove <name>   # Remove a repo by its directory name in the workspace

ws repo remove supports tab-completion of repo names in the current workspace.

Aliases

• ws ls = ws list
• ws rm = ws remove
• ws repo rm = ws repo remove

Managing templates

ws template list                          # List all templates
ws template add <name> --repo <path> ...  # Create or extend a template
ws template remove <name>                 # Delete a template
ws template remove <name> --repo <path>   # Remove specific repos from a template
ws template show <name>                   # Show repos in a template

Template subcommands also support ls and rm aliases.

Configuration

ws config                         # Show current configuration
ws config --workspace-dir <path>  # Set the workspace directory

Config is stored at ~/.config/workspacer/config.json.

Key	Default	Description
workspace_dir	~/workspaces	Directory where workspaces are created
templates	{}	Named sets of repo paths for worktree creation

Claude Code plugin

Workspacer ships with a Claude Code plugin that tracks agent activity per workspace. When active, ws list shows 🤖 (working) or 💬 (waiting for input) next to each workspace.

Install the plugin:

# Add the local repo as a marketplace
claude plugin marketplace add /path/to/workspacer

# Install the plugin from that marketplace
claude plugin install workspacer@workspacer

The plugin uses Claude Code hooks to automatically set and clear the agent state:

Event	Marker
UserPromptSubmit	🤖
Notification	💬
SessionEnd	(cleared)

You can also manage the agent state manually:

ws agent set 🤖    # Set marker (detects workspace from cwd)
ws agent clear     # Clear marker