Posts

Notably, when you install a pi.dev extension, the harness never actually reads or tries to present the README.md documentation associated with the extensions installed. Often, the new ecosystem of harness extensions coming forward are not just only extensible, but may also require some aspect of configuration up-front. https://pi.dev/packages $ pi --version 0.85.1 The pi.dev system prompt already advertises skills with their locations and descriptions. However, this rule is not applied for extensions. Therefore pi.dev agent treats extensions like opaque blobs of code, without any help documentation. ...

https://github.com/affaan-m/ECC The Basic Premise: plan -> test -> implement -> review -> verify -> remember -> improve Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills and workflows. I am not a fan of this harness extension for a variety of reasons: ...