Feature request: surface Git and GitHub lifecycle events as structured chat messages

What feature would you like to see?

Codex should emit Git and GitHub lifecycle actions into the active chat as structured, first-class events, not only as side effects or out-of-band UI state.

Examples:

• commit created
• branch created or switched
• push completed
• pull request created or updated
• pull request merged or closed
• merge conflicts detected or resolved
• review requested or received
• revert, cherry-pick, or rebase completed
• issue linked or closed by a pull request

Why this matters

Right now these actions often happen outside the conversational context. That makes it harder for Codex to reason over what already happened, continue from the latest repository state, and refer back to prior Git or GitHub changes without the user re-explaining them.

If these events appeared in the thread as structured messages, Codex could:

• use them as context for later turns
• reference commit or pull request state reliably
• avoid duplicate operations
• produce better follow-up actions after a commit or pull request
• improve auditability and reproducibility

Proposed behavior

When Codex performs or observes a Git or GitHub action, append a compact chat event such as:

• Commit created: abc123 - fix login race
• Pull request created: #456
• Pull request merged: #456
• Branch switched: feature/auth-cleanup

These should be machine-readable to the agent but human-readable in the UI.

Privacy and safety

These events should avoid leaking personal information or local environment details by default:

• redact or omit local folder paths
• avoid exposing emails, tokens, or secret values
• prefer repository-relative or GitHub-native identifiers
• allow a privacy-safe summary mode

Related

Issue #2765 discusses persistent session transcripts. This request is narrower and more immediate: show Git and GitHub actions as structured chat events during the live session so the agent can use them in-context.

Acceptance criteria

• Commit, branch, push, pull request, and merge actions appear in the chat as structured events.
• The agent can reference those events in later turns without the user restating them.
• Events are privacy-safe by default.
• UI messages are concise and link to the relevant commit or pull request when available.

Are you interested in implementing this feature?

No response