popagent

public
Latest change 98a9a832366ede73ff5e61d826d68af4f775db92 - Add safe autonomous deployment and complete project guidance by AkurAI Build
---
name: popagent-browser-security
description: Change or review popagent browser policy, sessions, capabilities, profiles, recordings, screencast, takeover, or browser APIs without weakening SSRF, credential, and access-class boundaries.
---

# Popagent browser security

Read `../../../AGENTS_BROWSER.md`, `../../../AGENTS_AGENT.md`, and `../../../AGENTS_RULES.md`. Read `../../../AGENTS_UI.md` for browser panel or settings changes and use the UI-verification skill after the final edit.

1. Locate the owning policy/session/profile/recording contract before editing and observe the narrow regression fail first.
2. Preserve checks across direct navigation, redirects, clicks, history, new tabs, DNS resolution, private addresses, and rebinding. Authentication state never bypasses host policy.
3. Preserve `interactive`, `read-only`, and `none` capability separation. Takeover must be explicit, bounded, authenticated, and disabled when hidden.
4. Keep profile plaintext temporary and mode-restricted; APIs return metadata only. Keep recordings path-contained, bounded, ignored by Git, and treated as sensitive.
5. Preserve thread/task cleanup, abort propagation, concurrency, idle limits, and hook visibility.
6. Run the narrow browser contracts, affected route/UI tests, `bunx tsc --noEmit`, and the final full suite. Perform desktop/mobile browser verification for UI-visible changes.
7. Update `../../../AGENTS_BROWSER.md` and any affected UI/backend domain file in the same change; remove superseded facts.

Do not add remote or hosted browser providers until one is explicitly selected.