futpib / slopd / 27026771549

86%

Build Type

push

github

Committed by futpib

Commit Message

fix: resolve relative `run --start-directory` against slopctl's cwd

A relative `-c`/`--start-directory` (e.g. `.`) was forwarded to slopd
verbatim, expanded there, and handed to tmux. Because slopd is a
long-lived daemon with its own working directory, `.` resolved against the
daemon's cwd (typically the user's home) rather than the directory the
user ran `slopctl` from, so `slopctl run -c .` started the pane in the
wrong place.

Resolve relative paths against slopctl's own working directory before the
Run request leaves the client. Paths beginning with `~` or containing
`$VAR`, and already-absolute paths, pass through untouched, so slopd still
expands `~`/`$VAR` against its own (possibly remote) environment as
documented.

mock_claude gains a `/cwd` control command so the new e2e test
(run_resolves_relative_start_directory_against_slopctl_cwd) can assert the
spawned pane's actual working directory.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Coverage Stats

11 of 17 new or added lines in 2 files covered. (64.71%)

21 existing lines in 1 file now uncovered.

4346 of 5014 relevant lines covered (86.68%)

2141727.89 hits per line