Glance Opencode

v0.1.1Other

@modemdev/glance-opencode

glance.sh plugin package for OpenCode

Actively maintained

#opencode #opencode-plugin #glance #screenshot #agent

GitHub repo npm page Homepage

GitHub stars

Monthly installs

6 in 7 days

Composite scoreSCORE

35.0

Multi-signal model

Last commit

1 month ago

2026-06-27

Install and configure

opencode.json

Writes to this project's opencode.json — applies to this repository only.

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@modemdev/glance-opencode@0.1.1"]
}

Writes to ~/.config/opencode/opencode.json — applies to every project.

~/.config/opencode/opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@modemdev/glance-opencode@0.1.1"]
}

opencode loads npm dependencies through its embedded runtime on startup and caches them locally — no manual global install needed.

README.md

View original→

Agent integrations for glance.sh — temporary image sharing for coding agents.

Paste a screenshot in your browser, your agent gets the URL instantly.

Available plugins

Agent	Directory	npm package	Install
pi	`pi/`	`@modemdev/glance-pi`	`pi install npm:@modemdev/glance-pi`
OpenCode	`opencode/`	`@modemdev/glance-opencode`	Add `"@modemdev/glance-opencode"` to `opencode.json` `plugin` list
Claude Code	`claude/`	`@modemdev/glance-claude`	`/plugin marketplace add modem-dev/glance-agent-plugins` then `/plugin install glance-claude@glance-agent-plugins`
Codex	`codex/`	`@modemdev/glance-codex`	`codex mcp add glance -- npx -y @modemdev/glance-codex`

How it works

Each plugin creates a live session on glance.sh, gives you a URL to open, and waits for you to paste an image. The image URL is returned to the agent over SSE — no manual copy-paste needed.

agent ──POST /api/session──▶ { id, url }
agent ──GET  /api/session/<id>/events──▶ SSE (waiting…)
user  ──opens /s/<id>, pastes image──▶ agent receives URL

Sessions are anonymous and ephemeral (10-minute TTL). Images expire after 30 minutes.

Packaging policy

New plugins should be published as installable packages (npm where possible) with a one-command install path in their README.

Each plugin directory should include:

Integration code
README.md with install / verify / update / remove steps
package.json (if the target agent supports package-based install)
Release automation (GitHub Actions workflow + documented version/tag convention)

Adding a new plugin

Create a directory for your agent (e.g. cursor/, cline/) with the files above and open a PR.

Sponsor

License

MIT