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: AGENTS.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,12 @@ In the `codex-rs` folder where the Rust code lives:
23
23
- When cutting a release, update the release and upstream baseline SHAs in `CHANGELOG.md`,
24
24
then rerun the generator.
25
25
26
+
## Releases (Codexel vs codex-rs)
27
+
28
+
- Codexel release tags that trigger the publishing workflows use `codexel-vX.Y.Z` (for example `codexel-v0.1.4`).
29
+
- The upstream `codex-rs` Rust release workflow uses `rust-vX.Y.Z` tags.
30
+
- A plain `vX.Y.Z` tag exists historically in this repo, but does not match those workflow triggers.
31
+
26
32
## Formatting, lint, tests
27
33
28
34
Run `just fmt` (in `codex-rs` directory) automatically after making Rust code changes; do not ask for approval to run it.
@@ -105,6 +111,12 @@ If you don’t have the tool:
105
111
- Prefer deep equals comparisons whenever possible. Perform `assert_eq!()` on entire objects, rather than individual fields.
106
112
- Avoid mutating process environment in tests; prefer passing environment-derived flags or dependencies from above.
107
113
114
+
### Spawning workspace binaries in tests (Cargo vs Buck2)
115
+
116
+
- Prefer `codex_utils_cargo_bin::cargo_bin("...")` over `assert_cmd::Command::cargo_bin(...)` or `escargot` when tests need to spawn first-party binaries.
117
+
- Under Buck2, `CARGO_BIN_EXE_*` may be project-relative (e.g. `buck-out/...`), which breaks if a test changes its working directory. `codex_utils_cargo_bin::cargo_bin` resolves to an absolute path first.
118
+
- When locating fixture files under Buck2, avoid `env!("CARGO_MANIFEST_DIR")` (Buck codegen sets it to `"."`). Prefer deriving paths from `codex_utils_cargo_bin::buck_project_root()` when needed.
119
+
108
120
### Integration tests (core)
109
121
110
122
- Prefer the utilities in `core_test_support::responses` when writing end-to-end Codex tests.
0 commit comments