Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3217e43e3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
* Refine settings and shell UI behavior * Fix manual model input behavior
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 44f1135303
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fba451deca
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 188bde4418
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const baseDirectory = resolve(options.baseDirectory); | ||
|
|
||
| function getWorkspacePath(sessionId: string): string { | ||
| assertValidWorkspaceSessionId(sessionId); |
There was a problem hiding this comment.
Accept legacy session IDs when deriving workspace paths
getWorkspacePath now hard-fails any ID outside /^ses_[a-z0-9]+$/, but the chat API still accepts any non-empty sessionId and prepareChatRequest persists it verbatim, so UUID/custom IDs that previously worked now fail later when workspace logic runs (chat start, session detail, delete/open workspace) and surface as 500s instead of a client error. This creates a regression for existing data and external clients; either validate/reject incompatible IDs at the API boundary before persisting, or make workspace derivation tolerant of pre-existing session IDs.
Useful? React with 👍 / 👎.
Summary
Tests