setup.sh skips agent self-name + session-pulse wiring on Windows (python3 not on git-bash PATH) #171

New issue

Closed

opened 2026-06-04 11:14:30 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 11:14:30 +00:00

Owner

Symptom — On the Windows host (git-bash), agentic-os/setup.sh prints skipped agent self-name + session-pulse wiring (python3 not on PATH) and agentic_os.agent_compose never runs, because python3 is absent from the git-bash PATH even though interpreters exist (C:\PythonNN\python.exe, chocolatey, uv-managed). uv itself is on PATH.

This is the sibling-repo half of coilyco-bridge/agentic-os-kai#451, which fixed the same gap in agentic-os-kai/setup.sh by adding a resolve_python helper that probes python3 -> python -> py -3 -> uv run --python 3.13 python and invokes scripts through $PYTHON instead of the bare #!/usr/bin/env python3 shebang.

Fix idea — Port the same resolve_python helper into agentic-os/setup.sh and gate the install-agent-name.py / install-session-pulse.py / agent_compose block on $PYTHON instead of command -v python3. The agent_compose step needs PyYAML, so prefer uv run --with pyyaml python -m agentic_os.agent_compose when uv is present (mirroring the capability-pull step in agentic-os-kai), falling back to $PYTHON otherwise.

See the agentic-os-kai fix commit for the helper shape.

**Symptom** — On the Windows host (git-bash), `agentic-os/setup.sh` prints `skipped agent self-name + session-pulse wiring (python3 not on PATH)` and `agentic_os.agent_compose` never runs, because `python3` is absent from the git-bash PATH even though interpreters exist (`C:\PythonNN\python.exe`, chocolatey, uv-managed). `uv` itself is on PATH. This is the sibling-repo half of coilyco-bridge/agentic-os-kai#451, which fixed the same gap in `agentic-os-kai/setup.sh` by adding a `resolve_python` helper that probes `python3 -> python -> py -3 -> uv run --python 3.13 python` and invokes scripts through `$PYTHON` instead of the bare `#!/usr/bin/env python3` shebang. **Fix idea** — Port the same `resolve_python` helper into `agentic-os/setup.sh` and gate the `install-agent-name.py` / `install-session-pulse.py` / `agent_compose` block on `$PYTHON` instead of `command -v python3`. The `agent_compose` step needs PyYAML, so prefer `uv run --with pyyaml python -m agentic_os.agent_compose` when uv is present (mirroring the capability-pull step in agentic-os-kai), falling back to `$PYTHON` otherwise. See the agentic-os-kai fix commit for the helper shape.

coilysiren added the

label

2026-06-17 07:05:15 +00:00

coilysiren commented

2026-06-17 08:23:06 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:06 +00:00