Description
## Problem
We replaced Browserbase ($20/mo) with PinchTab for browser automation on neoremote. This works well for Claude Code — we created a `pinchtab` skill that lets Claude navigate pages, take accessibility tree snapshots, click elements, type text, etc. via the PinchTab CLI.
However, nims in the NimsForest ecosystem currently have no way to use browser automation. The capability only exists as a local CLI skill for Claude Code on neoremote.
## What we have today
**PinchTab skill for Claude Code** (`~/.claude/skills/pinchtab/SKILL.md`):
- `pinchtab nav <url>` — navigate to URL
- `pinchtab snap -c` — compact accessibility tree snapshot with element refs (e0, e1, e2...)
- `pinchtab snap -i` — interactive elements only
- `pinchtab click <ref>` — click element by ref
- `pinchtab type <ref> <text>` — type into element
- `pinchtab text` — extract readable page text
- `pinchtab screenshot` — visual screenshot
**PinchTab daemon on neoremote:**
- Systemd user service running PinchTab v0.8.5
- HTTP API on `http://127.0.0.1:9867`
- Headless Chrome via snap Chromium with `--no-sandbox` wrapper
## What we need
Nims should be able to perform the same browser automation tasks (navigate, snapshot, click, type) through NATS Wind, so any nim can do web validation, data extraction, or page interaction as part of its workflow.
Nebula's reasoning: This is an infrastructure capability expansion — nims can't do browser automation yet, but nothing is broken or blocking users today. Medium priority reflects its value as a foundational enabler without urgency. Project changed to nimsforestpinchtab since that repo is the existing songbird-only PinchTab connector and is the natural home for expanding NATS Wind integration for nim-level browser automation.