release: codexpro 0.30.0 user issue fixes - #87
Merged
Conversation
Ship multi-project settings that were stuck on main, harden invalid Windows HOME for bash children, raise the bash timeout cap, follow symlinked skill dirs, and document update/Agent/dual-tunnel FAQ answers. Co-authored-by: Cursor <cursoragent@cursor.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
This was referenced Aug 8, 2026
Closed
Use isSubpath instead of case-sensitive startsWith so symlink/junction-resolved skills keep user source and ~/ display paths on Windows CI. Co-authored-by: Cursor <cursoragent@cursor.com>
Classify discovered skills by their configured scan root and match ~/ display paths against both realpathed and caller-supplied home spellings so Windows junctions that preserve long path targets no longer become source "other" with absolute paths. Co-authored-by: rebel <rebel0789@users.noreply.github.com>
Add workspace-gated import_file with openai/fileParams, approved-host HTTPS downloads, streaming size limits, SHA-256/MIME checks, and smoke coverage for issue #82. Co-authored-by: Cursor <cursoragent@cursor.com>
Use native realpath, multi-spelling home candidates, and ancestor realpath matching so junction-resolved skill display paths keep the ~/ prefix when Windows expands 8.3 names differently from the caller-supplied home. Co-authored-by: rebel <rebel0789@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--project/--clear-projectsalready worked onmain, but npm0.29.0never published those commits. This release bumps to0.30.0and documents update + restart steps.=\npm-cacheinside workspaces #81: restricted bash env rejects relative junkHOMEvalues like=and prefers a usable absoluteUSERPROFILE/HOME, plus valid WindowsAPPDATA/LOCALAPPDATA.timeout_mshard cap rises from 180s to 10 minutes by default (max 15 minutes viaCODEXPRO_MAX_BASH_TIMEOUT_MS). Default per-command timeout stays 30s. No remote Codex bus.import_filefor ChatGPT Apps SDK attachments (openai/fileParams), with approved-host HTTPS downloads, redirect revalidation, streaming size limits, SHA-256/MIME checks.Test plan
npm run buildnpm run smoke(includesimport-smoke)npm run stress(prior commit)npm audit --audit-level=high(0 vulnerabilities after lockfile update)git diff --checknpm run release:publishso users cannpm install -g codexpro@latestCloses #81
Closes #82
Closes #83
Closes #64
Closes #85
Closes #86