coily upgrade and setup both fail on Windows hosts #151

Open
opened 2026-05-28 12:53:22 +00:00 by coilysiren · 0 comments
Owner

Two Windows bugs in coily, found running coily exec up-to-date on kai-desktop-tower

1. coily upgrade assumes brew, has no scoop branch

On Windows, coily upgrade runs brew update / brew outdated coilysiren/tap/coily:

==> brew outdated coilysiren/tap/coily
coily: shell: brew not found on PATH: exec: "brew": executable file not found in %PATH%
    kind: generic
    message: 'shell: brew not found on PATH...'

Windows installs coily via scoop (coilysiren/scoop-bucket), not brew. The upgrade path is brew-only and fails on every Windows host. It should detect the platform (or the install source) and use scoop update coily on Windows, mirroring how the mac/linux path uses brew.

2. coily setup aborts on unset SHELL

==> install-completion
coily: install-completion: could not detect shell from $SHELL. Pass --shell bash|zsh|fish
    kind: generic
    message: 'install-completion: could not detect shell from $SHELL...'
coily: setup: install-completion: exit status 1

git-bash on Windows leaves the SHELL env var unset, so the install-completion step of coily setup fails and takes the whole coily setup down with it. Options: default to bash when SHELL is unset, detect the shell another way (parent process, $0), or make install-completion non-fatal within setup (warn + continue) so a missing completion target doesn't abort host setup.

Impact

Both land as hard FAILs in step 1 of the up-to-date host-freshness tracker on Windows, blocking the "tooling currency" gate. Neither is reproducible on mac/linux.

Context

Found 2026-05-28 alongside a batch of Windows-portability fixes in agentic-os / agentic-os-kai (CRLF normalization, bare-python3 -> uv-run verbs, bash path mangling, error-surfacing in the tracker). Broader script-portability audit: coilysiren/agentic-os-kai#482. Release-mechanics convergence: coilysiren/agentic-os-kai#474.

## Two Windows bugs in coily, found running `coily exec up-to-date` on kai-desktop-tower ### 1. `coily upgrade` assumes brew, has no scoop branch On Windows, `coily upgrade` runs `brew update` / `brew outdated coilysiren/tap/coily`: ``` ==> brew outdated coilysiren/tap/coily coily: shell: brew not found on PATH: exec: "brew": executable file not found in %PATH% kind: generic message: 'shell: brew not found on PATH...' ``` Windows installs coily via scoop (`coilysiren/scoop-bucket`), not brew. The upgrade path is brew-only and fails on every Windows host. It should detect the platform (or the install source) and use `scoop update coily` on Windows, mirroring how the mac/linux path uses brew. ### 2. `coily setup` aborts on unset SHELL ``` ==> install-completion coily: install-completion: could not detect shell from $SHELL. Pass --shell bash|zsh|fish kind: generic message: 'install-completion: could not detect shell from $SHELL...' coily: setup: install-completion: exit status 1 ``` git-bash on Windows leaves the SHELL env var unset, so the install-completion step of `coily setup` fails and takes the whole `coily setup` down with it. Options: default to bash when SHELL is unset, detect the shell another way (parent process, `$0`), or make install-completion non-fatal within `setup` (warn + continue) so a missing completion target doesn't abort host setup. ## Impact Both land as hard FAILs in step 1 of the `up-to-date` host-freshness tracker on Windows, blocking the "tooling currency" gate. Neither is reproducible on mac/linux. ## Context Found 2026-05-28 alongside a batch of Windows-portability fixes in agentic-os / agentic-os-kai (CRLF normalization, bare-python3 -> uv-run verbs, bash path mangling, error-surfacing in the tracker). Broader script-portability audit: coilysiren/agentic-os-kai#482. Release-mechanics convergence: coilysiren/agentic-os-kai#474.
coilysiren added
P2
and removed
P1
labels 2026-05-31 06:59:40 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-bridge/coily#151
No description provided.