codex-monitor_skill

This skill helps you query and monitor OpenAI Codex sessions locally by wrapping Swift CLI tools for quick listing, viewing, and watching.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill codex-monitor

  • _meta.json280 B
  • codex_monitor.py1.1 KB
  • SKILL.md1.6 KB

Overview

This skill provides command-line helpers to browse and monitor OpenAI Codex session logs stored on a local machine. It wraps a small Swift project to list, show, and watch session activity, exposing text and JSON outputs. Use it to quickly inspect historical sessions or run a live monitor in the menu bar.

How this skill works

The skill calls Swift executables from the local project at ~/Developer/CodexMonitor, using the CLI and app targets. Commands run via the Python wrapper invoke the Swift CLI (swift run CodexMonitor-CLI ...) or launch the menu bar monitor (swift run CodexMonitor-App). Extra arguments are passed through to the underlying CLI so behavior can evolve with the Swift project.

When to use it

  • Inspect sessions for a specific day, month, or year to audit activity.
  • Show the full content of a single session or specific message ranges.
  • Export session data as JSON for analysis or backups.
  • Watch live updates for all sessions or a single session during active work.
  • Launch the menu bar monitor for continuous, low-friction observability.

Best practices

  • Build the Swift project once (swift build) if swift run is slow during iterative use.
  • Use JSON output (--json) when piping results into tools, scripts, or analytics pipelines.
  • Specify ranges when showing long sessions to limit output and focus on relevant messages.
  • Run watch only for specific sessions when monitoring a single thread to reduce noise.
  • Keep the project at ~/Developer/CodexMonitor so the wrapper can find and run the executables.

Example use cases

  • List all sessions on 2026/01/08 to review work performed that day.
  • Show session ABC123 and display messages 1...3 and 26...28 to extract key interactions.
  • Run list --json for a month to import session metadata into a reporting tool.
  • Watch --session ABC123 while a colleague reproduces an issue to observe live messages.
  • Launch the monitor in the menu bar to get passive updates on new or changing sessions.

FAQ

Build once with swift build and run the built executable to avoid repeated compilation.

Can I get machine-readable output?

Yes. Use the --json flag on list and show commands to produce JSON for downstream processing.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational