Conversation
added 2 commits
September 22, 2026 11:35
Name the unsaved desktop state at risk before requiring confirmation so operators can avoid losing drafts or approvals. Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Keep the generated command reference aligned with the expanded restart warning. Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
✅ Deterministic PR hygiene checks passed. |
Contributor
⏳ DRAFT
What to do
Review readiness checklist
2/4 boxes ticked. This PR stays in draft until every box above is ticked. |
Owner
리뷰 · 우선순위 32 / 80이 PR은 라인 - 메인테이너의 판단이 필요한 지점 이 PR을 #4761의 “경고만 먼저” 조각으로 받고 이슈는 열어둘지, 아니면 파괴적 재시작을 줄이는 후속 작업이 같이 있어야 merge할지. 또한 draft이고 readiness checklist가 0/4라서, 지금 시점에서 리뷰 완료 표시를 할지 작성자 체크를 기다릴지. 너의 추천 경고 문구와 문서·테스트 정합은 좋고 범위도 작아서, 주석만 에러 문구와 맞춘 뒤 draft checklist를 채우면 merge해도 된다. #4761은 부분 해결로 두고 후속 이슈/PR로 “앱 서버만 재시작 / 불필요한 데스크톱 재시작 생략”을 따로 추적하는 쪽이 맞다. types.ts/config.ts 분할이나 preview deploy와는 무관하다. 이 댓글은 grok-bot이 작성했습니다 |
added 2 commits
September 22, 2026 17:36
Keep destructive desktop state loss visible for habitual --yes users without changing the JSON contract. Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
…saved-state-warning
Contributor
Author
|
Verification update for
The correct Grok findings were addressed. I left the local-green and ready-for-review boxes open rather than claiming the baseline timeout is green. |
3 tasks
lidge-jun
added a commit
that referenced
this pull request
Sep 23, 2026
…robe ceilings, hidden autostart, mise updates, Linux packaged E2E (#5682) * fix(desktop): ad-hoc sign the bun sidecar on macOS after prepare Bun's linker-signed standalone output is killed by macOS page validation (CODESIGNING "Invalid Page"), so the bundled ocx sidecar never ran and the desktop app stayed in "resolving". prepare-sidecar now reseals the copied sidecar with an ad-hoc signature, but only when a macOS host prepares a bun-darwin-* target, through the absolute /usr/bin/codesign; a failed or unlaunchable codesign stops preparation. The decision and the spawn boundary live in desktop/scripts/sidecar-signing.ts so they are tested without running codesign. Carries #5559. Co-authored-by: agentHits <140916359+agentHits@users.noreply.github.com> * fix(cli): warn about state loss before and after codex-restart ocx system codex-restart fully quits and relaunches the Codex desktop app, which can discard unsaved composer drafts, model-picker selections, and pending approval prompts. The missing --yes error, the confirmed human output, the capability metadata, the generated skill surface, and the runtime structure doc now name that concrete loss. The restart request, the --yes gate, and the JSON payload are unchanged. Carries #5488. Refs #4761 (the warning slice only; restart scope is unchanged). Co-authored-by: Yu Zhang <34849476+AaronZ345@users.noreply.github.com> * feat(server): OCX_PROBE_TIMEOUT_MS raises the liveness probe ceilings On hosts where a content filter or EDR network extension adds a fixed cost to every loopback connect, the shipped 750 ms probe expires before a healthy proxy answers and every CLI liveness consumer reports it down. OCX_PROBE_TIMEOUT_MS (whole milliseconds, 1 to 30000) raises the ceilings on such hosts. The override only raises: the 750 ms shared default and the 1500 ms stop/start ownership budgets keep their floors, so a small value can never shorten the budgets that prevent a duplicate proxy. Values above 30 s are ignored so the single-shot stop deadline stays bounded (at most about 90 s). The wiring tests read the constants in child processes, so no other test file can observe an override. The CLI reference in all eight locales and structure/ops/service-and-sidecars.md describe the setting. Carries #5409 with the floor and ceiling fixed during the carry. Co-authored-by: Kinso <5144108+kinsolee@users.noreply.github.com> * perf(desktop): keep a hidden login launch on the startup surface A login launch that starts hidden behind a usable tray no longer loads the full dashboard after Ready. It keeps the small bundled startup page, and the tray's Open Dashboard, a second ordinary launch, and the shell's open command all go through startup::open_dashboard, which performs the run's single navigation before showing the window. Manual launches and visible no-tray launches keep eager navigation. Two gaps in the original change are closed here. An open that arrives during startup is recorded before progress is read, and finish reads it after recording Ready, so whichever side runs second navigates. A WebView that refuses the navigation script gives the one-shot claim back, so the next open retries. Both reset with each run. Rust tests cover the first, repeated, refused, and in-flight opens; the desktop guide in all eight locales, structure/desktop-shell.md, and ADR-5494 describe the behavior. Carries #5498. Refs #5493 (hidden-autostart deferral). Co-authored-by: ingwannu <186453546+Ingwannu@users.noreply.github.com> * fix(update): respect mise-owned installations An opencodex package installed by mise was updated by npm self-update inside mise's tree, behind mise's back. Install detection now recognises a mise install from the adjacent .mise.backend.toml (tool alias plus the canonical npm:@bitkyc08/opencodex backend) on both the lexical and the resolved package path, reports installer "mise", and refuses mutation with "mise upgrade <alias>" before any proxy stop, package write, or worker creation: in the Node launcher, ocx update, the dashboard update check and worker, and the sidebar badge. Unreadable or contradictory metadata on either path fails closed without inventing a tool name. The dashboard hides the command chip when there is no verified command, and the lifecycle reference in all eight locales and all ten GUI catalogs describe the behaviour. Changes made while carrying it onto current dev: - ported onto the update ownership transaction and the package-tree restart guard that landed after the PR's base; - two verified owners whose tool roots differ only by a symlinked ancestor (macOS /var -> /private/var) are compared by canonical directory, so a real install behind a symlinked data directory is not reported as contradictory; - the launcher refusal test now runs on Windows too (junction plus npm.cmd), proves the fake npm never runs, and covers contradictory metadata; - the structure note moved to structure/ops/service-and-sidecars.md to keep structure/runtime.md within its line budget. Carries #5316. Co-authored-by: Gary Sassano <10464497+garysassano@users.noreply.github.com> * test(desktop): add the Linux packaged-shell E2E driver desktop/scripts/linux-packaged-e2e.ts boots the real AppImage and deb payloads under a private Xvfb, Openbox and D-Bus session with fresh HOME, XDG, CODEX_HOME and OPENCODEX_HOME roots and a reserved loopback port, then requires a visible OpenCodex window, the bundled sidecar's matching /healthz identity, port and version, and a clean drain after the only window closes. Its report records readiness time and process-tree RSS as evidence, not as budgets. Release asset collection accepts an explicit isolated bundle root, and the AppImage patchelf wrapper follows the active CARGO_TARGET_DIR so each Linux format can build in its own Cargo target. Changes made while carrying it: - the window is closed through the window manager (wmctrl -i -c, the EWMH close request a close button sends) instead of xdotool windowclose, which destroys the X window and can end the app without Tauri's close/drain path; the app must then exit on its own with code 0 and no signal, which is asserted and recorded in the report; - verify-linux-sidecar.sh takes the staged AppImage directory as an optional argument, keeping the local default path; - workflow wiring and the tests that read workflow files are in the following commit. Carries #5502 (driver, scripts, docs). Refs #5493. Co-authored-by: ingwannu <186453546+Ingwannu@users.noreply.github.com> * ci(desktop): run the Linux packaged-shell E2E and isolate Linux release formats CI: a new desktop scope (desktop/, gui/, src/, the standalone build scripts, package.json, bun.lock and ci.yml itself) selects desktop-shell alongside the native scope. When selected, the job builds the dashboard and the bundled sidecar, builds the AppImage and the deb in separate Cargo targets with updater artifacts disabled, stages them read-only, and runs the packaged-shell E2E under dbus-run-session, xvfb-run and Openbox. The report is uploaded with a SHA-pinned upload-artifact. The workflow keeps contents: read, uses no secrets, and installs no package into the runner. The aggregate gate derives the widened desktop-shell expectation the same way the job does. Release: on Linux, each format is built in its own CARGO_TARGET_DIR, staged read-only, and collected from that staged root; the existing job-scoped signing inputs are unchanged. Changes made while carrying it: - current dev's scope step no longer handles a privacy output; only the desktop output was added to it and to the aggregate; - the Linux sidecar verifier moved after the isolated AppImage build and staging, and verifies the staged AppImage directory; before, it would have run before any Linux bundle existed in the default target; - wmctrl is installed for the window-manager close request; - the scope and aggregate tests that landed on dev after the PR's base now model the desktop output, and a new test file carries the CI wiring assertions. Carries #5502 (workflow part). Refs #5493. Co-authored-by: ingwannu <186453546+Ingwannu@users.noreply.github.com> --------- Co-authored-by: agentHits <140916359+agentHits@users.noreply.github.com> Co-authored-by: Yu Zhang <34849476+AaronZ345@users.noreply.github.com> Co-authored-by: Kinso <5144108+kinsolee@users.noreply.github.com> Co-authored-by: ingwannu <186453546+Ingwannu@users.noreply.github.com> Co-authored-by: Gary Sassano <10464497+garysassano@users.noreply.github.com>
Owner
2 tasks
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
ocx system codex-restartis missing--yesPartially addresses #4761. This PR only improves the destructive-restart warning; it does not close the broader app-server-only restart work.
Verification
bun test tests/cli/cli-headless-parity.test.ts tests/cli/cli-capabilities.test.ts tests/ci-workflows/skill-ocx.test.ts(112 pass)bun test tests/responses/responses-compaction-routing.test.ts(124 pass)bun test tests/usage/request-history-index.test.ts tests/codex-integration/codex-shim.test.ts(100 pass, 23 skip, 1 pre-existing timeout)upstream/devworktree (7.4s against a 5s limit)bun run typecheckgit diff --checkChecklist
Review readiness checklist
This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:
All CI tests are green on my local testing.
I pushed my PR to the latest dev commit.
I resolved all correct Codex and CodeRabbit findings.
My PR is ready for review.