Skip to content

fix: agentdiff status should verify Codex/Gemini enablement flags #21

@codeprakhar25

Description

@codeprakhar25

What

agentdiff status currently confirms the agentdiff hook marker is present in Codex/Gemini config files, but doesn't verify the required enablement flags:

  • Codex: features.codex_hooks = true
  • Gemini: tools.enableHooks = true

These flags can be disabled by the user or agent updates, causing silent capture failure while status reports "ok".

Why

An engineering team could think capture is running when it's actually broken. The marker check provides ~80% confidence; enablement flags bring it to ~95%.

How

In print_agent_hook_status() in status.rs, after confirming the marker is present for Codex/Gemini:

  • For Codex: parse TOML config and verify features.codex_hooks = true
  • For Gemini: parse JSON config and verify tools.enableHooks = true
  • Show a distinct warn if flag is missing or false, even if marker is present

Effort

~15 min. No dependencies.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions