Repository navigation
Releases
VIGIL v0.1.4 — the watch does not stop for a dialog
FORM OSW-01 (RETROSPECTIVE ATTESTATION)
THE WATCH DOES NOT STOP FOR PAPERWORK,
AND A RECORD INTERRUPTED IS STILL A RECORD.
Replace v0.1.3 if you have it. Two faults in that build, both found the hard way on macOS 27, both capable of losing a clip.
The freeze
After a macOS update, EVE's next launch re-prompts for VIGIL's audio grant. In the gap before you approve, the tap delivers silence — and v0.1.3 put up a modal dialog about it on the main thread. Behind a fullscreen game nobody can see that dialog, let alone click it, and while it waits nothing else runs: the overlay sticks on screen, the menu greys out including Quit, the hotkeys go dead, and a clip that was open stays open.
Confirmed by sampling the process: the main thread inside -[NSAlert runModal], behind EVE, with a record still rolling.
The notice is now a floating, non-activating panel that draws above a fullscreen Space, never takes focus, and lets the watch run underneath it. And the check that raised it counts eight seconds from the tap's last attach rather than from app start — a watch that waited an hour for EVE was otherwise raising it one tick after attaching, before a single buffer could have arrived.
The rule, now written into the code: nothing on the main thread may block waiting for a click.
The loss
An 870 MB clip was killed mid-recording — pkill sends SIGTERM, and only SIGINT was handled. What was left was an mdat with no index: no way in without untrunc, a reference clip, and guessed timing.
Two fixes, both proven by killing a running watch mid-clip:
- SIGTERM files an open clip on the way out, exactly as Ctrl-C does. That's
pkill, Activity Monitor, logout and shutdown. Verified: 12.6 s of a 13 s clip, finalised and readable. - The writer fragments every four seconds. A finalised file is a normal MP4 and edits like one. An unfinalised one — crash, power loss, SIGKILL, anything that never reaches
finish()— is readable up to its last fragment instead of being nothing. Verified under SIGKILL, which no handler can catch: 8.0 s readable of ~10. Four seconds lost instead of all of it.
Also since v0.1.3
- Clips are named for whoever was flying, read fresh from the client's window title each time a record is struck.
- The pilot's name has its own row in the overlay.
- The menu bar distinguishes waiting from buffering, and the glyph turns red with a clock while a record is open.
- Stand at login in Standing Orders.
- The audio tap rebuilds when the default output device moves.
Installing
Still ad-hoc signed and not notarised. Gatekeeper refuses it on first open and, since macOS 15, Control-click no longer overrides that: open it, let it be refused, then System Settings › Privacy & Security › Open Anyway. Permissions must be granted again after each update. A Developer ID ends that and is pending.
On macOS 27, expect one more approval prompt the first time EVE launches with VIGIL standing. Approve it; the watch keeps standing while you do.
Still true
- One watch at a time.
- A real display sleep has never been sat through — only the recovery path it takes, forced deliberately.
- Still not flown through a fleet fight.
Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).
VIGIL v0.1.3 — the launcher is not the game
Superseded by v0.1.4. This build can freeze behind a fullscreen game on a permission prompt, and loses an open clip entirely if killed. Both fixed.
FORM OSW-01 (RETROSPECTIVE ATTESTATION)
THE MINISTRY SEES ONLY WHAT IT WAS POINTED AT,
AND DECLINES TO CONFUSE A DOOR WITH A ROOM.
Replace v0.1.2 if you have it. That build could attach to the EVE Launcher and record it instead of the game — six and a half minutes of a launcher window, in the one case that matters most: VIGIL standing before the client starts.
The fix
The matcher stripped .app off a configured name and substring-matched the application name, so EVE.app became EVE and matched eve-online — the launcher. With VIGIL waiting before the client started, that was the only match, so it attached to it and never looked again.
Matching is now the bundle identifier exactly or as a dotted prefix, the application name exactly, or the executable path containing the token. The launcher lives at /Applications/eve-online.app and the client at …/SharedCache/tq/EVE.app, so a path test separates them where a name test cannot. Checked against all three real identities — the client matches, the launcher and its helper match nothing.
Verified end to end on a live machine: nothing running → waiting; launcher up → still waiting, zero attachments; client up → attached on its own within ten seconds and buffering.
Also
- The menu bar now distinguishes waiting from buffering, which it did not. It reads "Waiting for the EVE client · Nothing is being held. The launcher does not count." The glyph dims when idle.
- The glyph turns red with a running clock while a record is open. Red is drawn into the image rather than applied as a tint, because a template image takes the menu bar's own colour and cannot be made red.
- The pilot's name has its own row in the overlay. It was being cut into the state line, where "Cormorant Fell" rendered as "Cormorant Fe", and half a name reads as a rendering fault.
- Stand at login (Standing Orders), so the watch is already there when EVE starts.
- The audio tap rebuilds when the default output device moves — unplugged headphones, a waking display. It used to keep delivering from a device nobody was listening to, silently.
- Clips are named for whoever was flying:
clip-2026-08-30-121601-Cormorant-Fell.mp4.
Installing
Still ad-hoc signed and not notarised. Gatekeeper refuses it on first open and, since macOS 15, Control-click no longer overrides that: open it, let it be refused, then System Settings › Privacy & Security › Open Anyway. Permissions must be granted again after each update, because macOS keys grants to the signature and an ad-hoc signature is a hash of the binary. A Developer ID ends that and is pending.
Still true
- One watch at a time.
- A real display sleep has never been sat through — only the recovery path it takes, forced deliberately.
- Still not flown through a fleet fight.
Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).
VIGIL v0.1.2 — watch the game, not the screen
Superseded by v0.1.3. This build can attach to the EVE Launcher and record that instead of the game — most likely if VIGIL is standing before the client starts.
FORM OSW-01 (RETROSPECTIVE ATTESTATION)
THE MINISTRY RETAINS NO RECORD IT HAS NOT BEEN INSTRUCTED TO
RETAIN, AND SEES ONLY WHAT IT WAS POINTED AT.
If you installed v0.1.1, replace it. That build captured the whole display, so its buffer held several minutes of whatever was in front of you and a saved clip caught the switch into the game along with everything around it. This one records EVE's window and nothing else on the machine.
The fix
The capture filter was the whole display — a decision made early on the reasoning that a fullscreen game fills the frame anyway. It was wrong in the way that only shows up in a saved clip.
That is a privacy property before it is a framing one. A rolling buffer of your entire screen is a different object from a rolling buffer of a game.
VIGIL now targets EVE's own window, resolved by bundle identifier or application name. Nothing else can enter the frame. If the window is not there it waits and says so, rather than falling back to the display — recording the screen because the game is absent is precisely the behaviour being removed. It re-attaches when EVE returns, and notices a window that disappears without ScreenCaptureKit reporting an error by watching for frames simply stopping.
--capture display still exists for the rare case you want the screen, and says plainly what it is doing. It is also in Standing Orders.
One thing worth knowing, because it makes window capture look broken: EVE is invisible to SCShareableContent under onScreenWindowsOnly: true, since a fullscreen game lives on its own Space. --windows was added to see this and stays in.
Also since v0.1.1
- Fixed: opening About or Standing Orders and closing it killed the app. A programmatically created
NSWindowreleases itself on close, and both sheets held a strong reference as well — closing either released it twice. Three identical crash reports. - Clips default to
~/Movies/VIGIL.
Installing
Still ad-hoc signed and not notarised, so Gatekeeper will refuse it on first open and, since macOS 15, Control-click no longer overrides that: open it, let it be refused, then System Settings › Privacy & Security › Open Anyway. Permissions must be granted again after each update, because macOS keys grants to the signature and an ad-hoc signature is a hash of the binary. A Developer ID fixes that permanently and is pending.
Still true
- One watch at a time.
- Display-sleep and resolution-change recovery is designed for but has never been exercised.
- Still not flown through a real fleet fight.
Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).
VIGIL v0.1.1 — failure made visible
Superseded by v0.1.2. This build captures the whole display, not just EVE — its replay buffer holds whatever is in front of you. Do not use it.
FORM OSW-01 (RETROSPECTIVE ATTESTATION)
EVERYTHING ABOVE OBSERVES; NOTHING ABOVE JUDGES.
THE MINISTRY IS MERELY NOTING.
The first build you can download. Read the two warnings below before you do — they are not boilerplate.
Installing
This build is ad-hoc signed and not notarised, because the maintainer's Apple Developer enrolment is still being processed.
1. Gatekeeper will refuse it on first open. Since macOS 15, Control-click no longer overrides that. Open it, let it be refused, then go to System Settings › Privacy & Security and press Open Anyway. Or strip the quarantine attribute yourself:
xattr -dr com.apple.quarantine /Applications/VIGIL.app
Never do that to software whose provenance you cannot vouch for. The source is here; read it, or build it yourself, and then you can.
2. Permissions must be granted again after every update. macOS keys permission grants to the code signature, and an ad-hoc signature is a hash of the binary — so each build is a brand-new application as far as the system is concerned. Screen Recording and System Audio Recording will both ask again on the next release. A Developer ID certificate fixes this permanently and is coming.
If either of those bothers you, build from source instead. It sidesteps both.
What changed since v0.1.0
- Failure is visible without a terminal. VIGIL is an agent app with no window, so a double-clicked bundle had nowhere to put a message — it exited looking like it had simply declined to start. Setup failures, a refused second instance, and a tap delivering nothing but zeros now all reach the screen, and everything is mirrored to
~/Library/Logs/VIGIL/vigil.log. - Standing Orders. A preferences window: rebind the chord, choose the clips folder, set replay length, memory ceiling, audio, capture size, frame rate and codec. The chord and folder apply at once; the rest when the watch next stands.
- An icon. Struck from the office seal — the full seal at 128 points and above, the glyph alone below, where the ring text turns to mud.
- Clips default to
~/Movies/VIGIL. They belong to the instrument, not the estate.
Still true, and still worth saying
- One watch at a time, enforced by an advisory lock.
- Display-sleep and resolution-change recovery is designed for but has never been exercised. Untested recovery code is a guess.
- A rebound chord that collides with another application usually cannot be detected:
RegisterEventHotKeygrants the same chord to several processes without complaint. - It has still not been flown through a real fleet fight. Every measurement so far is of a ship sitting in space, where the bitrate never approaches its ceiling.
Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).
VIGIL v0.1.0 — the watch stands
FORM OSW-01 (RETROSPECTIVE ATTESTATION)
THE MINISTRY RETAINS NO RECORD IT HAS NOT BEEN INSTRUCTED TO
RETAIN. THE PRECEDING MINUTES ARE HELD IN CONFIDENCE, AND ARE
OVERWRITTEN UNREAD.
The first filing. A replay recorder for EVE Online on macOS: the last five minutes of your client live in memory, and nothing reaches the disk until you strike the record. Striking it opens a clip containing everything already held and keeps recording until you close it.
What works
- Ring in memory, not on disk. ScreenCaptureKit → VideoToolbox → a segmented ring, 15 seconds to 15 minutes, with a byte ceiling as well as a time window.
- Saves reach backwards. The buffered past is muxed passthrough — nothing re-encoded — so a five-minute retrospective lands in about ten milliseconds.
- Audio chosen separately from video. A Core Audio process tap, because
SCContentFiltercouples audio selection to video framing and "the whole display, but only EVE and Discord" is unreachable through it. - Survives EVE relaunching.
processRestoreEnabledworks by bundle ID and EVE's client reports none, so VIGIL watches the audio process list and rebuilds the tap itself. - Overlay, menu bar, and Standing Orders. The chord and the clips folder are rebindable; the office stamps when it hears you.
Measured
Against a live client on an M5, native 3024×1964: 57.5 fps, zero dropped frames, audio and video durations matching, A/V within ±40 ms.
Build it yourself
There are no binaries here, and that is deliberate. VIGIL is signed for development, not distribution — it is not notarised, so Gatekeeper would refuse a copy that arrived from anywhere but your own compiler. A Developer ID is a later problem.
git clone https://github.com/mogglemoss/VIGIL
cd VIGIL
./bundle.sh
'.build/VIGIL.app/Contents/MacOS/vigil' --check --audio all
Run --check first. A denied System Audio Recording grant is invisible — every Core Audio call returns noErr and the buffers are zeros — so measuring the signal is the only honest test.
Known limits
- Not notarised. Build from source.
- One watch at a time, enforced by an advisory lock.
- Recovery from display sleep and resolution changes is designed for but has never actually been exercised. Untested recovery code is a guess.
- A rebound chord that collides with another application usually cannot be detected:
RegisterEventHotKeygrants the same chord to several processes without complaint. - It has not yet been flown through a real fleet fight.
Where this sits with CCP's rules
Nothing is injected, no memory is read, no packets are touched, no cache is scraped. The overlay is a separate window composited by WindowServer; capture is an OS framebuffer read. The hotkey receives — nothing is ever synthesised into the client. VIGIL will never react to game state, because that is the line. See the README.
Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).