Skip to content

RFC 0028: Browser Runtime & Render Pool #65

Description

@amiller

Implement rfcs/0028-browser-render-pool.md (now on main).

Problem: today oauth3/browser.ts drives ONE external CVM (login-with-everything) with a single global session — a non-owner who connects timeline-peek sees the owner's timeline (single-tenant wearing a multi-tenant costume), no isolation, no fairness.

Design: make the logged-in browser a first-class daemon runtime — a warm POOL of isolated browser containers; a browser-path read leases one, the requester's cookie jar is injected for that lease via the credential broker (RFC 0018), the browser is driven, the result returns, and the container is RESET before the next lease.

See the RFC's Design/Next-Steps sections. Depends on the broker (0018, landed) and the per-project container machinery (0009/0010).

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    p2Medium priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions