DEV Community

I Built a TUI That Makes Rust Code Inspection Feel Like Magic ✨

Yash Kumar Saini on February 15, 2026

This is a submission for the GitHub Copilot CLI Challenge The "Why Did I Build This?" Moment Okay so here's the thing. I was working on...

Read full post

Anmol Baranwal • Feb 16

nice 🔥 how long did it take to build this? I love when solo devs publish proper versioned releases on github.

Yash Kumar Saini • Feb 16

Thanks anmol you are not going to believe built the entire thing in just 2 days of time

Anmol Baranwal • Feb 17

whoa. that is impressive :)

Fyodor • Feb 21

Wow, that's damn fast 👍🏼 Great technology choices btw, and awesome practical idea 🔥 How familiar with Rust are you? (I mean, you didn't need to learn anything deeply in the process right?)

Yash Kumar Saini • Feb 21

Thanks, grateful that you love it, Please try and provide feedback on it, Really appreciate it,

github.com/yashksaini-coder/oracle

Matthew Hou • Feb 20

Terminal UIs for code tooling are having a moment right now, and for good reason.

The efficiency argument: a well-designed TUI removes the "where do I find this thing?" problem that GUIs create. Everything is accessible via keyboard, the information density can be higher than a GUI, and it works over SSH without any setup.

The Rust ecosystem is interesting for this because ratatui and similar crates make TUI development genuinely accessible. I've been meaning to build something similar for visualizing async task graphs. Does yours handle very large codebases well, or does the analysis slow down above a certain size?

Yash Kumar Saini • Feb 21

Thanks I really like working in rust and building this TUI, Yeah, it's not the strongest area right now. The analyzer walks through your Rust files one by one and parses them sequentially — no parallel processing or threading.

For small to medium projects that's totally fine and snappy, but if you're pointing it at a massive codebase with thousands of files, you'll notice it slows down. It's definitely something that could be improved with some parallelization (like using rayon or a thread pool), but that's not implemented yet.

That said, the project is actively being developed, so this could improve over time, currently working on implementing some proper working and algos to imrpove the analysis, It can work on large codebase but if you took a very heavy codebase with 1000s of files, then you will see some slowdown.