Agents
An agent in AI Agent Lens is one AgentShield installation: one machine, one user, one set of hooks. The Agents page is the fleet view.
Connecting a machine
agentshield login
login uses a device-code flow: it prints a short code, opens the browser, and links the installation to the organisation you are signed into. No long-lived secret is typed into a terminal. Afterwards:
agentshield status # hooks, MCP proxies, policy version, audit log location
agentshield ping # send a heartbeat now and confirm the connection
What the fleet view shows
| Column | Meaning |
|---|---|
| Status | Online if a heartbeat arrived recently; offline otherwise. |
| Hooks | Which agent integrations are registered on that machine (Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, OpenClaw, MCP proxy). |
| Policy | The rule pack version the machine is running. Machines pull new policy on their next heartbeat. |
| Mode | Enforce or audit-only, as resolved on that machine. Local configuration can override the organisation setting; when it does, you see it here. |
| Last seen | Time of the last heartbeat. |
Open an agent to see its recent decisions and the rules that fired on it.
Tamper protection
In managed mode the organisation can disallow disabling the hook. agentshield setup --disable and the AGENTSHIELD_BYPASS environment variable are both refused, and an attempt is recorded in the audit log. Standalone installs can always disable themselves; that is the point of open source.
Limits
Free organisations can connect up to 5 agents, Team up to 100, Enterprise without limit. See pricing.