GET STARTED
Connect your context.
Explore fictional data in Demo Mode without an endpoint. For live telemetry, Vigil connects to an API you or your team operate. Managed telemetry hosting is not included.
1. Install Vigil for Mac
Download the signed, notarized universal app for macOS 15 or later. Open the disk image and drag Vigil to Applications. Apple silicon and Intel executables are included.
Download Vigil 0.1.1 ↓ ZIP archive · SHA-256 checksums
Version 0.1.1 is a free developer preview. Choose Try fictional demo in the sidebar to explore without signing in. App Store availability is being prepared separately.
2. Connect your Vigil API
Open Vigil → Settings. Enter your team's HTTPS Vigil API address and the scoped API key provided by its operator, then choose Save & reconnect. The app stores this credential in macOS Keychain.
The API receives configured Sentry, Vercel runtime, AI Gateway and GitHub security sources. Its persistent service and MongoDB replica-set storage run separately from this marketing website. Source ingestion must be configured by the API operator.
If you do not have an endpoint or deployment access, contact the developer for setup access. A backend deployment is not provisioned when you download the Mac app.
3. Connect an MCP client, if you use one
MCP support requires Node.js 20.19 or later and the built Vigil MCP package. The archive includes the production dependencies; it contains no account credentials.
Get the MCP package
Download the production MCP package, then extract it locally:
tar -xzf vigil-mcp-0.1.0.tar.gz
cd vigil-mcpConnect through the Mac app
Leave Demo Mode before configuring MCP. In Vigil Settings, choose the extracted folder with Choose MCP Folder. You can return to Demo Mode after saving the folder; no live API is needed to share fictional app data. In MCP Hub → App data, start the private server and copy the generated router or Llama setup. Merge that definition with your existing configuration. Start and stop remain under your control.
Compatible MCP clients can read stored telemetry, cached TestFlight reports and loaded snapshots. The app-owned connection uses a private local socket and short-lived grants. Its tools do not provide production mutation actions.
Alternatively, connect directly to the API
For a standalone API-backed connection, run the same package with
VIGIL_API_URL and VIGIL_API_TOKEN supplied through your client
or approved secret broker. Keep credentials out of shared configuration and prompts.
4. Add TestFlight crashes, if you need them
Install the ASC App Store Connect CLI and sign in with an authorized profile through its own secure authentication flow. In Vigil Settings, select the ASC executable, profile names and numeric app IDs. Save TestFlight settings, then sync manually; automatic collection is an explicit option.
TestFlight reports are cached locally after collection. The app does not grant access to an Apple team by itself. Use only accounts and apps you are authorized to inspect.
What is available today?
The notarized Mac developer preview is available as a free direct download. This website does not offer managed Vigil hosting, a hosted account signup or App Store availability. The Mac App Store submission is being prepared separately.
Need a hand?
Contact support with your app version, macOS version and a description of the issue. Keep API keys and private telemetry out of your message.