yester<dev> captures the work behind the work — investigations, debugging sessions, code decisions, screenshots, recordings, links, and notes — without breaking your focus. Then it turns those moments into a clean, publishable report.
Local-first · No account required · Free during beta
You investigate bugs, compare behavior, test theories, read logs, collect screenshots, inspect code, and make decisions all day long.
By the time the report is due, the evidence is scattered across browser tabs, chat messages, screenshots, commits — and memory.
The result: reports that are either too thin to be useful, or too expensive to write well.
A tray-first workflow with global hotkeys. Every capture is timestamped, tagged, linked to the source app, and appended to your session log — automatically.
Name the activity you're working on. yester<dev> keeps a folder and timeline for it.
Screenshots and screen recordings ⌃⇧S, notes ⌃⇧N, code ⌃⇧D, and links ⌃⇧L.
Add quick notes and tags in seconds, while the context still exists.
Select and order captures across Sessions to build one clear publishing list.
Review the report in your browser, then publish to HTML, Confluence, Notion, or Slack.
Global hotkeys capture the current state of work without opening a heavy tool or stopping your investigation.
Every capture lands in the session log with a timestamp, source app, tags, notes, and media references.
Tags turn scattered capture moments into a navigable work trail. Create a missing tag right from the capture dialog.
Screenshots, recordings, snippets, links, and notes live in one report — the outcome and the path that led there.
Export clean HTML, push directly to Confluence Cloud or Notion, or send the report into a Slack thread.
Session post-its stay local and are deliberately excluded from every exported report.
Take notes directly on the video you captured. Draw on the frame, write on the frame, and pin every mark to the exact seconds where it matters. yester<dev> renders an annotated copy with your marks burned in — no video editor required.
Circle the broken layout, arrow the suspicious value, underline the log line — freehand pen with your choice of color and stroke width.
Drop text labels right where the explanation belongs. Click any label to edit it later.
Each mark has a start and end pin, so annotations appear exactly when they're relevant — then yester<dev> burns them into a shareable annotated copy.
Turn a work session into a structured update: what was done, what was found, what remains open.
Reproduction steps, screenshots, recordings, code findings, and hypotheses — in one timeline.
Polished, evidence-based reports that show effort, progress, decisions, and next steps.
Package the context another developer needs to continue the work — without a long meeting.
Publish to Confluence, Notion, or Slack so teammates review the evidence without interrupting you.
Document how a new codebase works while exploring it, so the understanding is reusable later.
Everything is stored on your machine in plain Markdown and media files. No account, no cloud lock-in.
Nothing leaves your machine without an explicit publish action. yester<dev> opens a browser preview first and waits for you.
Sticky notes for your raw thinking live next to the session — and never appear in any exported report.
yester<dev> makes daily reporting a natural side effect of doing the work. Free during the beta.