docs(ecosystem): add opencode-chrome-annotation - #49478
eagleeyejack wants to merge 1 commit into
Conversation
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Potential Duplicate FoundPR #48955: docs(ecosystem): add opencode-chrome-annotation plugin This is the exact same plugin being added to the ecosystem plugins table. The current PR (#49478) appears to be a duplicate of PR #48955, which was already opened to add the opencode-chrome-annotation extension to the documentation. |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
Adds opencode-chrome-annotation to the Plugins table.
It connects a Chrome tab to a local OpenCode session from a side panel: you click an element on the live page, write what should change, and the agent receives the cropped screenshot, the element's exact selector/tag/role/ARIA metadata, and your instruction. Multiple annotations can be queued and sent in one go. Everything runs over 127.0.0.1 to the user's own OpenCode instance - nothing leaves the machine.
The agent side is an npm plugin (opencode-annotate - fork of JodusNodus's
opencode-chrome-annotation, renamed and published independently); the extension is GPL-3.0 and a credited fork. Not affiliated with the OpenCode team (note included in the READMEs).Distinction for review: @plannotator/opencode covers reviewing agent output (plans, diffs); this one annotates the live running UI, which nothing else in the table does today.
Demo: screen recording