v0.9.0

bproxy 0.9.0 — Agent session ergonomics

Five features addressing friction points from real agentic sessions (~100 bproxy commands across 30–40 tasks). Closes #21.

New: tab activate

Foreground a tab explicitly before destructive actions. Eliminates the TAB_NOT_VISIBLE → screenshot → retry pattern.

bproxy tab activate -n agent -s <id>

New: links --href-contains

Filter links at extraction time. No more piping through python to match href patterns.

bproxy links -s <id> --href-contains "/company/" --limit 5

New: links --offset pagination

Paginate large link sets with offset. Response includes total count and capped flag so agents know how many pages remain.

bproxy links -s <id> --offset 50 --limit 50
# → { "links": [...], "total": 230, "capped": false }

New: text --after and --limit-chars

Extract text starting from a known marker. CLI-local post-processing — no protocol change.

bproxy text -s <id> --after "About" --limit-chars 1000
# → { "text": "...", "markerFound": true, "markerOffset": 142 }

Fix: response truncation

Large JSON responses (>64KB) no longer truncate when piped. Stdout writes use synchronous fd-level I/O to guarantee complete output regardless of consumer pipe state.

Breaking: protocol version 1 → 2

ActionResult["links"] gained required total: number field. PROTOCOL_VERSION is now a centralized constant in shared/src/version.ts. All protocol messages reference it via type — no more scattered protocol_version: 1 literals.

---

Internal

Context-grep Pi extension removed after A/B testing showed it reduces exploration breadth during planning, producing narrower implementations at the same cost. See docs/internal/journal/2026-06-22-context-grep-extension-ab-test.md for analysis.