What's new
Every update to dagsec, newest first. The same list is on dagsec.net/changelog and in the dashboard under Settings. The desktop app installs updates on its own; the version shows which release brought a change.
Found a problem or have an idea? Send it from Settings → Report a problem in the dashboard or the desktop app. Our answer shows up next to your report.
A clearer Teams page
- The Teams page has tabs like the admin pages: Overview, Plans, Rules, Notes, Members, Areas and repositories, Audit log and Settings.
- Overview shows the team's numbers, your tasks, rules waiting for approval and what the rules stopped lately.
- Your role and your area sit above every tab, and the address keeps the tab, so links open the right one.
Plans: a team's work, done with its AI agents
- Teams can turn on plans: goals split into tasks with acceptance criteria, on a board of To do, Doing, In review and Done.
- Members take open tasks and move their own up to review; the owner and admins assign and approve.
- AI agents read the plan, take, add and update tasks through dagsec's MCP tools, and Claude Code starts each session with the user's tasks.
- A task is done when a pull request that names it (dagsec: #12) passes dagsec and is merged, never because an agent says so.
Teams, areas and rules for AI agents
- Anyone can start a team for free, with 5 seats; a team whose owner is on the Team plan has 10.
- You can be in up to 2 teams, and switch between them on the Teams page.
- Teams add their repositories, or a whole GitHub account, and their rules apply there. Members' other work follows their own settings.
- Owners can make members admins, who manage members, repositories and the policy.
- Areas split a team into sub-teams such as rover, boat and air defence. Each member works in one area at a time, and can switch it themselves when the owner allows.
- Teams write their own rules for AI agents: commands to stop, package versions to keep, code patterns and protected files, for the whole team or one area. Rules can be tried before saving, and copied to your other teams.
- Pull requests to a team's repositories are checked against its rules: protected files, code patterns in the added lines and package versions. A blocking rule fails the dagsec check.
- Teams write notes for the AI (boards, versions, wiring) that Claude Code starts each session with, members suggest rules for owners and admins to approve, and the weekly email counts what each team's rules stopped.
PHP packages, runtime versions and the forum
- Composer: dagsec now reads composer.lock and composer.json, checks PHP packages for known vulnerabilities, and stops risky `composer require` installs in AI agents and the terminal.
- Runtimes: dagsec reads the PHP, Node.js, Python, Go, Java and Ruby versions in Dockerfiles, .nvmrc, composer.json and similar files, and says when one has known vulnerabilities, misses a patch release or is no longer supported. A vulnerability attackers are exploiting now (CISA KEV) fails the check.
- Code Guard notices when your AI agent writes an outdated runtime into a Dockerfile or .nvmrc, such as `FROM php:8.2.10`, and asks it to use the patched release.
- The new forum at app.dagsec.net/forum lists every new critical or high vulnerability from OSV.dev, marks the ones attackers are using, and tells you if your scanned repositories are affected. Ask questions and discuss them there. It's on dagsec.net/forum too, and a critical vulnerability in a runtime like Node.js or PHP shows at the top of the home page.
- Searches like `grep "npm install"` are no longer mistaken for installs.
- Code Guard and the pre-commit hook apply your team's code and file rules on your computer, even with your own Code Guard turned off.
- Claude Code starts each session in a team's repository with the team's notes and rules.
Code Guard in every AI tool, a setup checklist and a weekly email
- Code Guard now also checks the code Codex, GitHub Copilot and Windsurf write. Codex and Copilot are asked to fix what it finds; Windsurf shows it to you, since Windsurf doesn't pass a hook's answer back to its agent.
- The desktop app opens with a short checklist: sign in, connect an AI tool, run Doctor. Each step ticks itself off.
- A weekly email sums up what dagsec caught and fixed for you. It only comes in weeks something happened, and you can turn it off in Settings.
Code Guard for Cursor, Gemini CLI and Cline
- Code Guard now checks the code Cursor, Gemini CLI and Cline write, not only Claude Code, and passes each problem and its fix back to the agent.
- Already connected? The Connections page shows Update; one click adds Code Guard and keeps your own hooks.
Code Guard fix for Windows line endings
- In files with Windows line endings, Code Guard could report problems that were already in the file as if the agent had just written them. Now only the lines the agent wrote are checked.
Code Guard: your AI's code, checked as it's written
- When Claude Code writes a file, dagsec checks the new lines for leaked secrets, memory leaks, SQL injection and security switched off, and asks Claude to fix what it finds.
- 38 rules across 12 languages, each with the code it flags and the fix. The check runs on your computer; your code never leaves it.
- A new Code Guard page shows what was caught and fixed, lets you choose between fixing and only telling you, and turns rules on or off.
The desktop app on Linux
- A .deb package for Debian, Ubuntu, Kali and other Debian-based Linux, with the tray icon, notifications and automatic updates.
- On Linux the session and API key are kept in ~/.config/dagsec, readable only by you, so they survive restarts.
What's new, and a place to report problems
- Every update is now listed in Settings, on dagsec.net/changelog and in the docs.
- Report a problem or suggest an idea from Settings. Our answer shows up next to your report, and you get a notification.
A plan in every scan report
- Scan reports open with a "What to do" plan, most urgent first, with commands to copy.
- The side menu can stay open, and the top bar stays in place while you scroll.
Much faster scans of large repositories
- Git history is read in parallel, so large repositories finish far sooner.
- A live progress bar shows each step of a scan.
- Local scans keep running when you leave the page or close the window.
Local scans for large repositories
- For a large repository, dagsec suggests a faster scan on your computer.
- The desktop app can clone the repository to a folder you choose and scan it right away.
A new side menu and quick navigation
- A side menu, and Ctrl+K to jump to any page.
- Pages switch instantly, with a light progress bar.
- Autopilot shows how to connect GitHub and which repositories it watches.
Autopilot on your computer
- Autopilot finds the git projects on your computer and analyses them (Team plan).
- A redesigned Autopilot page with a progress bar, the current step and filters.
Install checks in the terminal
- dagsec can check the packages you install from the terminal, in Command Prompt, PowerShell, Git Bash, zsh and bash.
The desktop app, now on macOS
- The dagsec desktop app for Windows and macOS: tray icon, desktop notifications and signed automatic updates.
- Remove from this computer undoes everything the app set up.