feature: Codex support — detection, settings, parsed events, token and cost accounting

Open
#942 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

enhancement nice to have
Feature Description

Codex support on the agent integration contract.

Proposed Solution

Same checklist as OpenCode support:

  • Detect an installed Codex and locate its settings
  • Patch it to use localhost:47600 and the Cortex CA; ask before editing, support revert
  • Traffic parsed into typed events, not merely proxied
  • Token counts and cost correct for its wire format
  • Metrics aggregate alongside other agents
  • A tool inventory, or state explicitly that tool pruning is unsupported
  • Setup documented; verified depth stated
Additional Context

Part of the Cortex v0.9.0 release, stretch scope — deferred past v0.9.0 as the agent least
used internally, so it proves the least about the release. Depends on the agent integration contract.

Dominant language
Go
Stars
13
Forks
40
Avg merge
12h 9m
Merged PRs (30d)
164

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rossoctl/cortex

All issues in rossoctl/cortex

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.