b77fe8fefe
## Why Once the repo-local lint exists, `codex-rs` needs to follow the checked-in convention and CI needs to keep it from drifting. This commit applies the fallback `/*param*/` style consistently across existing positional literal call sites without changing those APIs. The longer-term preference is still to avoid APIs that require comments by choosing clearer parameter types and call shapes. This PR is intentionally the mechanical follow-through for the places where the existing signatures stay in place. After rebasing onto newer `main`, the rollout also had to cover newly introduced `tui_app_server` call sites. That made it clear the first cut of the CI job was too expensive for the common path: it was spending almost as much time installing `cargo-dylint` and re-testing the lint crate as a representative test job spends running product tests. The CI update keeps the full workspace enforcement but trims that extra overhead from ordinary `codex-rs` PRs. ## What changed - keep a dedicated `argument_comment_lint` job in `rust-ci` - mechanically annotate remaining opaque positional literals across `codex-rs` with exact `/*param*/` comments, including the rebased `tui_app_server` call sites that now fall under the lint - keep the checked-in style aligned with the lint policy by using `/*param*/` and leaving string and char literals uncommented - cache `cargo-dylint`, `dylint-link`, and the relevant Cargo registry/git metadata in the lint job - split changed-path detection so the lint crate's own `cargo test` step runs only when `tools/argument-comment-lint/*` or `rust-ci.yml` changes - continue to run the repo wrapper over the `codex-rs` workspace, so product-code enforcement is unchanged Most of the code changes in this commit are intentionally mechanical comment rewrites or insertions driven by the lint itself. ## Verification - `./tools/argument-comment-lint/run.sh --workspace` - `cargo test -p codex-tui-app-server -p codex-tui` - parsed `.github/workflows/rust-ci.yml` locally with PyYAML --- * -> #14652 * #14651 |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
WARNING: this code is mainly generated by Codex and should not be used in production
codex-debug-client
A tiny interactive client for codex app-server (protocol v2 only). It prints
all JSON-RPC lines from the server and lets you send new turns as you type.
Usage
Start the app-server client (it will spawn codex app-server itself):
cargo run -p codex-debug-client -- \
--codex-bin codex \
--approval-policy on-request
You can resume a specific thread:
cargo run -p codex-debug-client -- --thread-id thr_123
CLI flags
--codex-bin <path>: path to thecodexbinary (default:codex).-c, --config key=value: pass through--configoverrides tocodex.--thread-id <id>: resume a thread instead of starting a new one.--approval-policy <policy>:untrusted,on-failure(deprecated),on-request,never.--auto-approve: auto-approve command/file-change approvals (default: decline).--final-only: only show completed assistant messages and tool items.--model <name>: optional model override for thread start/resume.--model-provider <name>: optional provider override.--cwd <path>: optional working directory override.
Interactive commands
Type a line to send it as a new turn. Commands are prefixed with ::
:helpshow help:newstart a new thread:resume <thread-id>resume a thread:use <thread-id>switch active thread without resuming:refresh-threadlist available threads:quitexit
The prompt shows the active thread id. Client messages (help, errors, approvals)
print to stderr; raw server JSON prints to stdout so you can pipe/record it
unless --final-only is set.
Notes
- The client performs the required initialize/initialized handshake.
- It prints every server notification and response line as it arrives.
- Approvals for
item/commandExecution/requestApprovalanditem/fileChange/requestApprovalare auto-responded to with decline unless--auto-approveis set.