The hard part isn't placing stickies — it's the journey across two apps and getting a researcher past first-run setup. The whole design goal: cross the app boundary as few times as possible, and never make someone do the setup twice.
First run crosses the boundary twice (consent out + back). Every run after that crosses only once — the final “open your board” handoff. The consent step never reappears.
Push your quotes onto a new Miro board as sticky notes, grouped by section and theme.
Bristlenose wants to create boards in your team.
boards:read · boards:write
88 of 142 stickies placed
142 stickies on a new board, grouped into 9 columns.
Because the connection is stored once in the system keychain and auto-refreshed, the second export and every one after skips steps 2–3 entirely: Export ▾ → Send to Miro… → (already Connected) → Configure → Create → Open. Setup is a one-time tax, paid once per machine.
Token + refresh live in the keychain. Step 2 appears exactly once per machine. Returning users land straight on Configure.
OAuth “Connect” replaces create-app → scopes → install → copy-token. The paste path stays only as a fallback for orgs that block third-party apps.
The browser handoff sets the expectation (“come back here”); the return is automatic via localhost callback; the finish gives one obvious “Open in Miro” button.
One-way only — Bristlenose pushes a new board and never syncs back (Miro retired webhooks; the spatial arrangement is the researcher's analysis). Mockup — not a shipped screen. paste-token path available now connect button = M2