StareBrain

Building StareBrain — say a command in plain English, see exactly what it's about to do, confirm before anything runs. The hard part was never parsing the command. It's designing the confirmation screen itself.

My first instinct was to sort actions by category and give "sensitive" ones (messaging, calls) more scrutiny than others (wifi, app launching). Got pushed on this in a thread this week, and the reframe stuck: the real split isn't risk, it's recoverability. Toggling wifi and moving a calendar event with notice are both trivially reversible. Sending a text or placing a call isn't — there's no unsend on a message someone's already read, regardless of how "risky" typing it felt.

That test holds up better than risk ever did, because the two come apart constantly. A scary-sounding action can be fully reversible. A boring one can't be undone at all.

So the confirmation screen is changing: low-stakes, reversible steps collapse into one compact plan. Anything irreversible gets its own explicit line, even if that makes the screen longer. Betting that costs a second of reading time and buys real trust.

Building in public as I go — link in profile if you want to follow along.

Building a natural-language command app for Android — say something, get a plain-English confirmation, approve it, it executes. The pitch is "nothing happens without your say-so."

Except I hit a gap: the world can change in the seconds between confirmation and execution. User approves "book 2pm with John," but by the time it fires, that slot's gone. Or approves a text to "Sarah," but Sarah's number just changed. The confirmation was correct when shown — it's stale by the time it runs.

Right now the fix is naive: re-check whatever the action actually depends on immediately before firing, and if something material shifted, don't silently proceed — kick it back to the user instead of guessing that the new state still matches their intent.

Curious how others building confirm-before-execute or agentic flows handle that gap. Do you re-validate right before the action, treat it as a transaction with rollback, or just accept the small window and move on?

Uploaded the first video to StareBrain's YouTube channel this week (@starebrain), a short demo of the say-it-confirm-it-happens flow.

Also had two genuinely useful exchanges on Indie Hackers that are shaping the confirmation logic directly. One: verification and the report of what was verified aren't separable, a system can't claim "I couldn't confirm this" credibly unless something real actually tried to check first. Two: testing whether sample agreement across repeated model attempts can distinguish genuine ambiguity from ordinary hedging, before deciding whether to ask a clarifying question or just proceed.

Both are going into how StareBrain decides when to show a confirmation versus ask a follow-up question, rather than treating that as a fixed rule.

Small week technically, but the confirmation step is the whole bet here, so getting it right matters more than shipping new commands right now.

A conversation this week pushed me to test something I hadn't considered: instead of only building toward the full app, publish the interpretation logic itself, real example commands and the exact structured plan StareBrain would generate for each one. No app required to see it.

The idea is to test whether the core value (understanding what someone actually wants, clearly, before anything executes) is interesting on its own, before the harder app-shaped problems (permissions, reliability, on-device execution) are fully solved.

Also set up a YouTube channel this week (@StareBrain) to start sharing the real app running, not just screenshots. First real upload coming soon.

Small, unglamorous week of testing ideas rather than big news, but that's honestly most of what building this actually looks like.

StareBrain started as a personal annoyance: tapping through five screens on my phone for things I already knew exactly how to describe in one sentence.

Currently pre-launch, waitlist open. The core mechanic is simple: say what you want done, see exactly what StareBrain is about to do, then it executes only once you confirm. Most AI assistants either act too autonomously or bury confirmation behind assumptions you never see, this flips that.

Been building in public for the past few weeks, real conversations, real feedback, real mistakes along the way (including a demo video that got 19 views and zero engagement, which was more useful than it sounds). Posting updates here as things progress.

If you want to follow along or try it early: starebrain.vercel.app