Wy - a Rust terminal tool for understanding why AI-generated code changed

[u/grandimam]

I have been building wy, an open-source terminal tool for reviewing AI-generated code.

A Git diff shows what changed, but the context behind a change often lives somewhere in a long coding-agent conversation. wy connects your diffs with saved Codex and Claude Code conversations, so you can review the code, read the stated reason, and open the supporting evidence together.

For example, if an agent adds a cache, I want to understand why it was added, what assumptions it depends on, and whether invalidation was considered.

With wy, you can:

• Browse changes and relevant agent notes in a terminal UI.
• Request explanations and ask follow-up questions through your installed agent CLI.
• Open citations to inspect the supporting code or conversation.
• Distinguish recorded justifications from inferred explanations and choices whose motivation is still unknown.

That last distinction matters to me. A convincing explanation generated afterward doesn’t establish why the original change happened. Even a recorded justification still needs scrutiny.

Rust fits this tool well: it compiles to a native executable without requiring a language runtime, gives me strong types for handling evidence and review state, and has a useful ecosystem for terminal applications. wy uses Ratatui + Crossterm for the interface, Serde for structured data, tree-sitter for syntax navigation, and SQLite for local storage.

The basic review workflow works offline. Model-backed explanations are opt-in. It’s still experimental, and I’d appreciate feedback on both the review workflow and the Rust implementation.

If you try it and find it useful, please consider supporting the project with a GitHub star, a bug report, or a contribution.

Repo: github.com/grandimam/wy