You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 fix: delete workspace by ID not path, fix title bar for local runtime
Bug fixes:
- Delete workspace filters by ID instead of path. For local project-dir
runtimes, all workspaces share the same path (project dir), so filtering
by path was deleting ALL local workspaces when one was deleted.
- WorkspaceHeader now uses metadata.name for display, fixing 'project/project'
title issue for local runtimes where namedWorkspacePath is the project path.
Docs:
- Split runtime docs into docs/runtime/{local,worktree,ssh}.md
- Add docs/runtime/index.md overview with comparison table
- Update cross-references in workspaces.md and vscode-extension.md
Tests:
- Add integration tests for local project-dir workspace deletion
- Verify only specified workspace is deleted, not all with same path
- Verify project directory is not deleted
Local runtime runs the agent directly in your project directory—the same directory you use for development. There's no worktree isolation; the agent works in your actual working copy.
4
+
5
+
## When to Use
6
+
7
+
- Quick one-off tasks in your current working copy
8
+
- Reviewing agent work alongside your own uncommitted changes
9
+
- Projects where worktrees don't work well (e.g., some monorepos)
10
+
11
+
## Caveats
12
+
13
+
⚠️ **No isolation**: Multiple local workspaces for the same project see and modify the same files. Running them simultaneously can cause conflicts. mux shows a warning when another local workspace is actively streaming.
14
+
15
+
⚠️ **Affects your working copy**: Agent changes happen in your actual project directory.
16
+
17
+
## Filesystem
18
+
19
+
The workspace path is your project directory itself. No additional directories are created.
Copy file name to clipboardExpand all lines: docs/runtime/worktree.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# Local Workspaces
1
+
# Worktree Runtime
2
2
3
-
Local workspaces use[git worktrees](https://git-scm.com/docs/git-worktree) on your local machine. Worktrees share the `.git` directory with your main repository while maintaining independent working changes and checkout state.
3
+
Worktree runtime (the default) uses[git worktrees](https://git-scm.com/docs/git-worktree) on your local machine. Worktrees share the `.git` directory with your main repository while maintaining independent working changes and checkout state.
4
4
5
5
## How Worktrees Work
6
6
@@ -10,7 +10,7 @@ It's important to note that a **worktree is not locked to a branch**. The agent
10
10
11
11
## Filesystem Layout
12
12
13
-
Local workspaces are stored in `~/.mux/src/<project-name>/<workspace-name>`.
13
+
Worktree workspaces are stored in `~/.mux/src/<project-name>/<workspace-name>`.
Copy file name to clipboardExpand all lines: docs/workspaces.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,23 @@
2
2
3
3
Workspaces in mux provide isolated development environments for parallel agent work. Each workspace maintains its own Git state, allowing you to explore different approaches, run multiple tasks simultaneously, or test changes without affecting your main repository.
4
4
5
-
## Workspace Types
5
+
## Runtimes
6
6
7
-
mux supports two workspace backends:
7
+
mux supports three [runtime types](./runtime/index.md):
8
8
9
-
-**[Local Workspaces](./local.md)**: Use [git worktrees](https://git-scm.com/docs/git-worktree) on your local machine. Worktrees share the `.git` directory with your main repository while maintaining independent working changes.
9
+
-**[Worktree](./runtime/worktree.md)** (default): Isolated directories using [git worktrees](https://git-scm.com/docs/git-worktree). Worktrees share `.git` with your main repository while maintaining independent working changes.
10
10
11
-
-**[SSH Workspaces](./ssh.md)**: Regular git clones on a remote server accessed via SSH. These are completely independent repositories stored on the remote machine.
11
+
-**[Local](./runtime/local.md)**: Run directly in your project directory. No isolation—best for quick edits to your working copy.
12
12
13
-
## Choosing a Backend
13
+
-**[SSH](./runtime/ssh.md)**: Remote execution over SSH. Ideal for heavy workloads, security isolation, or leveraging remote infrastructure.
14
14
15
-
The workspace backend is selected when you create a workspace:
15
+
## Choosing a Runtime
16
16
17
-
-**Local**: Best for fast iteration, local testing, and when you want to leverage your local machine's resources
18
-
-**SSH**: Ideal for heavy workloads, long-running tasks, or when you need access to remote infrastructure
17
+
The runtime is selected when you create a workspace:
18
+
19
+
-**Worktree** (default): Best for parallel agent work with isolation
20
+
-**Local**: Quick tasks in your current working copy
21
+
-**SSH**: Heavy workloads, security, or remote infrastructure
0 commit comments