Codex WeReply Error Handling across Rust, Tauri, and UI
Trace a local failure through Rust error context, the Tauri response, and visible frontend feedback. Verify the behavior with a controlled fixture.
中文Install in Codex
Codex with a WeReply checkout, its Rust, Tauri, and UI checks, and a non-sensitive repro fixture.
- Copy the entire pinned `.codex/skills/error-handling-debugging/` directory to `.agents/skills/error-handling-debugging/` in the target checkout.
- Open Codex in that checkout and invoke `$error-handling-debugging` with the example task and desired output.
Example task
Invoke `$error-handling-debugging` with a fictional missing config. Check the backend error context and the user-visible feedback on the settings page.What to check
The response identifies the local cause, and the UI presents understandable feedback. The fixture reproduces the outcome.
Original SKILL.md on GitHub · Updated
Frequently asked question
How should the frontend present an error?
Use the project's existing message component. The backend uses a consistent ApiResponse shape for business outcomes.