You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,12 @@
1
1
# Changelog
2
2
3
+
## v1.0.5
4
+
5
+
- Keep built-in background review jobs attached to the parent Codex session so plain `$cc:status` and `$cc:result` stay intuitive after nested rescue/review flows.
6
+
- Make `$cc:status --all` show the full job history for the current repository workspace instead of staying session-scoped.
7
+
- Harden large-diff review and hook fingerprinting so oversized `git diff` output degrades cleanly instead of failing with `ENOBUFS`.
8
+
- Clarify README guidance around review visibility, large diffs, and the difference between session-scoped status and repository-wide status.
9
+
3
10
## v1.0.4
4
11
5
12
- Make background built-in rescue/review completions steer users to `$cc:result <job-id>` instead of inlining raw child output.
Copy file name to clipboardExpand all lines: README.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,8 @@ Scope `auto` (the default) inspects `git status` and chooses between working-tre
114
114
115
115
In foreground, review returns the result directly. In background, the plugin uses a Codex built-in subagent, tracks the review as a job, and nudges you to open the result when it completes.
116
116
117
+
If the diff is too large to inline safely, the review prompt falls back to concise status/stat context and tells Claude to inspect the diff directly with read-only `git diff` commands instead of failing the run.
118
+
117
119
### `$cc:adversarial-review`
118
120
119
121
Same as `$cc:review`, but steers Claude to challenge the implementation — tradeoffs, alternative approaches, hidden assumptions.
@@ -163,10 +165,12 @@ Background rescue runs through a built-in Codex subagent. When the child finishe
163
165
```text
164
166
$cc:status # list active and recent jobs
165
167
$cc:status task-abc123 # detailed status for one job
166
-
$cc:status --all # include older jobs
168
+
$cc:status --all # show all tracked jobs in this repository workspace
167
169
$cc:status --wait task-abc123 # block until job completes
168
170
```
169
171
172
+
By default, `$cc:status` shows jobs owned by the current Codex session. Use `--all` when you want the wider repository view across older or sibling sessions in the same workspace.
173
+
170
174
### `$cc:result`
171
175
172
176
```text
@@ -205,7 +209,7 @@ All review and rescue commands support `--background`. Background jobs are track
205
209
3.**Completion nudges** — when a background built-in flow finishes, the plugin tries to nudge the parent thread with the right `$cc:result <job-id>`. If that nudge cannot surface cleanly, unread-result hooks are the backstop.
206
210
The nudge is intentionally just a pointer. The actual stored result still opens through `$cc:result`.
207
211
4.**Unread-result fallback** — when you submit your next prompt after a finished unread job, Codex can remind you that a result is waiting and point you to `$cc:status` / `$cc:result`.
208
-
5.**Session ownership** — jobs are scoped to the Codex session that created them. Nested sessions do not steal ownership of parent jobs.
212
+
5.**Session ownership** — jobs stay attached to the user-facing parent Codex session even when a built-in rescue/review child does the actual work, so plain `$cc:status` still shows the job you just launched.
209
213
6.**Cleanup on exit** — when your Codex session ends, any still-running detached jobs are terminated via PID identity validation, and stale reserved job markers are cleaned up over time.
210
214
211
215
**Typical background flow:**
@@ -317,6 +321,18 @@ $cc:result
317
321
```
318
322
The built-in notify path is best-effort. The tracked job store and unread hook remain the reliable fallback.
319
323
324
+
If you think the job may belong to an older session in the same repository, use:
325
+
```text
326
+
$cc:status --all
327
+
```
328
+
329
+
**Large review diff caused a failure or was omitted**
330
+
That is expected on very large diffs. The plugin now degrades to a compact review context and points Claude toward read-only `git diff` commands instead of trying to inline everything. If you want the full picture, run a narrower review such as:
331
+
```text
332
+
$cc:review --base main
333
+
$cc:review --scope working-tree
334
+
```
335
+
320
336
**Review gate draining tokens**
321
337
Disable it: `$cc:setup --disable-review-gate`. The gate fires on every Ctrl+C, which adds up.
@@ -308,7 +398,7 @@ function collectBranchContext(cwd, baseRef) {
308
398
formatSection(
309
399
"Branch Diff",
310
400
inlineDiff
311
-
? diff
401
+
? diff.text
312
402
: `Large diff omitted. Inspect the branch diff directly with read-only git commands such as \`git diff --no-ext-diff --submodule=diff ${commitRange}\`.`
- If that helper returns a non-empty `jobId`, pass it into the companion command as an internal `--job-id <reserved-job-id>` routing flag.
61
+
- Add an internal `--owner-session-id <parent-session-id>` routing flag when spawning the built-in child so the tracked review job stays visible in the parent Codex session's plain `$cc:status`.
61
62
- If the built-in review is running in background, the parent should first capture its own thread id by running:
0 commit comments