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
- Gemini emits plans and available-command updates from the ACP stream, but VaultAI currently does **not** surface Gemini `user_input` as a supported adapter capability.
30
30
- Codex and Gemini support `session/close` in the client/runtime handle path; Claude session removal is currently local-state cleanup only.
31
31
- The current Claude vendor also pulls `@anthropic-ai/claude-agent-sdk``0.2.83`.
32
+
- Codex now tracks `zed-industries/codex-acp``0.11.1` at upstream commit `c3e95ca414f57a3db8a5bf5714719a102b98e0b5`, with a small local delta to preserve VaultAI review, diff, mode and user-input behavior.
32
33
33
34
---
34
35
@@ -219,7 +220,16 @@ Supported methods:
219
220
220
221
Auth detection is not based only on persisted `auth_method`. VaultAI also considers environment variables and available secrets when computing the effective ready/authenticated state.
221
222
222
-
VaultAI carries a local patch on `vendor/codex-acp``v0.10.0` so `SessionModeState` / `Approval Preset` survives cases where upstream Codex expands a `workspace-write` sandbox with extra writable roots. Without this patch, Codex can stop emitting `modes` even though the session still has a valid approval+sandbox configuration.
223
+
VaultAI still carries a bounded local delta on `vendor/codex-acp``v0.11.1`.
224
+
225
+
That delta is intentional and currently lives mainly in `src/thread.rs` and `src/codex_agent.rs` to preserve product behavior that the desktop app already depends on:
226
+
227
+
- VaultAI-specific metadata for status, plan, diff hunks and `user_input_request`
228
+
- reconstruction of `unified_diff` into `old_text` / `new_text` for inline review and the edited-files panel
229
+
- resilient `modes` / approval-preset behavior when Codex expands writable roots under `workspace-write`
230
+
- actor shutdown semantics that do not keep internal message channels alive after external senders are dropped
231
+
232
+
In other words, Codex is now aligned with upstream `0.11.1`, but it is not a raw upstream checkout. The remaining delta is product-facing, not incidental.
223
233
224
234
### Gemini
225
235
@@ -406,7 +416,7 @@ vendor/
406
416
│ ├── dist/index.js
407
417
│ ├── node_modules/
408
418
│ └── package.json
409
-
└── codex-acp/ # codex-acp v0.10.0 + local VaultAI patch
- synced against upstream commit `c3e95ca414f57a3db8a5bf5714719a102b98e0b5`
41
+
- local VaultAI delta remains intentionally bounded and lives mainly in:
42
+
-`vendor/codex-acp/src/thread.rs`
43
+
-`vendor/codex-acp/src/codex_agent.rs`
44
+
-`Claude-agent-acp-upstream/`
45
+
- vendored snapshot remains based on `@zed-industries/claude-agent-acp``0.23.1`
46
+
47
+
## Current Codex Delta
48
+
49
+
The Codex vendor is no longer a raw upstream checkout.
50
+
51
+
The remaining VaultAI-specific delta exists to preserve desktop product behavior:
52
+
53
+
- ACP metadata that VaultAI consumes for status, plan updates, diffs and `user_input_request`
54
+
- reconstruction of `unified_diff` into `old_text`, `new_text` and hunk metadata for inline review and edited-files flows
55
+
- mode and approval-preset stability when Codex expands writable roots under `workspace-write`
56
+
- actor lifecycle behavior that does not keep the internal message channel alive after external senders disappear
57
+
58
+
When updating Codex again, treat `c3e95ca` as the comparison base and review those files intentionally instead of replacing the whole directory blindly.
59
+
36
60
## Updating Vendored Runtimes
37
61
38
62
When updating a vendored dependency:
39
63
40
64
1. Refresh the upstream snapshot to the exact release or commit you intend to ship.
41
65
2. Keep `dist/` aligned with the vendored Claude source snapshot.
42
-
3. Remove any local byproducts before committing.
43
-
4. Re-run the relevant validation:
44
-
-`cargo test -q`
45
-
-`cd apps/desktop && npm run lint && npm test`
66
+
3. Re-apply only the bounded local product delta that VaultAI still needs.
67
+
4. Remove any local byproducts before committing.
68
+
5. Re-run the relevant validation:
69
+
-`cd vendor/codex-acp && cargo test -q`
70
+
-`VAULTAI_CODEX_ACP_BUNDLE_BIN=/Users/jfg/Documents/DEVELOPMENT/VaultAI/vendor/codex-acp/target/debug/codex-acp cargo test -p vault-ai-desktop`
0 commit comments