feat: Add --check flag to mi6 status for hook verification
Resolved 💬 2 comments Opened Jan 11, 2026 by sslivkoff Closed Jan 11, 2026
Problem
mi6 status shows "ENABLED" based on whether hooks are configured in settings files, but does not verify hooks actually work. Users can have hooks configured but broken (e.g., mi6 not in PATH, permission issues).
Current behavior:
$ mi6 status
Framework Status Method
Claude Code ENABLED plugin
Gemini CLI ENABLED config hooks
User assumes everything works, but hooks may be silently failing.
Proposed Solution
Add --check flag that actually tests hook execution:
$ mi6 status --check
Framework Status Method Verified
Claude Code ENABLED plugin hooks responding
Gemini CLI ENABLED config hooks hooks responding
Codex CLI ENABLED config hooks hooks not responding (!)
Warning: Codex hooks are configured but not responding.
- Check that mi6 is in your PATH
- Run: which mi6
Implementation Approach
- For each enabled framework, invoke a lightweight test:
``bash``
mi6 ingest event --test --framework claude
- The --test flag would:
- Skip database write
- Return success/failure quickly
- Verify the command can be invoked
- Alternative: check if recent events exist from that framework
``sql``
SELECT COUNT(*) FROM events
WHERE framework = 'claude'
AND created_at > datetime('now', '-1 hour')
Scope
- New --check flag on mi6 status
- Lightweight verification (< 100ms per framework)
- Clear actionable output when verification fails
- Optional: --check could be default behavior (with --fast to skip)
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗