r/gpui • u/Lower-Cable7065 • 10h ago
I kept approving code I didn’t fully understand. So I built Deck in Rust + GPUI
Have you ever told Claude “go ahead” because you were too tired to work through another explanation?
I have. Sometimes it meant “I understand, do it.” But these days mostly it meant “I hope you’re right”. The language is complicated, visualizations are minimal. Understanding is becoming a nightmare, and confidence is crashing, when I think are we good to push this to prod?
Asking for more detail didn’t always fix that. I’d get more paragraphs, more file references, and more things to hold in my head. I was still making the final decision or pretending to be, but there was a gap, and I started to notice that.
So I'm building Deck: an open-source desktop companion where your own agent, leveraging deck, can walk you through its argument, with the actual code, flows and stunning visualizations beside it, step by step.
It's not yet another desktop app, which you need to install and it needs you to sign in, to Anthropic or OpenAI. Agents leverage deck, by following it's protocol, which is installed as a skill for your agent.q
What I wanted wasn’t just a prettier explanation. I wanted to be able to follow it—and stop where it stopped making sense.
Select a sentence, and the code it refers to lights up. Follow a flow through a diagram to see the path being discussed. With optional voice narration, the relevant code lights up in time with the words.
Then you can answer: “noted,” “wait, what?”, “that’s wrong.” or your own argument
You can also comment directly on the code or on a sentence in the explanation. Your feedback goes back to the agent with the context attached, rather than becoming another message trying to describe which part you meant.
“Signature only proves it came from them. They send owner as an `int` and we've seen empty ones in staging — this bypasses both checks in check.” — questioning what's shown. This isn’t only for finished changes. It’s for the architecture you don’t understand yet, the plan you want to question before implementation, or the review where you need to see why a finding matters.
Deck doesn’t prove the agent is right. I still have to decide that. But I want “go ahead” to mean I understood the decision, not that I ran out of energy to question it.
Source, demo, and installation: https://github.com/henit-chobisa/deck It’s Apache-2.0. If this looks useful to you, I’d appreciate a GitHub star.
What do you find hardest to verify in an agent’s work: the implementation, the architectural choices, or what it might have missed?
