Stopped writing code? We noticed.

Scry is a read-first, integrated review environment.

Learn more

Your IDE is designed for old habits.

It was designed for editing: crawling through lines of text, changing characters one keystroke at a time. Reading was always an afterthought. After all, monospaced text is legible, isn’t it?

Review the change.

Commits and diffs are reading too. Open any change in a Git or jj stack as a page, with the reasoning written above the diff.

Annotate while your agent works.

Mark up any line the way you would in a pull request. Scry plugs in as an MCP server, so the agent picks up your notes in real time and revises as it goes.

Read between the commits.

Trace a line back to the agent conversation that wrote it, then replay the edits in between. It needs operation-level history to work, like Zed’s DeltaDB.

Browse the codebase instead of managing files. A component, its test, its stories and its styles share one page, and following a name shows you what calls it.

Code that reads like a wiki.

Headings get bigger type, names go bold, and a diagram can sit right next to the function it explains.

Docs, tickets, threads and meeting notes, beside the code.

Keep your context with your code. The spec you’re building from, the ticket in progress, the chat that’s still going, this morning’s notes, all open beside the lines they’re about.

Read first. Edit when you must.

A quick fix is a key away. Everything else about the screen is built for reading; debugging and the terminal stay in your editor.

Questions

A reader for the code you won’t write.

Join the waitlist for early access to test builds.

Test builds and Scry news only. Unsubscribe anytime. Privacy

Not convinced? Tell us why