---
created: 2026-05-06
gap: G10
order: 1
severity: P1
category: docs
estimate: S
issue: "https://github.com/lidge-jun/agbrowse/issues/57"
depends_on: []
---

# G10 — Cloud-runtime positioning gap, not an implementation gap (vs Vercel/Browserbase/Browser Use Cloud)

> Severity **P1** · Category `docs` · Estimate **S** ·
> Tracking issue [#57](https://github.com/lidge-jun/agbrowse/issues/57) · Depends on **—**

## GPT Pro evidence

Evidence (competitor side): URL: https://github.com/vercel-labs/agent-browser — quote: “Browserbase session instead of launching a local browser.” Vercel also documents Browser Use cloud-session integration, while Browser Use markets a fully hosted cloud agent. 
GitHub
+1

Evidence (agbrowse side): README.md:347-352 marks hosted/cloud browser operation, remote external-CDP, broader MCP, and leaderboard claims as experimental/deferred; structure/phase_status.md:257-269 forbids hosted/cloud/external-CDP and benchmark-score claims. 
GitHub
+1

Why this matters: The market increasingly treats cloud browser infrastructure as table stakes, so agbrowse will look “behind” unless the non-goal is explicit. The right issue is positioning and claim enforcement, not adding cloud runtime.
Proposed scope, respecting forbidden list:

structure/comparison.md — add “local-CDP only” comparison against Browserbase, Browser Use Cloud, and Vercel provider flags.

structure/production_readiness.md — add deployment guidance for local/headed/CI use without remote CDP.

skills/browser/SKILL.md — add first-run note: no stealth, no CAPTCHA bypass, no hosted/cloud runtime.

web-ai/doctor.mjs — add --claim-audit checks for forbidden cloud/stealth/external-CDP phrasing.

bin/agbrowse — ensure --help includes “local CDP only” and points to comparison docs.

structure/release_gates.md — add gate:no-cloud-claims.
Test surface: test/unit.
cli-jaw mirror impact: parity required for claim text and skill-surface wording.
Acceptance gate: keep gate:truth-table-fresh; add gate:no-cloud-claims.
Estimate: S, 1 day.

## Diff-level work breakdown

> Fill in concrete diffs (NEW / MODIFY / DELETE with file:line) once this gap
> reaches the active sprint. Until then, the bullets in **Proposed scope**
> above are the agreed shape; do not implement before the depending gaps
> (—) ship and `gate:all` stays green.

### NEW files
- _to be filled before implementation_

### MODIFY
- _to be filled before implementation_

### DELETE
- _to be filled before implementation_

## Tests
- `test/unit/...` — _list test files once written_

## Truth-table update
- `structure/CAPABILITY_TRUTH_TABLE.md` — add row or update status when this
  gap reaches `ready` in agbrowse.
- `cli-jaw/structure/CAPABILITY_TRUTH_TABLE.md` — mirror entry per the
  `cli-jaw mirror impact` line above.

## Release gates touched
- Existing: `gate:typecheck`, `gate:tests`, `gate:truth-table-fresh`,
  `gate:mcp-scope-frozen`, `gate:no-experimental-in-readme-ready-section`.
- Added by this gap: see **Acceptance gate** in the GPT Pro evidence block.