Skip to content

Desktop app (Windows, macOS and Linux) ​

The dagsec app is the dashboard from app.dagsec.net plus the parts that only work on your own computer:

  • Connections: finds Claude Code, Cursor, Gemini CLI, Windsurf, GitHub Copilot, Cline, Codex, Kiro and Antigravity and connects them to dagsec in one click, without an API key in any settings file.
  • Local scan: scans a repository on this computer. Free on every plan; your code never leaves the machine.
  • Commit protection: a pre-commit hook that stops a commit adding a secret to code, offline.
  • Terminal (optional, off by default): a dagsec command, and a check on the installs you type in the terminal.
  • Notifications: a desktop notification when dagsec stops an install. The app waits in the tray (Windows, Linux) or menu bar (macOS) and updates itself.

Windows 10 and 11 (64-bit), macOS 11 or later on Apple Silicon and Intel Macs, and 64-bit Debian, Ubuntu, Kali and other Debian-based Linux (Ubuntu 22.04 or newer).

Install on Windows ​

  1. Download dagsec-setup.exe (about 11 MB) and run it. It installs for your user only; no administrator rights needed.
  2. If Windows SmartScreen says it protected your PC, choose More info, then Run anyway. The app isn't code-signed yet, so Windows doesn't recognise the publisher. Every release is published at github.com/hasanerman/dagsec-desktop.
  3. Open dagsec and choose Sign in with GitHub. Sign-in finishes in your browser and returns to the app; the session is kept in the Windows credential store.
  4. Optional: the terminal command and install check are off until you turn them on in Settings → Terminal.

Install on macOS ​

  1. Download dagsec.dmg, open it and drag dagsec to Applications. One app runs natively on both Apple Silicon and Intel.
  2. The app isn't notarized by Apple yet, so the first time macOS won't open it with a double-click. Right-click (or Control-click) dagsec in Applications and choose Open, then Open again. On macOS 15 and later, open it once, then go to System Settings → Privacy & Security and choose Open Anyway.
  3. Choose Sign in with GitHub. The session is kept in the macOS Keychain.
  4. Optional: the terminal command and install check are off until you turn them on in Settings → Terminal.

Keychain access

The API key for your tools is kept in the Keychain too. The first time a tool uses it, macOS may ask whether dagsec-hook may use the item "dagsec". Choose Always Allow, or installs are checked only while you answer. After an update macOS may ask once more.

Install on Linux ​

  1. Download dagsec_amd64.deb and install it. apt also installs what the app needs (WebKitGTK and the tray library):

    sh
    sudo apt install ./dagsec_amd64.deb
  2. Open dagsec from your applications menu and choose Sign in with GitHub.

  3. Not every Linux desktop has a keyring service, so the session and the API key are kept in ~/.config/dagsec, readable only by your user, the way gh and docker keep their tokens.

The tray icon needs a panel that shows tray (status notifier) icons; Xfce, KDE and Cinnamon do. On GNOME, install the AppIndicator and KStatusNotifierItem Support extension. Without one, opening dagsec from the applications menu brings its window back. Updates install with dpkg, so the app asks for your password when one is ready.

Connect your AI coding tools ​

Open Connections. The app lists each tool it finds:

StateMeaning
Not installedThe tool isn't set up for your Windows user
Not connectedInstalled; Connect adds dagsec
Old setup foundA hook with your key in the file, or the Claude Code plugin; Upgrade replaces it
Update availableConnected by an older app version; Upgrade adds what's new
ConnectedEvery install the agent runs is checked

Connect first shows every file it will change and the exact change, then waits for you. When you confirm:

  • Each file is backed up beside itself as <name>.dagsec-backup-<time> before it is written.
  • Only dagsec's own entries are added or removed; the rest of your settings stay as they are.
  • The first connection creates an API key named Desktop app (your computer's name) and keeps it in the Windows credential store or macOS Keychain. The tools' files point at the app's helper program, dagsec-hook.exe, which reads the key from there.

What each tool gets:

ToolInstall checkPackage lookups (MCP)Skill
Claude Code~/.claude/settings.json~/.claude.json~/.claude/skills/dagsec
Cursor~/.cursor/hooks.json~/.cursor/mcp.json
Gemini CLI~/.gemini/settings.json~/.gemini/settings.json
Windsurf~/.codeium/windsurf/hooks.json~/.codeium/windsurf/mcp_config.json
GitHub Copilot (CLI and VS Code)~/.copilot/hooks/dagsec.json~/.copilot/mcp-config.json, VS Code's mcp.json
Cline~/Documents/Cline/Hooks/PreToolUse (.ps1 on Windows)Cline's cline_mcp_settings.json
Codex~/.codex/hooks.json~/.codex/config.toml
Kiro(no hooks yet)~/.kiro/settings/mcp.json
Antigravity(no hooks yet)~/.gemini/config/mcp_config.json

Restart the tool after connecting so it reads the new settings. Cline runs hooks only after you turn on Enable Hooks in its settings. Connecting Codex also turns on its hooks (features.hooks = true in config.toml); the rest of the file, comments included, stays as it is. Kiro and Antigravity have no hooks dagsec can use yet: installs there aren't stopped, but the agent checks packages through the MCP server. Windsurf can't ask for confirmation, so in a team's warn mode it shows the finding and lets the install run. If you had installed the Claude Code plugin, connecting turns it off so installs aren't checked twice.

Doctor

Connections → Doctor → Run checks tests the server, your sign-in, the helper program, this computer's API key and the MCP server, without installing anything or writing to your audit log. If the key was revoked, Create a new key for this computer replaces it; the tools' files don't change.

Local scan ​

Local scan → Browse…, pick a folder with a .git directory, then Scan. The bar shows the step it's on: reading the git history, scoring dependencies, looking up vulnerabilities, checking whether leaked keys still work.

The result looks like a scan on app.dagsec.net, with the same checks. The difference is where it runs:

Local scanScan on app.dagsec.net
Where the code is readThis computerdagsec server, deleted after the scan
PlanFree on every plan, no quotaCounts against your plan
Private repositoriesAny repository you have checked outThe ones you grant the GitHub App
HistoryThe last 30, on this computer onlyIn your account

The scan asks package registries and OSV.dev about your dependencies, and GitHub, Stripe and Slack whether a leaked credential still works, the same as the command line. Nothing is sent to dagsec.

Autopilot ​

On the Team plan, Autopilot → This computer finds the git repositories in your usual code folders (or the ones you choose) and analyses each one daily and whenever it gets a new commit: leaked secrets, vulnerabilities and the version that fixes them, outdated packages. It shows the project it's working on and its progress, runs on this computer like the Local scan, and notifies you about new serious issues. The GitHub repositories tab watches the repositories you give the GitHub App. See Autopilot.

Commit protection ​

With a repository's folder in the Local scan box, Commit protection → Turn on installs a git pre-commit hook in that repository. Before each commit it scans only what you staged:

  • A secret added to code stops the commit, with the file and line.
  • A secret in tests, docs or examples is shown and let through, as in a scan.
  • If the check itself fails, the commit goes ahead with a warning.
text
  secret   config.py:1  AWS access key ID (AKIA********)

dagsec stopped this commit: it adds 1 secret(s) to code.
Move the value to an environment variable or a secrets manager, then stage the file again.
If it is not a real secret, commit once with: git commit --no-verify

If the repository already has a pre-commit hook, or sets core.hooksPath (husky, the pre-commit framework), the app won't overwrite it. It shows the one line to add to your existing hook instead.

Terminal ​

Both features are off by default. Turn them on in Settings → Terminal, then open a new terminal window.

The dagsec command adds a launcher to your PATH (%LOCALAPPDATA%\dagsec\bin on Windows, ~/.dagsec/bin on macOS and Linux):

bash
dagsec check npm lodash@4.17.4        # vulnerabilities, health and the version to use
dagsec check pypi requests==2.19.0
dagsec check maven org.apache.logging.log4j:log4j-core@2.14.1
dagsec scan .                         # the Local scan, on this computer
dagsec doctor                         # is this computer connected?

Ecosystems: npm, pypi, crates, go, maven, nuget, packagist. check and doctor use this computer's API key; scan runs entirely on your computer.

The install check asks dagsec before a package manager you type installs something: npm, pnpm, yarn, bun, pip, pipx, uv, poetry, pdm, pipenv, python -m pip, cargo, go, dotnet, nuget, composer require and mvn dependency:get. Other commands (npm run dev, python app.py) run as before, without a network call. A risky install shows the reason and asks:

text
dagsec: lodash@4.17.4 has 4 critical/high vulnerabilities. Install lodash@4.18.0 or later instead.

Install anyway? [y/N]

It works in Command Prompt, PowerShell and Git Bash on Windows, and in zsh and bash on macOS and Linux. For PowerShell and the others, dagsec adds a few lines to your shell profile between # >>> dagsec install check >>> markers; for Command Prompt, a doskey macro file loaded by Command Prompt's AutoRun setting (anything you already run there stays). Turning it off removes exactly those lines; the profile is backed up first. If PowerShell's execution policy is Restricted, PowerShell runs no profile scripts, so installs typed there aren't checked; the app tells you, and Set-ExecutionPolicy -Scope CurrentUser RemoteSigned changes it. Your team's install policy applies here too, and blocked installs appear in the audit log as Terminal.

Tray, notifications and updates ​

  • Closing the window keeps dagsec running: in the tray next to the clock on Windows and Linux, in the menu bar on macOS. Click the icon (or the Dock icon on a Mac) to open it again; Quit dagsec in its menu closes it.
  • When dagsec stops an install in one of your tools, or your team gets a notification, a desktop notification shows it within about 20 seconds.
  • dagsec checks for a new version when it starts and every six hours, and tells you when one is ready. Settings → Updates → Install and restart installs it. Every update is signed, and the app refuses one whose signature doesn't match. Your connections and commit protection stay as they are.

Uninstall ​

Windows: remove dagsec from Windows Settings → Apps → Installed apps.

Linux: in dagsec, open Settings → Remove dagsec from this computer → Remove and quit, then run sudo apt remove dagsec.

macOS: in dagsec, open Settings → Remove dagsec from this computer → Remove and quit, then drag dagsec from Applications to the Trash. (Deleting the app alone leaves your tools pointing at a program that is gone; they then let installs through unchecked.) The same button works on Windows if you want a clean slate without uninstalling.

Either way:

  • disconnects every connected tool (their settings files are backed up first),
  • removes the commit protection hooks the app installed,
  • removes the terminal command and install check, if you turned them on,
  • forgets the saved sign-in and API key.

The API key itself stays in your account until you revoke it on the API keys page.

Troubleshooting ​

The installer says it can't write dagsec-hook.exe. An older installer couldn't replace the helper while Claude Code or Cursor was using it. Current installers stop it first; with an old one, run taskkill /F /IM dagsec-hook.exe and choose Retry.

A tool isn't blocking after connecting. Restart the tool, then run the Doctor. Claude Code and Cursor read their settings only at start.

No notifications. On Windows, check Windows Settings → System → Notifications; on macOS, System Settings → Notifications → dagsec. Do not disturb or a Focus mode hides them too.

macOS says dagsec "is damaged" or "can't be opened". That's Gatekeeper refusing an app downloaded from the internet that Apple hasn't notarized. Use Open Anyway under System Settings → Privacy & Security. If it persists, run xattr -dr com.apple.quarantine /Applications/dagsec.app in Terminal once.