AI browser agent privacy: a per-tab access checklist
AI browser agent privacy depends on more than a consent prompt. Use per-tab scope, action checkpoints, and a test plan before an agent touches signed-in web sessions.
Tag archive
Agent Security
7 articles connected to this topic.
MCP Apps for AI agents: keep interactive tools bounded and reviewable
MCP Apps give AI agents interactive dashboards, forms, and reviews inside chat. Learn how ticketed tools, bounded context, and sandboxed UI keep the workflow inspectable.
AI agent workspace terminals: a safer way to run parallel work
AI agent workspace terminals keep shell access, task state, and approvals close to the active job. Learn how to use guarded terminals without turning a chat UI into unchecked root access.
OpenClaw onboarding: set up a self-hosted agent with a verified model
OpenClaw onboarding verifies that a model can complete a real turn before it saves credentials or configures your workspace, Gateway, channels, and agents.
External agent: wake paths, security boundaries, and local control
An external agent can extend an AI platform without surrendering routing or trust. Learn how wake paths, local bridges, and CLI-owned credentials keep external agents usable.
Codex agent tool approvals: when coding agents should ask first
Codex agent tool approvals decide when a coding agent can run plugins, remote exec, or web search without turning every powerful action into a hidden risk.
AI agent message routing needs session identity, not just intent detection
AI agent message routing fails when identity, channel scope and session state drift. OpenClaw 2026.6.8 shows why durable routing context matters.