vibe-coding-master 0.3.10 → 0.3.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -4,8 +4,8 @@
4
4
  <meta charset="UTF-8" />
5
5
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6
6
  <title>VibeCodingMaster</title>
7
- <script type="module" crossorigin src="/assets/index-D-6FVz_K.js"></script>
8
- <link rel="stylesheet" crossorigin href="/assets/index-CR1EOe-w.css">
7
+ <script type="module" crossorigin src="/assets/index-C7Nb1xPJ.js"></script>
8
+ <link rel="stylesheet" crossorigin href="/assets/index-B13y-ZM8.css">
9
9
  </head>
10
10
  <body>
11
11
  <div id="root"></div>
@@ -453,7 +453,7 @@ status, decision, report path, and any failure or exception metadata.
453
453
  The Codex CLI provider uses the long-lived embedded terminal session, not
454
454
  `codex exec`, because VCM needs Codex `UserPromptSubmit` and `Stop` hook events
455
455
  and the user may continue discussing the review after the report is written.
456
- Current implementation shape for a fresh terminal:
456
+ Default local implementation shape for a fresh terminal:
457
457
 
458
458
  ```bash
459
459
  codex \
@@ -467,6 +467,24 @@ codex \
467
467
  --config model_reasoning_effort="<effort-selected-in-VCM-UI>"
468
468
  ```
469
469
 
470
+ When VCM runs inside a Dev Container with `VCM_SANDBOX=devcontainer`, the
471
+ container is the security boundary. VCM then starts Codex Reviewer without
472
+ Codex's nested filesystem sandbox to avoid Linux container `bwrap` and
473
+ `apply_patch` write failures:
474
+
475
+ ```bash
476
+ codex \
477
+ --cd <taskRepoRoot>/.ai/codex \
478
+ --dangerously-bypass-approvals-and-sandbox \
479
+ --dangerously-bypass-hook-trust \
480
+ --search \
481
+ --model <model-selected-in-VCM-UI> \
482
+ --config model_reasoning_effort="<effort-selected-in-VCM-UI>"
483
+ ```
484
+
485
+ Use this mode only when VCM, Codex, Claude Code, and the target repository all
486
+ run inside the same trusted container or VM boundary.
487
+
470
488
  VCM omits `--model` or `model_reasoning_effort` when the user selects
471
489
  `Default`, letting Codex CLI use its account or CLI default. `--search` enables
472
490
  Codex CLI's native web search tool for reviewer checks that need current
@@ -476,10 +494,11 @@ Starting from `.ai/codex` causes Codex to load `.ai/codex/AGENTS.md` through
476
494
  its normal `AGENTS.md` discovery path and `.ai/codex/.codex/hooks.json` through
477
495
  the Codex project hook path. VCM sends the gate prompt into this terminal,
478
496
  validates the report path, request id, and decision before marking a gate
479
- completed, then callbacks PM. `--ask-for-approval never` and the VCM-owned hook
480
- trust bypass prevent Codex from pausing at permission or hook trust prompts;
481
- execution failures are recorded as `failed` so the user can retry, skip, or
482
- override.
497
+ completed, then callbacks PM. In default local mode, `--ask-for-approval never`
498
+ and the VCM-owned hook trust bypass prevent Codex from pausing at permission or
499
+ hook trust prompts; in Dev Container mode, the Codex approval and sandbox bypass
500
+ does the same while relying on the container boundary. Execution failures are
501
+ recorded as `failed` so the user can retry, skip, or override.
483
502
 
484
503
  ## 10. UI Shape
485
504