Terminal Mode by Even Realities - Keep coding agents always in sight
by•
Terminal Mode by Even Realities unlocks an ambient terminal on Even G2 smart glasses. When a coding agent stalls, you catch it: see which agent needs you now, give direction, and approve key steps while your laptop runs long tasks, so token-maxers get more from every run and vibe coders stay in flow.
Replies
Terminal Mode by Even Realities
@yulesenmiao congrats on the launch David. This is really interesting, how do you prevent the glasses from becoming another notification surface and fatiguing the user? in your cc use case, there are many, many "allow once".
Terminal Mode by Even Realities
@zolani_matebese
Very good question;
We are not looking to eliminate the approval process - frankly, we heavily believe in "human-in-the-loop". What terminal mode aims to do is to present the information in a more accessible, less tethered format.
& having the information in front of your sight that you can act on with a simple hand motion is arguably more efficient then pulling out the device, scrolling through, and then act. :))
Terminal Mode by Even Realities
@yulesenmiao
We first built Terminal Mode for our own team, and it quickly changed how we worked internally: fewer terminal check-ins, fewer idle agents, and less context switching back to the laptop.
That’s why we’re launching it here. We wanted more builders to benefit from the same workflow.
@yulesenmiao Congratulations on the launch, David!
This feels like a very practical solution to a real problem. I use AI coding agents for development, research, and automation, and they rarely fail on the hard tasks. More often, they get stuck waiting for a quick approval, clarification, or decision while I'm away from my desk.
Two questions: have you found that most delays come from missed approvals, or are there other common bottlenecks that Terminal Mode helps solve? And the second one is, how do users avoid notification fatigue while staying responsive to the agents that actually need attention?
Wishing you and the team a fantastic launch!
Terminal Mode by Even Realities
@md_khayruzzaman
I was hoping someone would ask this.
The other part that Terminal helps with is to keep track of what your agents are doing. When using something like /goal, one misdirection can waste hours of time and tokens; so waking up the screen to check every now and then on a hard task can give you a big boost in terms of result.
Re: fatigue, there is no real solution, as fatigue, imho, is proportional to effort. Terminal mode is to help you keep agents more accessible, not the decision process simpler.
@yulesenmiao Kudos on the launch. At what point does keeping agents "always available" become distracting rather than empowering? How did you think about balancing responsiveness with preserving deep focus?
Curious about latency here. How quickly does a blocked agent show up in the glasses after the state changes?
Terminal Mode by Even Realities
@jocky
Path is agent runner -(network)-> companion app -(BLE)-> glasses.
BLE write is ~100ms; the dominant cost is whatever the runner takes to flip "awaiting input." With Claude Code, it surfaces in the HUD inside ~0.5-1s of the actual block. :)
@yulesenmiao That's pretty cool! Congrats to the launch!
Interesting decision to put agent status directly in the glasses instead of another phone app. Feels like the value only works if the sync is fast enough to feel instant.
Terminal Mode by Even Realities
@song_kirby
Exactly. If it feels like another delayed phone notification, it fails. We treat G2 as a live state surface, not an inbox. It only shows moments that need you: blocked, waiting, approval needed.
In our Claude Code tests, the HUD updates roughly 0.5-1s after the agent enters that state, so you catch the stall instead of discovering it 20 minutes later.
The peripheral vision framing clicks! The stall that actually costs me is the agent that asked a clarifying question 15 min ago and just sat there quietly. How do you keep someone from tapping approve on a destructive command when the HUD can only show them one line of it?
Terminal Mode by Even Realities
@artstavenka1
That concern is exactly right — we don’t want approvals to be blind.
The HUD is glanceable by default, but approvals are not limited to one line. You can enter the session and scroll through the full context before taking action. So the one-line view is more of a “this needs you” signal, not the approval surface itself.
For anything sensitive, the flow is: notice it in peripheral vision → open the session → review the context → approve intentionally.
This feels oddly practical. Half the time an agent gets stuck, I don't notice until I come back 20 min later. Being able to keep an eye on progress w/o constantly switching context is interesting
Terminal Mode by Even Realities
@gizem_ozturk
Exactly. We’re not trying to make people watch every terminal line from glasses.
The useful part is catching the “needs you now” moment before it becomes 20 minutes of idle time. That’s where having the agent state in your peripheral vision starts to make sense.
Battery life is my biggest question. How much does Terminal Mode affect all-day wear?
Terminal Mode by Even Realities
@ea_z
Glad you are asking this; We actually put a lot of engineering efforts into this.
TLDR: Skipping all the technical deep dives, we are confidently still all-day wear & pushing two days depending your usage!
Being able to approve a tool call without touching my laptop is small in isolation. Multiplied across a full day of parallel agent runs, it's not small at all.
Terminal Mode by Even Realities
@crystalmei
That's the bet. A single approval isn't worth a product. Not breaking flow 40 times a day is - that's why we feel it makes sense to be in your line of sight when your agents need you.
Glad it lands!
Funny how the bottleneck flipped: the agent codes fine on its own, the expensive part is the human not noticing it stalled 20 minutes ago waiting for a yes/no. I run long Claude Code sessions and the round trip of "check the laptop, it was just waiting on an approval" adds up more than I'd like to admit. Glasses may feel early, but the underlying insight - agent state belongs in your peripheral vision, not buried in a terminal tab - seems right. How do you decide what's worth surfacing vs noise when multiple agents are running?
Terminal Mode by Even Realities
@david_marko
We treat it as state, not logs.
Running agents stay quiet. We surface the moments that need human attention: waiting for input, blocked, approval needed, or ready for review.
The key question is “which agent needs me now?” not “what is every agent doing every second?”
iArt.ai
How do you prevent accidental approvals while moving around or during daily activity?
Terminal Mode by Even Realities
@lizzy_leeeee
Good question. We designed approvals to be intentional, not something that can happen from a random movement.
You need to enter the specific session first, then take the approval action there. So it’s not a passive “one accidental tap and something runs” flow.
A lot of the UX work went into making sure Terminal Mode stays glanceable for status, but deliberate for approvals.
Will's line about 'a glance, a tap, a word' was probably my favorite part of the launch. Most smart glasses products try to compete with phones. This feels like a different philosophy.
Terminal Mode by Even Realities
@xiao_zhang9
Ditto.
We heavily try to cut out the things that aren't absolute musts. This is how we can show you what really matters.