Launching today
Terminal Mode by Even Realities
Keep coding agents always in sight
416 followers
Keep coding agents always in sight
416 followers
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.
Terminal Mode by Even Realities
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?”
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.
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.
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!