Number 08

Vira

A personal AI assistant that lives in my Mac's notch. Say "Hey Vira" or press Option+Space, and it listens, answers out loud and does things on the computer.

In progressAISoftware2026–now
Role
Sole developer. Wrote the Python core (agent, memory, voice, tools), the local service it runs as, and the Swift menu bar app with the island.
Built with
  • Python
  • Swift
  • Gemini
  • Whisper
  • Piper
  • WebSockets
Started
Apr 2026
Finished
Still going

Story

Vira started in April as Jarvis, in its own repo: a terminal chat with a local Llama model through Ollama, plus memory and a few commands. It worked, but I only used it when I remembered to open a terminal.

So I rebuilt it to be always there. The core now runs in the background at login, the brain is Gemini with other providers as fallbacks, and a small Mac app puts it in the notch like the iPhone’s Dynamic Island. I can talk to it, type to it, or ignore it until I need it.

How it works

Vira is two programs that talk over a local WebSocket:

  • The core (Python) runs as a LaunchAgent. It holds the agent, memory, tools and the provider router, and streams events as it works: text, tool calls, confirmations, notices.
  • The app (Swift) is a menu bar icon and the island. It does wake word, dictation and speech on the device, and draws whatever state the core is in: listening, thinking, working, speaking, or asking permission.

Anything risky, like deleting a file, needs a yes first. The island shows Allow and Deny, and you can also just say yes or no.

Option+Space talks, Option+Shift+Space types, and Esc cancels. Long typed replies open into a panel instead of being read out.

There’s also a fake brain for testing the app without API keys:

python main.py --service --fake

What broke

When Vira asked me to confirm something out loud, it kept listening while it spoke, so it could hear its own question and answer itself.

The fix was to gate the microphone while Vira is talking and route every yes or no through one place that owns the listening state. Cancelling had a similar bug: a cancelled reply left the conversation history half-written until I closed the agent properly on cancel.

Devlog