Skip to content

Codex File Inspector 0.2.5

Choose a tag to compare

View all tags
@Bathur Bathur released this 10 Sep 12:13
· 3 commits to main since this release
v0.2.5
290dcd4

Adds optional local failure diagnostics so failed tool calls can be investigated after an agent finishes its task.

What's new

  • Enable file logging with the --diagnostics startup argument; it is disabled by default.
  • Record final error and partial results with bound arguments, existing error/warning information, and already-caught exception details. Successful calls and failures outside the standard tool-result boundary are not recorded.
  • Write per-process JSONL files under the application's logs directory. A bounded background queue keeps tool results from waiting for disk writes. Logging is best effort and records may be dropped.
  • Bound records at 256 KiB with explicit truncation, rotate files at 8 MiB, and clean old closed diagnostic files toward a 128 MiB directory target. The target is not a strict cross-process quota.
  • Update README, DESIGN, and repository guidance for the new option.

The four tool APIs, model-visible results, and read-only inspection behavior are unchanged. Runtime dependencies remain pinned to the existing versions.

Enable diagnostics

Add the following to the existing [mcp_servers.codex_file_inspector] table, alongside command and before any per-tool tables:

args = ["--diagnostics"]

If an args array already exists, add the argument there. Restart Codex to apply it. Remove the argument and restart to disable future logging; existing files remain.

Logs include unredacted paths, queries, and exception details. Review their contents before sharing them. File logging does not collect read/search result bodies or guarantee complete reproduction evidence.

Distribution

Use the complete Windows x64 archive with the .NET 10 x64 runtime. Keep its assemblies, runtimes, bundled ripgrep, and license files together.

  • CodexFileInspector-0.2.5-win-x64.zip
  • CodexFileInspector-0.2.5-source.zip
  • SHA256SUMS for those two archives

The matching exported public source passed 201/201 Release tests. Both the published executable and the executable extracted from the Windows archive passed 8/8 STDIO tests. All 144 entries across the 90-file source archive and 54-file binary archive were rehashed against verified inputs, and the runtime license inventory matched all 32 packages. These are local verification results, not broad cross-machine certification or an independent security audit. Binaries are unsigned.

Assets 5
Loading