Vigil

Built for Windows 10 & 11

Your agent has been waiting 11 minutes. You had no idea.

Vigil is a Windows-native always-on-top overlay that shows every Claude Code, Codex, Grok, Antigravity and Kimi session in real time — and lets you approve, answer and interrupt them without leaving what you're doing.

Interactive demo

This is Vigil, running.

The panel below is a live recreation of the Vigil overlay. When the agent asks for permission, answer it yourself.

A blank Windows desktop with the real taskbar, used as the backdrop for the interactive Vigil demo.
api-refactorWORKINGCLAUDEEdit src/auth/middleware.ts3m

Features

The demo shows the loop. Below is the rest of the cockpit — usage on the notch, policies per agent, history, and more.

See everything

Every session, every state, at a glance.

  • Real-time state for each agent: working, waiting, done, error, disconnected
  • Last 20 messages of any conversation, without opening the terminal
  • Sub-agents, grouped under the session that spawned them
  • Token statistics and usage windows — know how much quota you have left

Act without switching windows

Answer the agent from where you already are.

  • Approve or deny a permission request in one click
  • Answer an agent's question by typing directly in the overlay
  • Interrupt a running agent when it's going the wrong way
  • Jump straight to the right terminal when you do want to dive in

Stay out of the way

An overlay you forget about until it matters.

  • Fades back when agents are working, steps forward when they need you
  • Light enough to leave running all day
  • Drag it anywhere, on any monitor
  • Starts with Windows, or doesn't — your call

Usage on the notch

See remaining quota and usage windows on the notch itself — and pick which agent’s window you care about. Not buried in a secondary panel.

Permission policy, your way

Set approve, deny, always-approve, or manual defaults per tool — and override them per agent. Full control when one session is noisier than the rest.

Permissionsapi-refactor
Edit / Writeglobal
Readglobal
Web fetch / searchglobal
Otherglobal

Conversation without the terminal

Open the last messages of any session in the overlay. Read context, then jump to the terminal only when you need to type code.

Sub-agents in the notch

Child sessions stay grouped under the agent that spawned them — visible in the compact bar, not lost in a separate list.

api-refactorWORKINGCLAUDEEdit src/auth/middleware.tsExploreBashRead3m+2

Notch display modes

Priority agent with overflow, multi-agent side by side, or a detailed single-agent row. Match the bar to how you run your fleet.

api-refactorWORKINGCLAUDEEdit src/auth/middleware.ts3m+2

Names and tags

Rename sessions and attach your own tags so the right agent is findable when you have more than a handful running.

History and resume

Browse past sessions and resume one when you need it — Vigil lands you back in the right terminal context.

Interrupt a running agent

Claude Code

Stop a session that is going the wrong way from the overlay — without hunting for the right window first.

And more…

The rest of the cockpit, without a full card each:

  • Customize the display — show or hide fields, pick colours, swap mascots
  • Sound cues when an agent needs you
  • Per-tool enable/disable — only hook what you use

Usage window priming

Claude Code

When your usage window is closed, Vigil can start it early so your next reset comes sooner. Opt-in, off by default, and it costs a few tokens each time.

Know what's happening, everywhere

Get pinged on your phone when an agent needs you — on your terms.

  • Telegram notifications when an agent finishes, gets stuck, or fails
  • Approve or deny from your phone
  • Choose what notifies you globally, and override rules per agent — finish only, every wait, failures, or silence one session entirely
  • Your own bot, your own token — no Vigil server in the middle
Vigilbot
Today

✓ Task finished

api-refactor · Claude Code
Auth middleware JWT migration is done. Typecheck clean, 3 tests passed.

14:07

write-tests is still working — generating coverage for the new JWT path.

14:08

Permission request

api-refactor · Claude Code
Edit src/auth/session.ts

14:09

Works with your agents

Vigil talks to each CLI through its own hook system. What it can do depends on what each tool exposes — here's exactly what you get.

What each supported CLI lets Vigil do
CapabilityClaude CodeCodex CLIGrok BuildAntigravity CLIKimi CLI
MonitoringSupportedSupportedSupportedSupportedSupported
Approve / DenySupportedSupportedLimited, see note 1Not availableLimited, see note 2
Answer questionsSupportedNot availableLimited, see note 3Not availableNot available
Interrupt agentSupportedNot availableNot availableNot availableNot available
Sub-agentsSupportedSupportedSupportedNot availableSupported
API errorsSupportedNot availableSupportedNot availableNot available
HistorySupportedSupportedSupportedSupportedSupported
StatisticsSupportedSupportedSupportedNot availableSupported
Usage windowsSupportedSupportedSupportedSupportedNot available
Usage window primingSupported, see note 4Not availableNot availableNot availableNot available
Mobile notifications, see note 5SupportedSupportedSupportedSupportedSupported
  1. Grok — Approve/Deny: full Approve/Deny from Vigil in always-approve mode. In default mode the request is shown read-only — confirm in the terminal.
  2. Kimi — Approve/Deny: full Approve/Deny from Vigil in yolo mode. In manual or auto mode the request is shown read-only — confirm in the terminal.
  3. Grok — Answer questions: shown read-only; type your answer in the terminal.
  4. Claude Code — Usage window priming: opt-in — when your usage window is closed, Vigil starts it early so your resets come sooner (uses a few tokens each time). Enable it in Settings.
  5. Mobile notifications: these work for every tool Vigil monitors. Which events reach you follows the rows above — a tool that exposes no API-error hook can't tell you it failed — and approving from your phone follows the Approve / Deny row.
  6. Why the gaps? Each CLI exposes a different set of hooks. Where a cell is empty, the tool simply doesn't give Vigil anything to work with — we'd rather show you than let you find out after you install.

More on the way. New tools ship as free updates.

Up and running in a minute

  1. Install

    Download the installer and run it. It installs for your user only — no admin rights required. Windows will warn you the first time: Vigil isn't EV-signed yet. Click "More info", then "Run anyway".

  2. Review, then allow

    Vigil shows you exactly what it will add to your tools' config files. You approve, or you don't. Nothing happens behind your back.

  3. Start an agent

    Launch Claude Code as usual. It shows up in the overlay instantly.

Changed your mind? Uninstalling from Settings restores every config file to exactly how it was.

There is no Vigil server

Your prompts, your code and your conversations never pass through us — because there's no "us" to pass through. Here's every connection Vigil makes, and why.

No backend, no account, no telemetry. Vigil has no servers. You never create an account. We collect nothing about you — there's nowhere for it to go.

Your conversations stay on disk. Vigil reads your agents' local transcripts to show them to you. It never uploads them, anywhere.

Agents talk to Vigil over a local Windows named pipe. That's the entire architecture.

Every outbound connection

Goes toWhat forWhen
api.anthropic.comReads your Claude usage limitsOnly if usage tracking is on
chatgpt.comReads your Codex usage limitsOnly if usage tracking is on
cli-chat-proxy.grok.comReads your Grok usage limitsOnly if usage tracking is on
api.telegram.orgSends notifications to your botOnly if you set up mobile notifications
api.github.comChecks for a new Vigil versionOn startup

Every one of these goes either to a service you already use, with credentials already on your machine, or to Vigil's own housekeeping — checking for updates. None of them go to us.

Questions

Is Vigil free?

Yes. Download it and use it. Vigil is free — nothing to activate, and nothing that expires.

Do I need an account or a licence?

No. There is no account and no licence. Install Vigil and it runs.

Is the source code public?

Yes. Vigil is open source (MIT). The code is on GitHub.

Does Vigil work without an internet connection?

Yes. Vigil runs locally, so it keeps working offline. Nothing phones home to unlock it, so a bad Wi-Fi connection will never lock you out. It reaches the network only for the things you turn on — usage limits, your own Telegram bot — and to check for a new version.

Does Vigil send my code or prompts anywhere?

Your code and prompts, never. Vigil does talk to a few services — your agents' own providers, for usage limits, and your own Telegram bot if you set one up. Here's the full list.

What exactly does Vigil change in my config files?

It adds hook entries to the config files of the tools you enable — nothing else. Vigil shows you the exact change before it makes it, and uninstalling restores every file to how it was.

How do I reinstall, or move to a new machine?

Install it again. Nothing to activate and nothing to turn off. Your settings stay on that machine's disk; on a new machine you start fresh, or copy them yourself. Use Vigil on as many machines as you like.

Which Windows versions are supported?

Windows 10 (version 2004 and later) and Windows 11, 64-bit. Vigil is Windows-native — there is no macOS or Linux build. Mac agent islands don't run on Windows; this product is built for Windows developers.

Why doesn't feature X work with tool Y?

Because that CLI doesn't expose the hook Vigil would need. The compatibility table above shows exactly what each tool supports.

Windows says it doesn't recognise the installer. Is that normal?

Yes. Vigil isn't signed with an EV certificate yet, so Windows SmartScreen warns you the first time you run the installer. Click "More info", then "Run anyway". Everything else about the install is ordinary: it goes into your user profile, it needs no admin rights, and uninstalling removes it cleanly.

How do I get support?

Email stevenpf@gmail.com, or open an issue on GitHub. Bug reports get a reply.

Stop waiting on agents that are waiting on you.

Free. No account, no licence.

Open source (MIT)

Windows 10 & 11 · No Vigil server