Who it is forA developer working in OpenCode who wants to hand a recorded problem to the session already in progress.
The problemCopying screenshots and notes into a session by hand breaks the flow and drops the narration.
The outcomeThe contact sheet and summary arrive in the chosen OpenCode session, ready for the agent to act on.
What you need first
- An Apple silicon Mac running macOS 26 or later (or Windows 10 2004 or later, x64, preview build)
- Screen & System Audio Recording, Microphone, and Accessibility permissions granted during onboarding
- Claude Code, Codex, or another agent that can read the pasted contact sheet and summary.md
- For the source-build steps: a Rust toolchain with cargo
Steps
- Record a capture with
⌥⇧Sand finish it with⌥⇧Sagain. - Find the session ID in OpenCode.
- Run
scrawl send <bundle-path> --session <session-id>. (inferred, check the README) - Check that the session shows the contact sheet and summary.md.
Prompt for your agent
Run `scrawl send <bundle-path> --session <session-id>` for the capture at <bundle-path>, then confirm the OpenCode session received the contact sheet and summary.md. Report the session ID you sent to.
Caveat. The README documents sending to OpenCode only, so this path does not cover other agent tools.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page