DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to monitor live Codex activity into a local record file with Numbat

Install a monitor-only Codex hook that writes events and findings to an NDJSON file.

Credentials. The live record file captures agent activity from a real user session, so restrict file permissions and review who can read it.

Who it is forA platform operator who wants continuous visibility into a Codex user's activity on a shared workstation.

The problemPast-session scans show history only after the fact, and operators need to see activity as it happens.

The outcomeLive Codex events, findings, and indicators written to ~/.numbat/records.ndjson, with hooks running in monitor-only mode.

What you need first

  • A macOS, Linux, or Windows machine with a terminal
  • The numbat binary, from a release download or Go 1.26.9 or newer
  • At least one supported agent installed, such as Codex or Claude Code
  • Permission to read the agent's local session files and, for live capture, to change its hook configuration

Steps

  1. Install Numbat, then run numbat hook install --agent codex --emit all.
  2. Run numbat hook status --agent codex to confirm the configuration is in place.
  3. Open /hooks in the Codex CLI, or Settings > Hooks in the Codex app, and review and trust the hook definition.
  4. Run a short Codex task and check that new lines appear in ~/.numbat/records.ndjson.
  5. After each Numbat upgrade, rerun numbat hook install --agent codex --emit all with the same options and review trust again.

Prompt for your agent

Use the repo perplexityai/numbat. Run `numbat hook install --agent codex --emit all` and then `numbat hook status --agent codex` on <target-machine>. Report the status output and the record_type values seen in ~/.numbat/records.ndjson after one short Codex task. Verify that the hook status output reports the Codex hook as installed, and remember that status checks configuration only, not delivery.

Caveat. Hook status verifies configuration only, not execution or delivery, so confirm that new records actually appear in the output file.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page