Skip to content

feat(sensor): capture rich Codex activity and provenance - #84

Draft
barisozbas wants to merge 1 commit into
pr/codex-tool-recordsfrom
pr/codex-rich-activity
Draft

feat(sensor): capture rich Codex activity and provenance#84
barisozbas wants to merge 1 commit into
pr/codex-tool-recordsfrom
pr/codex-rich-activity

Conversation

@barisozbas

@barisozbas barisozbas commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

What changed

The Codex parser now captures completed rich activity and session provenance in addition to classic function-call records.

  • Parses completed command executions, file changes, and MCP calls.
  • Reconciles duplicate classic and rich records by call ID or exact signature within the same action boundary.
  • Captures multi-agent lifecycle events and legacy agent-activity messages.
  • Retains bounded session lineage, source, branch, agent path, nickname, depth, and role metadata.
  • Preserves direct agent-role metadata ahead of nested fallback values.

Why

Current Codex sessions emit higher-level activity records that contain better completion status and provenance than classic wrappers. Capturing both without reconciliation would double-count activity; ignoring the rich records would lose important context.

Validation

  • pytest -q Sensor/tests
  • ruff check Sensor/adr_sensor/parsers/codex_parser.py Sensor/tests/test_parsers.py

Stack

Builds on #83.

Summary:
Intent:
- Preserve completed command, file, MCP, and multi-agent activity from current Codex events.
- Retain bounded session lineage and agent context.

Changes:
- Parse rich activity records and reconcile them with classic tool records only within safe boundaries.
- Capture agent lifecycle events, session provenance, lineage, and direct role metadata.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant