podman run -d returns before the container process is running.
CS Core's claude-code check immediately calls our wrapper, which
found the container not yet running and exited 1 — causing the
"claude-code not found" error.
Add a poll loop (10 x 0.5s) that waits for State.Running=true
before setting PATH and launching CS Core.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- New lib/container.sh generates three files per project:
- bin/claude: wrapper that routes every claude call into the
agents container via `podman/docker exec --workdir $PWD`
- start.sh: builds image if missing, starts detached container
with project mounted at same absolute path as host, prepends
bin/ to PATH, then launches CS Core on the host
- stop.sh: stops and removes the agents container
- Container mounts project at identical host path so CS Core's
working directory paths resolve correctly inside the container
- TTY detection in wrapper: uses -it when stdin is a terminal,
-i otherwise (node-pty compatibility)
- Container stopped automatically when CS Core exits
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
