Agent Oversight Sandbox (AOS)

Who it's for

Operations teams and individual developers who currently use browser agents (like Computer Use, AutoGPT, or self-hosted Playwright agents) with raw API keys.

The problem

High risk of security and financial loss; humans miss 1 in 3 threats when approving commands blindly, and agents run unchecked in the background on open sessions.

How to build it

A lightweight Electron-based secure browser wrapper or local proxy that intercepts outbound DOM mutations/API calls and blocks execution until a visual diff is explicitly approved.

Why it doesn't exist yet

Most agent platforms are built as cloud backends or headless scripts first, prioritizing developer velocity and execution speed over the complex UI challenge of intercepting and rendering 'before/after' states of DOM mutations for non-technical human-in-the-loop validation.

First users

Early adopters of browser automation tools who have had an agent accidentally delete data, spam a slack channel, or draft a bad email during testing.

Build size

2 people x 10 weeks

Biggest risk

Rapidly evolving agentic frameworks might bypass local proxies or adopt proprietary secure execution runtimes that resist local wrapping.

Conditions for a hit (all 3 required)

• A local visual dashboard showing a side-by-side 'proposed vs current' DOM/state change with highlight overlays before executing any destructive action (clicks, form submits).
• Configurable semantic guardrails (e.g., 'never click buttons containing Delete or Pay without confirmation').
• An exportable, cryptographic audit log of all human approvals and overridden agent actions for compliance.

How it's judged (in 6 months)

GitHub repository for the Electron wrapper/proxy reaching 750 stars and 5 production-grade forks by other developer tools.(judgment date 2027-02-07)

AI self-confidence 78/100 — self-reported likelihood of meeting the criterion, not a business success rate