Back to Signal Feed
CodeTracked since May 17, 2026

Add Grok as a first-class agent in Codeg’s local ACP flow

Codeg now treats Grok as a native local ACP binary agent, registering it in the shared ACP registry and routing install/update/uninstall through the existing local binary cache path instead of a Grok-specific remote or resolver flow.

GrokACP registrybinary stdio agentbinary cache

What Happened

  • Codeg now treats Grok as a native local ACP binary agent, registering it in the shared ACP registry and routing install/update/uninstall through the existing local binary cache path instead of a Grok-specific remote or resolver flow.
  • Codeg now treats Grok as a native local ACP binary agent, registering it in the shared ACP registry and routing install/update/uninstall through the existing local binary cache path instead of a Grok-specific remote or resolver flow.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced Grok into the standard ACP local-agent path by registering it as `grok agent stdio` and binding it to existing binary-agent lifecycle logic, removing the need for a dedicated Grok remote registry while adding Grok MCP config and session parsing hooks.

Why Track This

Why It Matters

Users who deploy Codeg can onboard and manage Grok using the same local ACP tooling as other agents, so Grok no longer requires a separate setup path and is easier to install and maintain through existing workflows. This also means new Grok sessions should behave more consistently with existing local-agent operations because registration, updates, and cleanup now share the shared ACP registry + binary-cache behavior. Continue to watch for platform-specific failures in raw executable downloads and any regressions in Grok session resume/transcript handling that could block first-time setup or reopened sessions.

Impact

Users who deploy Codeg can onboard and manage Grok using the same local ACP tooling as other agents, so Grok no longer requires a separate setup path and is easier to install and maintain through existing workflows. This also means new Grok sessions should behave more consistently with existing local-agent operations because registration, updates, and cleanup now share the shared ACP registry + binary-cache behavior. Continue to watch for platform-specific failures in raw executable downloads and any regressions in Grok session resume/transcript handling that could block first-time setup or reopened sessions.

What To Watch Next

  • Watch whether Grok becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: watch_raw_executable_download_failures, watch_grok_mcp_config_schema_compatibility.
Open Topic TimelineOpen Technical EventOpen Original Sourcewatch_raw_executable_download_failures / watch_grok_mcp_config_schema_compatibility / watch_session_resume_parser_edge_cases

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

xintaofei/codeg PR #186: [codex] Add Grok via unified ACP flow

Registers `grok agent stdio` in the shared ACP registry and reuses the existing binary-agent install/update/uninstall flow.