Wrap pi-mono coding agent in Docker, Makefile and a ppi CLI launcher
Session from combust-labs_pi-mono-docker on Hugging Face by rgruchalski · Apache-2.0 · condensed by Coders Talk
Build out Docker/Makefile tooling around the pi-mono coding agent image, then iterate on a ppi launcher script (version handling, paths) via a series of feature branches merged into main.
- +0Prompt · +0Summarize current the project
- +0mAgent did · +0mExplored the repo (Dockerfile, pi CLI script, .git, .pi sessions) and produced a project overview table.
- +3mPrompt · +3mAdd a Makefile with a build-docker target that reads the version from the Dockerfile and runs docker build -t localhost/pi-mono:<version> .
- +3mAgent did · +3mIteratively built out Makefile targets (build-docker, install-ppi, hf-push-sessions), added README.md and ppi launcher script, restructured Dockerfile into container/Containerfile, added GIT_REPO build arg, committing and merging each change into main via feature branches with model-credited commit messages.
- +31mFail · +31mDocker build failed: 'fatal: repository . does not exist' when cloning via the GIT_REPO build arg.
- +31mAgent did · +31mFixed the GIT_REPO default URL and quoted it in the Containerfile to resolve the clone failure.
- +39mIntervention · +39mAfter many repeated 'could not find edits' failures trying to swap the hardcoded version string in ppi, the developer told the agent to just use bash sed instead of the edit tool.Why: The edit tool kept failing on non-unique/whitespace-mismatched text; sed was the fast, obvious fix and I said so directly instead of watching more failed attempts.
- +47mIntervention · +47mAfter the agent again got stuck on ambiguous edit matches while updating path variables in ppi, the developer fixed the file by hand and told the agent to reload it.Why: The agent was looping on 'found 2 occurrences' errors, so I just made the change myself and had it re-read the file rather than keep debugging the edit tool.
- +48mOutcome · +48mFinal commit 76d2c56 on main updates ppi to use a base directory variable for paths and version handling; working tree clean.
Next time I'd give the agent the full Containerfile/ppi layout upfront and tell it to use sed/grep for simple string replacements instead of the fragile edit-with-exact-match tool, since that tool repeatedly failed on non-unique or whitespace-sensitive matches. Stepping in to hand-edit ppi myself and telling it to just reload, and telling it to use sed directly, were what actually got things unstuck rather than letting it retry the same edit approach.