You Can Have Your Pi and Kepler It Too

Kepler can now use the minimalist Pi agent through the third-party pi-acp proxy, which implements the Agent Client Protocol used by agent development environments to communicate with CLI harnesses such as Claude Code, Codex, and OpenCode. While setup is straightforward after installing Pi and pi-acp, Kepler currently displays inaccurate permission modes and thinking levels because pi-acp hardcodes effort settings rather than using Pi’s newer available-thinking-levels function, and because Pi’s intentionally permissive default behavior does not map cleanly to Kepler’s expected permission-level system. The author plans to contribute fixes to pi-acp, while Kepler’s team is considering how to support agents without permission modes. Although Pi’s plugin ecosystem can add features such as subagents and research tools, the author argues that ACP support is fundamental enough to be integrated directly into Pi rather than maintained through a plugin or external proxy.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.