Docs: packaging plan gating + limits, non-pricing pages (packaging PR 8)

[ehfeng]

Important

Do not merge yet. This documents functionality that is not yet deployed. It merges only when the August '26 self-serve packaging changes ship, timed with the announcement.

Linear: KERNEL-1903 (parent: KERNEL-1507)

New plan state documented

• Free (Developer): profiles unlimited, managed auth with 3 connections and a 6-hour minimum health-check interval, file I/O (files persist only for the browser session), replays with 1-day retention, browser pools (size bounded by browser concurrency), 1 stored custom extension per org.
• Hobbyist: unchanged except extensions (1 stored per org) and pools now available; health-check minimum stays 1 hour.
• Start-Up: app invocation concurrency 50 → 150; unlimited stored extensions.
• Proxies and GPU remain Start-Up and Enterprise. Enterprise unchanged.

Extension limit semantics

Extension limits are on storage, not runtime:

• Stored custom extensions (enforced on POST /extensions): 1 per org on Developer (free) and Hobbyist, unlimited on Start-Up and Enterprise. Deleting a stored extension frees the slot.
• Loading extensions into a browser session is not plan-limited. A flat technical ceiling of 20 extensions per browser session applies to every plan.

Pages changed

• info/pricing.mdx — managed-infrastructure table (replays, profiles, managed auth profiles, file I/O, extensions, pools), concurrency table (app invocations 50 → 150, health-check interval Free 6h, new managed auth connections row, Stored custom extensions row at 1/1/Unlimited/Unlimited, and Extensions per browser session at 20 for all plans), managed auth billing copy, and the stale "browser pools are Start-Up and Enterprise" note.
• auth/connection-lifecycle.mdx — added a Developer (free) row at 6 hours to the cadence table.
• auth/configuration.mdx — health_check_interval description now links to the cadence table.
• auth/faq.mdx — managed auth is on every plan, 3 connections on free.
• reference/cli/managed-auth.mdx — both --health-check-interval flags note the plan-set effective minimum (range stays 300–86400).
• browsers/pools.mdx — replaced the plan-gated limitation with a concurrency-bounded one.
• browsers/replays.mdx — replays available on every plan, retention varies.
• browsers/extensions.mdx — callout in the upload section for the 1-stored-extension cap on Developer/Hobbyist; the "using extensions in a browser" note now states loading is not plan-limited (20 per session for everyone).
• integrations/vercel/eve-extension.mdx — manage_replays no longer says "requires a paid plan".

No changelog entry — that's added at announcement time.

Proxies copy finding

proxies/overview.mdx never states that proxies are Start-Up and Enterprise only. The only gating statement on that page is the bypass-hosts note (line ~315), which correctly says Start-Up and Enterprise. The only place proxy gating appears at all is the Configurable & BYO proxies row in info/pricing.mdx. So the copy isn't wrong, it's incomplete — a Developer or Hobbyist reader on /proxies/overview gets no signal that proxies are unavailable to them. Left unchanged per instructions; worth a follow-up ticket to add a plan callout to the proxies overview.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 5, 2026, 6:29 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Aug 5, 2026 8:45pm

[cursor]

Risk assessment: Very Low

Verdict: Approve

Summary

This PR updates plan gating and limits copy across public Mintlify docs only. The diff touches 9 .mdx files (+32/−16) with no application code, config, infra, auth/billing logic, or schema changes.

Evidence from the diff

Area	Assessment
Codepaths	Documentation pages only (info/pricing.mdx, auth/browser docs, CLI reference, Eve extension tool notes)
Blast radius	User-facing docs accuracy; no runtime or shared-service impact
Complexity	Table/copy updates and small clarifications (extension storage vs session load, free-tier health-check cadence)
Infra / security	None
Production logic	None

Why Very Low

Matches documentation-only criteria: small, easy-to-reason-about copy changes with no production behavior change. No CODEOWNERS file present; no prior approvals to re-evaluate.

Action

Approving per Very Low risk policy.

  

_{Sent by Cursor Automation: Assign PR reviewers}