[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2st6vww3w7qnr":3},{"code":4,"message":5,"data":6,"timestamp":33},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":12,"age_days":13,"hn_threads":14,"one_liner":15,"summary_md":16,"topic":17,"github_topics":20,"license":29,"homepage":30,"updated_at":31,"history":32},"kitlangton\u002Fscrawl",11,"Show an agent a problem: mark up, record, send","Rust",728,72,10,[],"Turns a spoken, annotated screen recording into a structured bundle that coding agents can read.","Scrawl's premise is simple: when an agent gets stuck, showing it the bug beats typing a description. If you use coding agents and spend time re-explaining UI behavior, that premise alone may earn it a trial on a Mac.\n\n## The problem\n\nYou hit a bug in your app or a page you're building and need a coding agent to understand it. Typing out \"click here, then this happens, look at that weird spacing\" is slow and lossy, and screenshots lose the timing and narration. Scrawl changes the capture step: you press a shortcut, talk through the problem while clicking and drawing on screen, then press it again. The result is a bundle with annotated keyframes, a transcript and a structured timeline that an installed agent skill can read. The agent gets evidence rather than your reconstruction of it.\n\n## What's different\n\nInstead of dumping a video file into a chat, Scrawl packages the recording into artifacts designed for an agent: a contact sheet of annotated keyframes, full-resolution frames, a time-aligned transcript and interaction timeline in `summary.md`, and a `scrawl.json` manifest. Because the transcript and on-screen actions are time-aligned, an agent can connect \"the button jumps\" to the moment you clicked. A CLI exposes the same material — `inspect` for the summary or JSON, `frames --from\u002F--to` to pull frames from a time window so an agent can focus on one moment.\n\nScrawl also tries to shorten the routing step. A capture that ends on a browser showing a project's dev site can be sent straight to that project's OpenCode session, and `route --url` shows where a capture would go without sending it. Auto-crop is the other notable mechanism: record the whole screen and Scrawl infers where you were gesturing and crops each keyframe, rather than making you select an area first. The [README](https:\u002F\u002Fgithub.com\u002Fkitlangton\u002Fscrawl\u002Fblob\u002Fmain\u002FREADME.md) says crop settings were tuned on simulated captures with hand-labelled ideal crops — the author's account of tuning, not an independent accuracy test. Auto-crop is a heuristic, so unclear gestures or overlapping windows may not crop as you expect; the review window and the `autocrop` playground exist so you can check and adjust.\n\n## Who should try it\n\nIt fits developers who already work with Claude Code, OpenCode, Codex or similar agents and whose bugs are visual or interactive: layout breaks, hover states, flows that only fail after several clicks. It is a poor fit if you work primarily in a terminal or on backend issues where a written error output is clearer, or if you are not on a supported machine — the main build targets Apple silicon Macs on macOS 15+, with some features requiring macOS 26. There is a [Windows preview](https:\u002F\u002Fgithub.com\u002Fkitlangton\u002Fscrawl\u002Freleases\u002Flatest), but it is unsigned and does not self-update yet, so it is a different level of commitment.\n\n## Requirements and limitations\n\nMac users need an Apple silicon Mac and macOS 15 or later; live transcription and Liquid Glass need macOS 26. On first launch Scrawl walks through four screens, including every permission it needs, and won't continue until screen recording and the other grants are on. The Windows path is explicitly a preview, unsigned, so expect a SmartScreen warning and manual updates.\n\nThe agent workflow has its own upkeep. To let an agent read a bundle, you install a skill, and the `scrawl` command must be linked onto your PATH — the Homebrew cask does this, or Settings › Agents installs it. Automatic dev-site routing currently supports OpenCode sessions and a specific list of browsers. If a capture fails to deliver, the README says the original top-level destination field, not `context.session`, determines the recipient, and that you should check whether the capture already arrived before resending.\n\n## HotRepo's take\n\nHotRepo first tracked this repository on 2026-10-24, and its only stored board observation is #11 on the NEW-REPOSITORY board (新项目榜, Rust) on 2026-10-25 at 728 total stars. That is a dated snapshot of a 10-day-old project, not a daily growth curve, so persistence of interest cannot be judged from it. Before relying on it, verify that auto-crop handles your layouts and that your agent reads the bundle as intended by checking the contact sheet and `summary.md` from one real capture.",{"slug":18,"name":19},"developer-tools","Developer Tools",[21,22,23,18,24,25,26,27,28],"ai-agents","claude-code","coding-agents","gpui","macos","opencode","rust","screen-recording","MIT","https:\u002F\u002Fscrawl.kitlangton.com","2026-10-25T02:49:12Z",[],1792909472]