Install guide

Install, then
you're on watch.

Drag Vigil to Applications, open it, then connect Claude Code or Codex. Because releases are intentionally ad-hoc signed, macOS may need one explicit confirmation.

1

Download, then drag it in.

Grab the build for your Mac (Apple Silicon, 5.7 MB or Intel, 6.0 MB), open the dmg, and drag Vigil into Applications.

Open Vigil normally. If macOS blocks the first launch, open System Settings → Privacy & Security and choose Open Anyway beside the Vigil notice.

2

You're on watch.

Vigil settles into the menu bar. Claude Code and Codex are auto-detected; connect them from Settings. Codex then asks you to open its terminal, run /hooks, and trust each yellow Review item. Status goes live on the next agent event.

Updates stay checkable.

Vigil checks for new versions quietly and lights an update arrow in the menu bar when one is out. Releases are intentionally ad-hoc signed, with no Apple Developer ID or personal signing identity attached, so macOS may ask you to approve the first launch in Privacy & Security. An update can also require Accessibility to be re-authorized for exact click-to-focus; the permissions section below shows how. CI verifies the anonymous signature, app contents, architecture, and version, and each release publishes an architecture-specific SHA-512 value to compare with the downloaded DMG.

The optional permissions, plainly.

Watching your agents does not require special macOS access. These prompts only appear when you use exact click-to-focus.

Accessibility
Lets a project click raise the matching editor window, terminal tab, or tmux pane instead of only opening the app. An ad-hoc update can require reapproval; remove any stale Vigil entry and add the current /Applications/Vigil.app.
Automation
macOS may ask before Vigil controls System Events, Terminal, or iTerm to select that exact session. You can deny it; Vigil falls back to a less precise app open.
Everything else
Hooks, local usage tracking, limit meters, sounds, and visual alerts work without either permission. Vigil does not need Screen Recording.

What it writes, and removing it.

Vigil is tidy on purpose. Here's everything it touches, and how to take it all back.

Its own folder
~/.vigil/ holds the local server port, an auth token, and any sound packs you install.
Agent hooks
A few lines are merged into ~/.claude/settings.json (Claude Code) and ~/.codex/config.toml (Codex) by default; CLAUDE_CONFIG_DIR and CODEX_HOME are honored. Your existing settings are preserved; only Vigil's hook entries are added. Claude login and Codex /hooks review happen in each tool's terminal, not its desktop app.
App data
Preferences and stats live in ~/Library/Application Support/Vigil. Nothing leaves your Mac.
Clean uninstall
Settings → Uninstall restores your agent configs, removes Vigil's hooks, scripts, and data, then moves the app to the Trash. That's it, no leftovers.
Download for Apple Silicon5.7 MB Intel Mac6.0 MB Back to the tour
Free beta · macOS 12+ · direct download, always the newest build