codlogs is a read-only Codex session tool with two entry points:
- a global CLI for finding sessions and exporting one
.jsonlsession to Markdown or HTML - an Electrobun desktop browser for scanning sessions, filtering by folder, and exporting the selected session to
.mdor.html
Install it globally from this folder:
npm install -g d:\github\codlogsUse either codlogs or codlogs-sessions:
codlogs
codlogs d:\github\myDUDreamTool
codlogs /mnt/d/github/myDUDreamTool
codlogs --md C:\Users\tobitege\.codex\sessions\2026\03\06\session.jsonl
codlogs --html C:\Users\tobitege\.codex\sessions\2026\03\06\session.jsonl
codlogs --md C:\Users\tobitege\.codex\sessions\2026\03\06\session.jsonl --include-images --include-tool-resultsNotes:
- the folder argument is optional; if omitted, the current working directory is used
- if the folder is inside a git repo, the CLI matches sessions for the repo root by default
- use
--cwd-onlyto match only the folder tree you pass in - use
--codex-home PATHif your Codex data lives somewhere other than%CODEX_HOME%or~/.codex - use
--include-imageswith--mdor--htmlto write embedded images into a sibling.assetsfolder - use
--htmlto export a session as a self-contained HTML transcript - use
--include-tool-resultswith--mdor--htmlto include tool calls and tool outputs in the export - Windows drive paths, WSL
/mnt/<drive>/...paths, and WSL UNC paths are treated as aliases of the same repo
The desktop browser uses Electrobun.
Prerequisites:
- Bun
>=1.3.9 - Windows 11+ with WebView2 available for the embedded webview runtime
Run it locally:
bun install
bun run startFor live UI reload while editing:
bun run dev:hmrOther useful commands:
bun run build:web
bun run buildNotes:
bun run startis the easiest local launch path because it builds the web assets first- the first Electrobun run downloads its platform-specific core binaries
- the app defaults to the current folder tree on launch
