Terminal Mode by Even Realities
Keep coding agents always in sight
Start new thread

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.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt, I’m David from Even Realities. Today we’re launching Terminal Mode by Even Realities for Even G2 smart glasses: an ambient terminal for the AI coding agents running on your laptop. AI coding agents are getting better at long-running tasks. But they still stall at small human moments: a review approval, a blocked command, a quick instruction, a yes/no choice. If you miss that moment, the agent waits. Terminal Mode makes sure you never miss that moment on Even G2 glasses. Your laptop still does the heavy work. Even G2 gives you a terminal layer in your line of sight, so you can see which agent needs you now, give a short voice instruction, and approve key steps with a tap. This is not about replacing your laptop. It is about filling the gaps between focused desk time, so your agents do not sit idle just because you stepped away from the screen. Terminal Mode by Even Realities unlocks: - Monitoring AI coding agents from Even G2 smart glasses - Seeing which agent is running, blocked, or waiting - Giving quick direction by voice - Approving key steps with a tap - Keeping agents moving while you are on the go We’d love feedback from builders using Claude Code, Codex, Cursor, or other coding agents: What are you building with coding agents right now, and when do they usually get stuck?

 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".

Maker

 

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. :))

Maker

   
Exactly. The important distinction is that Terminal Mode doesn’t remove human-in-the-loop approvals; it makes them less tethered to the laptop.


Same decision, less context switching.

Maker

 

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.

 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!

Maker

 

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.

Maker

   
For me the win is catching those moments earlier, not making every decision easier.

 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?

Maker

   
That’s the central design tradeoff for us.

We don’t want G2 to become another notification surface. The goal is not to make agents feel constantly demanding, but to make the important state changes visible when they would otherwise be missed.

So we think about it in two layers: quiet visibility for normal progress, and intentional interruption only when the agent actually needs human input: blocked, waiting, approval needed, or ready for review.

The value is preserving deep focus while still catching the moments that would quietly waste time.

 David, is there a way to get a glass (not yours, a general one on the market) that mirrors my iPhone screen 1:1 (like AirPlay) and nothing more? No camera, no mic, no extra sensors, nothing, just mirroring my iPhone screen, so I can use it without looking down while walking.

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?

Maker

 
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?

Maker

 

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. :)

 That's pretty cool! Congrats to the launch!

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?

Maker

 
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?”

Maker

 

We don't make the decisions for you - the last thing we want to do is to filter out an important "rm rf". All the permissions that pops up in your agent will pop up on the glasses. If you are feeling frisky today, you can try various settings that eliminate permissions from the CLI :))

Also, nice name!

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

Maker

 

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.

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.

Maker

 

That's the bet. A single approval isn't worth a product. - that's why we feel it makes sense to be in your line of sight when your agents need you.

Glad it lands!

Can I write code on my eyes? Hahahaha

Maker

 

You instruct & interact with the agents that write the code in your glasses (which is arguably the more efficient way :D).

This is one of those products that makes you rethink what "working with AI agents" should actually look like. Instead of being glued to a screen waiting for outputs, you can supervise work while living your life. Really fascinating direction for human-AI collaboration. 👏

Maker

 

Cannot agree more. The principle that inspires us is "let agents work & let humans live".

How do you prevent accidental approvals while moving around or during daily activity?

Maker

 

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.

Maker

 

Ditto.

We heavily try to cut out the things that aren't absolute musts. This is how we can show you what really matters.

1234
Next
Last