AGENTS.md: no dev-exec.sh for `cargo` commands
What changed, and why it matters
This commit only updates developer-facing documentation (AGENTS.md). It tells contributors they can run Rust's cargo commands directly on their computer instead of inside the project's Docker/development wrapper script. No firmware code, build scripts, or security behavior changed.
No security action needed. Review as normal documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies AGENTS.md instructions for AI agents/developers. It removes the requirement to use ./scripts/dev_exec.sh for cargo test, cargo check, and cargo clippy, and updates examples accordingly. The change is purely procedural documentation; no source files, toolchain, compiler flags, or runtime code were altered.
Changed components
AGENTS.mdInspect captured patch +9 / −5
diff --git a/AGENTS.md b/AGENTS.md
index 0d7bdbf..a0402ba 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -27,6 +27,9 @@ for the current scope.
Run regular Unix commands such as `git`, `rg`, `grep`, `ls`, `find`, `sed`, and `cat` directly on
the host.
+Cargo commands for the Rust workspace, such as `cargo test`, `cargo check`, and `cargo clippy`, may
+also be run directly on the host by passing `--manifest-path src/rust/Cargo.toml`.
+
Use `./scripts/dev_exec.sh <command>` only for project-specific commands that depend on the project
toolchain or compiler environment.
@@ -34,9 +37,8 @@ In practice, the repository `make` targets in this file are project-specific too
When running from the host, invoke them via `./scripts/dev_exec.sh make <target>`.
Do not wrap `./scripts/dev_exec.sh` itself in `bash -lc`. Prefer changing CWD
-with CLI args like `tar -C <PATH>` or `cargo build --manifest-path <PATH>`. If
-a command genuinely needs shell features such as pipes, pass an explicit shell
-as the command, e.g. `./scripts/dev_exec.sh bash -lc 'cat versions.json | jq'`.
+with CLI args like `tar -C <PATH>`. If a command genuinely needs shell features such as pipes, pass
+an explicit shell as the command, e.g. `./scripts/dev_exec.sh bash -lc 'cat versions.json | jq'`.
- `make firmware` / `make bootloader`: compile firmware or bootloader ELFs into `build/`.
- `make simulator`: build the Linux simulator under `build-build-noasan/bin/`.
@@ -45,9 +47,11 @@ as the command, e.g. `./scripts/dev_exec.sh bash -lc 'cat versions.json | jq'`.
- `make run-rust-clippy`: lint Rust code with the workspace configuration.
- When invoking the above `make` targets from the host, prefer
`./scripts/dev_exec.sh make <target>`.
-- Rust tests may also be run directly with `cargo test`:
+- Rust workspace commands may also be run directly with `cargo`, without `./scripts/dev_exec.sh`:
- From the repository root on the host, use
- `./scripts/dev_exec.sh cargo test --manifest-path src/rust/Cargo.toml [ -p <crate> ] --all-features -- --test-threads 1`.
+ `cargo test --manifest-path src/rust/Cargo.toml [ -p <crate> ] --all-features -- --test-threads 1`.
+ - For checks, use
+ `cargo check --manifest-path src/rust/Cargo.toml [ -p <crate> ] --all-features`.
## Coding Style & Naming Conventions
`.clang-format` (Chromium base, 4-space indent, Linux braces) and `.clang-tidy` govern C/C++. Use
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.