Skip to content

fix(cli): sandbox-aware broker diagnostics + doctor --fix - #23

Merged
willio merged 1 commit into
mainfrom
fix/desktop-sandbox-diagnostics
Sep 1, 2026
Merged

willio merged 1 commit into
mainfrom
fix/desktop-sandbox-diagnostics

Conversation

@willio

@willio willio commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Desktop-Codex sandbox runs of broker commands failed confusingly (fetch failed → 'broker down', bare EPERM on the daemon log, rejected --fix flag). Status now reports probe-blocked-vs-down distinctly with the runtime facts, ensureBroker errors carry escalation guidance, doctor accepts explicit --fix, and the skill documents the sandbox behavior for desktop agents.

Running broker lifecycle commands from sandboxed agents (Codex desktop)
produced three confusing failures: status probed loopback and reported
the broker down on `fetch failed`, broker start died with a bare EPERM
writing its log, and `c2c doctor --fix` was rejected because repair is
the implicit default.

- doctor accepts an explicit --fix alongside --no-fix.
- broker status distinguishes "runtime file exists but probe failed"
  (sandbox suspicion, exit 1, connector URL from runtime) from actually
  not running.
- ensureBroker wraps log-open failures with actionable escalation
  guidance instead of a bare EPERM.
- SKILL.md documents the sandbox behavior for desktop agents.
@willio
willio merged commit 164e690 into main Sep 1, 2026
1 check passed
@willio
willio deleted the fix/desktop-sandbox-diagnostics branch September 1, 2026 06:14
willio added a commit that referenced this pull request Sep 1, 2026
fix(cli): sandbox-aware broker diagnostics + doctor --fix
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.

1 participant