Summary
The clide container has python3 but not pip (pip, pip3, and python3 -m pip all missing). This blocks installing sdale, which is now a core workflow tool for agent-driven VPS work.
Current workaround
PYTHONPATH=/workspace/clide-sdale python3 -m sdale <command> <dale> [args...]
This works but requires knowing the workaround. The workspace CLAUDE.md documents it, but new sessions sometimes miss it.
Options
- Add
python3-pip to the Dockerfile — minimal change, lets agents pip install -e /workspace/clide-sdale
- Pre-install sdale in the image —
pip install -e /workspace/clide-sdale in Dockerfile. Zero setup per session.
- Add sdale to PATH via entrypoint — symlink or PYTHONPATH export in entrypoint.sh so it's always available
Option 2 or 3 is preferred — sdale is used in every VPS-related session and shouldn't require per-session setup.
Source
Session hiccup log: workspace/tickets/session-hiccups-2026-03-20.md (#1, #4)
Summary
The clide container has
python3but notpip(pip,pip3, andpython3 -m pipall missing). This blocks installing sdale, which is now a core workflow tool for agent-driven VPS work.Current workaround
This works but requires knowing the workaround. The workspace CLAUDE.md documents it, but new sessions sometimes miss it.
Options
python3-pipto the Dockerfile — minimal change, lets agentspip install -e /workspace/clide-sdalepip install -e /workspace/clide-sdalein Dockerfile. Zero setup per session.Option 2 or 3 is preferred — sdale is used in every VPS-related session and shouldn't require per-session setup.
Source
Session hiccup log:
workspace/tickets/session-hiccups-2026-03-20.md(#1, #4)