Skip to content

feat: add auditable multi-agent lifecycle monitoring - #163

Open
lchojnowski wants to merge 1 commit into
graykode:mainfrom
lchojnowski:feat/auditable-multi-agent-lifecycle
Open

feat: add auditable multi-agent lifecycle monitoring#163
lchojnowski wants to merge 1 commit into
graykode:mainfrom
lchojnowski:feat/auditable-multi-agent-lifecycle

Conversation

@lchojnowski

Copy link
Copy Markdown

Summary

  • Add Grok and Kimi Code collectors, and harden Claude and OpenCode lifecycle correlation.
  • Add content-free native Codex plugin setup, uninstall, audit, and exact process-exit correlation without wrapping the native codex command.
  • Require exact process-incarnation ownership for destructive actions and terminal jumps, with fail-closed status evidence.
  • Add responsive monitoring UI and MCP behavior, deterministic demo snapshots, refreshed documentation, and regenerated theme assets.
  • Prepare the release-sized change as abtop 0.6.0 and remove the obsolete Chinese localization and configuration surface.

Safety and compatibility

Collectors remain local and read-only except for the explicit Claude and Codex setup commands and the Codex helper private bounded lifecycle state. Codex hook ingest does not persist prompts, tool input or output, commands, environment data, credentials, or arbitrary provider text.

Codex setup supports the audited native codex-cli 0.146.0 contract on macOS and Linux. It never aliases, wraps, replaces, or proxies native Codex. Because Codex does not expose thread, PID, and generation-bound attestation of the effective live hook engine, live Codex Thinking, Executing, Waiting, and Idle candidates deliberately remain non-actionable Unknown / Unavailable; only an exact supported Live-to-Gone process transition can produce short-lived heuristic Done.

Testing

  • cargo fmt --all -- --check
  • cargo clippy --all-targets -- -D warnings
  • cargo test --all-targets — 589 unit tests and 9 compatibility integration tests
  • Codex timeout and process-group tests repeated 20 consecutive times
  • cargo build --release
  • cargo check --target x86_64-unknown-linux-gnu
  • cargo check --target x86_64-pc-windows-gnu
  • cargo publish --dry-run --allow-dirty
  • abtop --version, abtop --demo --once, and abtop --demo --json smoke checks
  • VHS tape validation, regenerated v0.6.0 hero and theme assets, shell syntax validation, and git diff --check

Coordination

This branch is based on upstream main at 148f64d. It overlaps src/collector/codex.rs with #154 and #161 but does not claim to close #153 or #160. In particular, it intentionally does not treat rollout activity as proof of live Codex status; unattested live lifecycle remains fail-closed, and freeform Code Mode input is not exposed through display or snapshot fields.

@lchojnowski

Copy link
Copy Markdown
Author

A consolidated draft successor is now available at #166. It includes this lifecycle branch, #164, and the subsequent Codex lifecycle, Herdr, CodexBar, privacy, and reliability work. I’m leaving this PR open until the maintainer decides how to review or replace the earlier branches.

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.

Windows: resumed Codex CLI sessions from previous dates may not be detected

1 participant