Code Workspace
https://github.com/forrestchang/code-workspace- Category
- Developer Tools
- Rank
- No. 1695Tools index
Previous survey · No. 1702 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- forrestchang
- GitHub
- 11 stars
- Latest release
- codex-mobile-multica-workdir-screenshot-1779162250
- Date
About
Git worktree-based workspace management for Claude Code, switch between parallel agent sessions cleanly.
What it does
Code Workspace provisions an isolated checkout for a task, creates a fresh branch, installs JavaScript dependencies when detected, and opens Claude Code with branch and workspace context. A companion command removes the checkout after confirmation and can also delete its local branch.
Why it's ranked here
The tool earns attention because it compresses a useful multi-command routine into two small, readable shell commands. Its branch creation, dependency detection, context injection, and guarded cleanup form a coherent workflow. The narrow scope is also a constraint: portability, extensibility, and broader project setup receive little attention.
What's good
Workspace names avoid directory collisions, while generated branches include the configured Git user and workspace name. New branches start from the fetched remote default branch when an origin exists. Cleanup warns about uncommitted changes, requires confirmation, and asks separately before deleting the branch.
Tradeoffs
Creation fetches from the origin automatically and requires the external randomization utility used to shuffle names. Dependency setup only recognizes JavaScript manifests and four package managers. Cleanup force-removes the worktree after confirmation, even when changes remain. The finite built-in name list can also be exhausted.
How to use it well
Use it when Claude Code users regularly split repository work into isolated branches and want disposable local environments with minimal ceremony. It fits JavaScript projects best because dependency installation is built in. It does not provide non-JavaScript environment setup, pull request creation, continuous integration, or multi-agent orchestration.
Technical notes+
new-workspace is a Bash CLI using set -euo pipefail; it validates Git state, selects a free entry from CITIES through shuf, derives BRANCH_NAME, fetches origin, resolves its default branch, runs git worktree add, detects pnpm, Bun, Yarn, or npm lockfiles, and replaces itself with claude --append-system-prompt. rm-workspace verifies that .git is a file, checks status, confirms removal, calls git worktree remove --force, then optionally runs forced branch deletion. install.sh marks both commands executable and symlinks them into BIN_DIR, defaulting to $HOME/.local/bin. README.md also documents direct PATH setup and WORKSPACES_BASE.
Observed
- Primary language
- Bash shell scripts
- Interface
- Two command-line commands for workspace creation and removal
- Installation surface
- Direct PATH addition or symlinks created by an installer script
- Required integrations
- Git and the Claude Code command-line tool
- Dependency support
- Automatic installation for pnpm, Bun, Yarn, and npm projects
- Configuration
- Workspace root can be changed through the WORKSPACES_BASE environment variable
Read from README.md, install.sh, rm-workspace, new-workspace.
What it can do
Create isolated Git worktree-based workspaces
Git repository → Separate workspace environment
Switch between parallel Claude Code agent sessions
Multiple active agent sessions → Clean transition to selected session
Manage multiple concurrent coding projects
Multiple code projects → Organized workspace separation
Isolate agent work environments
Claude Code agent instance → Dedicated workspace environment
Maintain clean separation between coding contexts
Different coding tasks or projects → Isolated development environments
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.