What makes AgentSight different technically?
It uses eBPF boundary tracing to observe LLM calls, file and network activity and tool calls, rather than relying on hooks inside the agent. It was published with an arXiv paper in August 2025.
AgentSight takes a different technical route to the same question: it uses eBPF boundary tracing to watch LLM calls, files, network and tool calls, and pairs with a companion enforcement component called ActPlane. It is free, open source and research-led. Beam works from agent hooks and normalised records instead, and adds pre-run skill and MCP scanning.
Details below are drawn from a September 2026 review of the AI agent security market. Some figures are vendor-sourced or analyst estimates, and this is a fast-moving space — check with each vendor before you buy.
| Beam | AgentSight (eunomia-bpf) | |
|---|---|---|
| What it is | Local-first activity monitor and pre-run scanner for AI coding agents. Early prototype. | Open-source research tool that traces agent behaviour at the kernel boundary with eBPF. |
| Monitoring | Shell commands, file changes, tool calls, network endpoints and browser actions from harnesses such as Claude Code, Codex and Cursor, normalised into local NDJSON with risk flags and evidence attached. | eBPF boundary tracing of LLM calls, file and network activity and tool calls, with prompt-injection detection. |
| Skill / MCP scanning | Yes. SKILL.md files and MCP configurations are scanned before you run them, using 11 heuristic patterns plus an MCP version-pin check. | Not covered in our source research. |
| Blocking / enforcement | No. Beam observes and flags. It never allows or denies an action. | A companion component, ActPlane, handles the enforcement side. |
| Individual use | Runs locally for one person on one machine. Shared teams, fleet rollout and approvals are not built yet. | Free for anyone; aimed at researchers and developers. |
| Deployment | A local collector plus a local interface. No MDM package, no central console, no SSO, no SOC 2, no SIEM forwarding. | Self-hosted, open source. |
| Source / licence | Not open source today. | Open source; published with an arXiv paper in August 2025. |
| Pricing | Not published. | Free. |
As reported in our source research. Some figures are estimates.
If kernel-level visibility matters to you and you are comfortable with a research-grade open-source tool, AgentSight is the more interesting technical approach. Beam is the easier thing to read a timeline in, but it is early and does not enforce anything.
It uses eBPF boundary tracing to observe LLM calls, file and network activity and tool calls, rather than relying on hooks inside the agent. It was published with an arXiv paper in August 2025.
Yes. It is open source and free, aimed at researchers and developers.
Enforcement is handled by a companion component called ActPlane. Beam has no enforcement component at all.
Beam is an early, local-first prototype. Read what it actually does today before comparing it further.