fix(cloud-codex): pin Cody's registryAgentName to 'codex'#364
Merged
Conversation
…codex) The cleanup sweep that runs during reprovision marks any AgentInstallation whose agentName has no AGENT_TYPES runtime mapping as `status: stale` — the mention service then stops routing chat.mention events to it. Cody was installed under agentName=cloud-codex (which isn't in AGENT_TYPES) and went stale within ~5 minutes of install. Reinstalled under agentName=codex (which IS mapped to runtime:'codex' in AGENT_TYPES); mention routing works and codex CLI replies land in the pod. Wire that as the default in values-dev so subsequent helm-upgrades keep her on the right registry name. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The cleanup sweep that runs during reprovision marks any AgentInstallation whose agentName has no AGENT_TYPES runtime mapping as `status: stale`. The mention service then stops routing chat.mention events to it.
Cody was originally installed under `agentName=cloud-codex` (not in AGENT_TYPES) and went stale within ~5 minutes — `@cody` mentions stopped landing. Reinstalled under `agentName=codex` (which IS mapped to `runtime: 'codex'` in AGENT_TYPES); routing now works and codex CLI replies land in the pod ("4" reply to "2+2" verified).
Wire that as the default in values-dev so subsequent helm-upgrades keep her on the right registry name.
Test plan
🤖 Generated with Claude Code