$ the-wire · showcase
OpenCode's daemon protocol breaks compatibility, gemini-cli ships v0.67.0
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
OpenCode's pty daemon moves to protocol v8 and discards v7 handoffs, while gemini-cli v0.67.0 finally delivers shell command output to ACP clients and Codex binds memory consolidation permissions to the memory directory.
feat(process-daemon): protocol v8 for shell commands anomalyco/opencode
Protocol v8 for opencode-pty lets OpenCode run local shell commands inside the daemon in pipe mode and keep them across a planned server restart. The PR calls it a breaking bump: a v8 server discards a v7 handoff and starts a fresh daemon, so persistent terminals start over.
fix(cli): serialize AnsiOutput to text content in ACP tool call updates google-gemini/gemini-cli
toToolCallContent() returned null when a tool result's returnDisplay was an AnsiOutput array, so run_shell_command output reached ACP clients as empty content arrays. The fix flattens AnsiOutput into a text content block, which means shell output now actually arrives in your ACP client.
Bind memory consolidation permissions to the memory root openai/codex
Managed memory consolidation agents now get a PermissionProfile explicitly, with configuration and permission workspace roots bound to the memory directory, network access disabled, and temp directories excluded from writable roots. Inherited workspace roots stay readable; disabled and externally managed parent profiles are preserved.
Keep threads on their saved model provider when defaults change openai/codex
Changing the default model provider used to strand threads configured against another provider. Cold resumes now resolve through the thread's saved provider, explicit provider switches on resume are rejected, and loaded threads use retained provider config while managed provider policy still applies.
Release v0.67.0 google-gemini/gemini-cli
v0.67.0 is out, and the changelog leads with bridging the IDE companion into container sandboxes over exec stdio. The release also carries the ACP shell-output and template placeholder fixes landing in the same window.
fix(automations): show the repository provider's logo on template cards OpenHands/OpenHands
The long tail: OpenHands is quietly rebuilding its automation template setup, with a Bitbucket Data Center and Azure DevOps repository picker, provider-scoped repo payloads, and event-source awareness in the setup assistant. For now it is tested against mocks, not a live Data Center instance.
Action items