BUILD RECORD 05Open source2026

OpenCode Annotate

Select an interface in the browser and route that exact feedback into the coding-agent session that owns it.

CreatorCreator · protocol, browser tooling, and package designPublished browser and agent-session workflow
PRIMARY EVIDENCE

The work, not a mockup.

OpenCode Annotate browser comment routed from a selected interface

OpenCode Annotate browser comment routed from a selected interface
product capture1280 × 800APPROVED PUBLIC MEDIA
ARCHITECTURE

WEB ↔ AI ↔ TOOLING

01WEB
02AI
03TOOLING
01 / OVERVIEW

What exists.

The browser captures selected elements, comments, routes, and optional screenshots while an OpenCode plugin delivers them to the correct active coding session.

02 / PROBLEM + CONSTRAINT

Where it resisted.

Interface feedback usually loses the selected element, current route, screenshot, and intended code session during handoff.

03 / INTERVENTION

What I changed.

I connected browser and agent through a session-aware WebSocket protocol with singleton coordination, queued annotations, and steer modes.

DIFFICULT DECISION

The obvious implementation was not the product.

Preserve the browser's evidence instead of asking a person to recreate visual context in prose.

Current proof

03
  1. One local relay coordinates several OpenCode processes.
  2. Element and box selection retain useful page context.
  3. Queue and steer modes preserve annotations across reconnects.
LESSONS

What this build changed.

Feedback becomes substantially more actionable when transport preserves where it came from and who owns the response.

BUILD MATERIALS

The implementation surface.

01Bun02TypeScript03WebSocket04OpenCode05html2canvas
Next build recordStackjet