claudemesh-cli 1.9.4 → 1.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -126,8 +126,29 @@ gnome-terminal -- bash -lc 'claudemesh launch --name "Lug Nut" --mesh openclaw -
|
|
|
126
126
|
|
|
127
127
|
# screen detached:
|
|
128
128
|
screen -dmS lugnut bash -lc 'claudemesh launch --name "Lug Nut" --mesh openclaw -y'
|
|
129
|
+
|
|
130
|
+
# Windows Terminal (wt.exe) — open a new tab:
|
|
131
|
+
wt.exe new-tab --title claudemesh-lugnut powershell -NoExit -Command "claudemesh launch --name 'Lug Nut' --mesh openclaw -y"
|
|
132
|
+
|
|
133
|
+
# Windows Terminal — split the current pane vertically instead:
|
|
134
|
+
wt.exe split-pane -V powershell -NoExit -Command "claudemesh launch --name 'Lug Nut' --mesh openclaw -y"
|
|
135
|
+
|
|
136
|
+
# PowerShell — spawn a detached window of the user's default shell:
|
|
137
|
+
Start-Process powershell -ArgumentList '-NoExit','-Command','claudemesh launch --name "Lug Nut" --mesh openclaw -y'
|
|
138
|
+
|
|
139
|
+
# cmd.exe — start a new console window:
|
|
140
|
+
start "claudemesh-lugnut" cmd /k "claudemesh launch --name ""Lug Nut"" --mesh openclaw -y"
|
|
141
|
+
|
|
142
|
+
# WSL from a Windows host — same launch verb, just route through wsl.exe:
|
|
143
|
+
wsl.exe -- bash -lc 'claudemesh launch --name "Lug Nut" --mesh openclaw -y'
|
|
129
144
|
```
|
|
130
145
|
|
|
146
|
+
Windows-specific gotchas:
|
|
147
|
+
- **Single quotes don't nest in cmd.exe.** Use `""` to escape inner double quotes (see the `cmd /k` example) or move to PowerShell where single quotes work normally.
|
|
148
|
+
- **`-NoExit`** is the PowerShell equivalent of bash's `exec` + interactive shell — keeps the window open after `claudemesh launch` returns control to its child `claude` process. Without it, the window closes when the launch script exits.
|
|
149
|
+
- **WSL paths.** If you spawn from a Windows-side script into WSL, the `claudemesh` CLI in WSL writes to `~/.claudemesh/` on the Linux side, *not* `%USERPROFILE%\.claudemesh\`. The two installs are independent — match the spawn host to the install host.
|
|
150
|
+
- **Windows Terminal profile names.** Replace `powershell` with `pwsh` for PowerShell 7+, or use `--profile "<name>"` to target a configured profile (e.g. one preconfigured with WSL Ubuntu + a starting directory).
|
|
151
|
+
|
|
131
152
|
The user's environment may also have these pre-built helpers (CLAUDE.md will tell you):
|
|
132
153
|
|
|
133
154
|
- `~/tools/scripts/spawn-iterm-panes.sh` and `spawn-iterm-window.sh` — safer iTerm spawners that only write into sessions they themselves created.
|