Last month I posted about wiring the G2 into the AI coding agents already sitting on my Mac, so the glasses answer like they know what I do all day instead of like a search box. That post went way better than I expected, and honestly the DMs have been the best part of it. (Original post here if you want the architecture and the SDK gotchas.)

Three weeks later it's basically different software, and about 250 people have set it up so far. Here's where it's at. The giveaway details are near the bottom.

GotCOS has a Mac app now

https://preview.redd.it/lckrpa72mdjh1.png?width=3000&format=png&auto=webp&s=036926f0eea43240c8a91d7924e4aba7a364c6f5

Version one was a terminal command and a lot of faith. Now there's COS Control, a menu bar app that runs the server for you, shows you what's actually running, updates without breaking itself, and can repair common install or update failures. After setup, you shouldn't need the terminal for normal use.

It opens on an Activity view, which I did not expect to use nearly as much as I do. Six windows into what your COS is already holding: Messages, Speakers, Meetings, Memories, Threads, and your agent Sessions. You stop guessing what it caught. Every meeting, every answer, every voice it's learned is sitting there in a list you can open.

It knows who talked

https://preview.redd.it/jmdhc872mdjh1.png?width=3200&format=png&auto=webp&s=84b2813ff735406f1c9d67b1bd1b79ffaaa3e8e6

This one surprised me. Meetings get transcribed locally, and now voices carry across them, so somebody you talked to three weeks ago shows up by name in today's call instead of as "Speaker 1" all over again.

It was hard, and I built the review tools before I trusted the accuracy at all. Below a confidence floor the panel just says "unidentified" rather than guessing, because a confident wrong name is worse than no name. You can play the audio back, confirm a voice, or tell it "nope, wrong person" and it'll retract whatever training that mistake created. With a microphone strapped to your face in a real room, that correction loop is doing most of the work.

Everything else that shipped

https://preview.redd.it/hjiqq772mdjh1.png?width=3200&format=png&auto=webp&s=afd31d109162e34168db1630855fae697282a1f7

• Meetings show up faster. A saved meeting used to wait on the full high-quality pass before it landed anywhere. Now it appears right away, then the higher-quality pass fills in the rest.
• Transcription got faster when nothing else is going on. The post-meeting polish grabs the GPU when nothing live is competing for it, and hands it back the second a meeting starts. Roughly 6x faster per word than the CPU path.
• Live text on the lens while you're still talking, swapped for the real transcript once it commits.
• Video uploads resume now instead of dying on a bad connection.
• Photos on the lens at 288x144, plus answer images you can pull up on the G2.
• Jobs still live on the Mac, so you can close Even Hub or drop off Wi-Fi and the answer is waiting when you get back.

Cursor works now, and there's no second bill

Not just Claude Code and Codex anymore. Cursor works too, so you can put Grok or Composer behind the glasses. You pick the model per question from the lens and swap mid-conversation if one isn't getting it. Three agent CLIs, whichever one you're already paying for.

Which gets to the thing people keep assuming wrong. GotCOS doesn't add a separate API bill. It signs in through the CLI you already use, so it runs on the Claude Code, Codex, or Cursor account you already have, subject to that provider's plan and limits. Nothing to paste, nothing metering you per token.

Whatever can run entirely on your machine already does. Transcription is local by default through whisper.cpp, so meeting audio never leaves the Mac, and spoken replies can be local too. Cloud transcription is there as a fallback but it's off until you turn it on, and just configuring a key won't upload anything on its own. To be precise, since this crowd will ask: the reasoning still goes to whichever provider you signed into, on your existing plan. What's local is the transcription, the speech, and the files. Meetings, memories, and transcripts sit on your disk as plain files you can open, grep, back up, or delete.

It works inside the Hub, not around it

Saying this plainly since there are a few different approaches floating around this sub. It's a marketplace app. You install it from the Even Hub like anything else. Nothing to flash, nothing to unlock, no warranty to worry about. I build inside the Even Hub SDK sandbox and code around whatever it hands me.

That's a tradeoff and I'm not claiming it's the better one. The custom firmware folks get past walls I have to engineer around, and I've picked things up from their work. But if you want your glasses doing more without modifying the glasses, this is the path.

What you end up with is a workflow that stays on hardware you already own. Ask a question, read it on the lens. Talk, and watch the transcript appear while you're still talking. Point the server at a folder and the agent works through the files in it, including whatever your Mac already syncs down from iCloud Drive. A meeting you just recorded becomes a file the agent can read a minute later, so you can ask about it without exporting anything anywhere.

Two people this owes something to

u/ICE_MF_Mike ran my server through his own Claude setup after the last post and came back with an actual security review. Shell injection in a title generator, file permissions, network defaults, a Telegram switch that should have been opt-in. He was right about all of it, and all of it is patched and shipped. Best thing that's happened to this project.

u/True-Benefit-4856 is the only reason there's a desktop app. The companion started as their idea and turned out to be the one change that made this usable for anyone who doesn't want to live in a terminal.

If you read the source and find something, I want to hear it. It's MIT, it's on npm, and it runs on your machine, so read it before you run it.

The giveaway: a pair of G2s

https://www.gotcos.com/challenge/

I've got a second pair sitting here and I'd rather they go to somebody who'll do something interesting with them than sit in a drawer.

To enter: comment with what you'd build or how you'd use it. Not a wishlist. The actual use case, the workflow, the thing you can't do today and want to. Feature ideas for COS Glasses count, and so does a completely different application of the hardware.

How I'll pick: I read all of them and pick the one I most want to see exist. Best idea wins, upvotes don't decide it, though I'll definitely read the ones you upvote.

Deadline: October 1.

Fine print: used pair, good condition, mine to give. Open worldwide, and the winner covers shipping from the US plus any customs or duties on their end. I'd rather send these to the right person in another country than limit it to one. You don't need to be running COS Glasses to enter, and running it doesn't help your odds. If your idea wins and it's something I can build, I'd rather build it with you than for you.

Setup

• Setup wizard, about five minutes: https://www.gotcos.com/wizard/
• The Mac app: https://www.gotcos.com/control/
• Full docs, every feature on one page: https://www.gotcos.com/docs/
• Source, MIT, on npm: https://www.npmjs.com/package/@gotcos/glasses-server
• Even Hub: search “COS Glasses”

You need at least one of Claude Code, Codex CLI, or Cursor installed and signed in. Whichever you already have is fine. It works standalone, and if you're already running a bigger COS setup, point the server at that folder and the glasses inherit all of it.

I keep calling this a side project and it keeps being the thing I use every single day. Recording a customer call and asking what I missed. Logging an idea halfway through a walk without pulling my phone out.

If you try it and it breaks, tell me and I'll get you running. Building against this SDK yourself? Happy to compare notes on any of the traps. And if you've got an idea for what this should do next, drop it in the comments, because there's a pair of glasses in it for one of you.

Do you love Codex Pets too? I’ve got something for you!

I wanted a more visual way to see what Codex was doing, especially when several tasks and subagents were running at the same time.

So I built Codex Avatars, an open-source Windows companion that gives each Codex task and subagent its own animated Pet on your desktop.

Features include:

• Independent avatars for main agents and subagents
• Live working, waiting, completed, and dormant states
• Task names, model, and reasoning effort displayed under each avatar
• Movement across one or multiple monitors
• Different Pet assignment modes: matching subagents or fully random
• Native Codex Pet V2 support
• An integrated Pet marketplace and direct installation
• Custom roaming areas, avatar sizes, and visibility settings
• Automatic startup with Windows and quick enable/disable controls

The overlay itself is invisible, so the Pets simply roam around your desktop while Codex works.

The project is currently Windows-only, and the installer is not code-signed yet, so SmartScreen may display a warning.

GitHub and latest release:

https://github.com/Kajdrak2/Codex-avatars

I’d love to hear your feedback, feature ideas, and bug reports. Contributions and new Pet submissions are welcome too!

Disclosure: I build Swobu (swobuforge/swobu), the open-source local compatibility gateway used here.

I wanted to use Codex’s harness with DeepSeek V4 Pro. The protocols do not line up directly: Codex sends Responses API requests, while DeepSeek currently exposes V4 Pro through Chat Completions and Anthropic-compatible interfaces. Native Responses support is available only for Flash.

Swobu translates between those protocols locally. Setup happens through an interactive terminal UI: add DeepSeek, paste your API key, then copy the local endpoint into Codex.

No hand-edited Swobu config files. No OpenRouter. No Codex fork.

Run it:

curl -fsSL https://swobu.com/install.sh | sh

I am not claiming this is the first DeepSeek–Codex bridge. DeepSeek’s official ecosystem already documents Moon Bridge. I am testing whether a general-purpose local gateway becomes more useful once you also want multiple providers, stable routes, account switching or fallback.

Swobu is still maturing, so I would especially appreciate reports of difficult edge cases.