.webp)
.webp)
Agentic workflows are multi-step tasks delegated to AI agents that can reason, use tools, and take action toward a goal, rather than just answering a prompt. In security, that means workflows like confirming a vulnerability, choosing a safe fix, and opening a pull request. The quality of an agentic workflow depends on the context the agent can access: an agent with deep knowledge of application behavior and risk produces reliable results, while one working from raw findings alone produces guesses.
AURI Agents are pre-built, open source security agents from Endor Labs that run agentic workflows inside AI coding assistants like Claude Code, Cursor, and OpenAI Codex. Each agent packages a specific workflow, such as remediating vulnerable dependencies or triaging SAST findings, and is grounded in Endor Labs context including reachability analysis and upgrade impact data. Install them from the Agents Hub and invoke them in plain language.
AURI Agents run in Claude Code, Cursor, OpenAI Codex, and Google Antigravity, installed as a plugin from the associated marketplace. Teams running their own agent runtime can use portable, runtime-neutral agent bundles, and the Cursor SDK supports running workflows programmatically. One install covers all 11 agents in your host of choice.
No. Agents run inside your coding assistant, on your infrastructure, using your own LLM keys and source control credentials. Your code and secrets never cross into the Endor Labs boundary, and your token spend stays yours. Only telemetry flows back to the Agents Hub, so security teams get central visibility without the code ever leaving your environment.
Most agents in the catalog are read-only and cannot edit files, open pull requests, dismiss findings, or write policy on their own. The two agents that can change state, SCA Remediation and AI SAST Remediation, declare exactly what they're allowed to do and keep every mutating action behind a separate approval gate. All changes happen against your own git provider under your own credentials.
The MCP server gives your coding assistant access to raw Endor Labs data and scanning capabilities, and is intended to guide coding agents towards secure coding outcomes. AURI Agents package complete security workflows on top of that data: the prompt, the evidence requirements, the approval gates, and the output contract are already built. Use the MCP server for ad hoc scanning in your IDE, and use agents when you want a repeatable workflow like remediation or triage.
Yes. The open source Endor Labs Agent Kit defines every agent as a readable source recipe that declares what the agent does, which Endor Labs data it can touch, and what evidence it must produce. A builder compiles each recipe into artifacts for every supported host, and validators reject unsafe combinations before an agent ships. Keep your agents private, or contribute them back to the catalog.
AURI Agents are free and open source for Endor Labs customers. There's no new runtime to adopt, no new console to buy, and no per-seat pricing; agents use the LLM subscription your team already pays for. Agents require a specific Endor Labs product license (for example, SCA Remediation requires Endor Open Source).
