Skip to content

toolpath-codex#25

Merged
benbaarber merged 2 commits into
mainfrom
ben/codex
Apr 21, 2026
Merged

toolpath-codex#25
benbaarber merged 2 commits into
mainfrom
ben/codex

Conversation

@benbaarber
Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions
Copy link
Copy Markdown

🔍 Preview deployed: https://d4ec0fd6.toolpath.pages.dev

Copy link
Copy Markdown
Contributor

@akesling akesling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

include_thinking: bool,
},
/// Derive from Codex CLI rollout files
Codex {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any way to ask which "project" a Codex session is associated with so we can have project-filtered listing of sessions like with our other providers?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude, Gemini, and Pi all store conversation files keyed by project. Those providers need a --project to know which directory to scan:

  • Claude: ~/.claude/projects//*.jsonl
  • Gemini: ~/.gemini/tmp//chats/...
  • Pi: sessions are resolved per-project cwd

Codex doesn't. Per the CLAUDE.md note and toolpath-codex/src/io.rs:

▎ Codex CLI rollout files from ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl. Sessions are date-bucketed (not project-keyed).

So yes we can, but we would add it as a post-hoc filter

@benbaarber benbaarber merged commit ae2d14e into main Apr 21, 2026
2 checks passed
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.

2 participants