Workscribe for VS CodeWorkscribe turns your terminal and editor activity into a daily work summary, written automatically — no manual logging, no end-of-day scramble to remember what you did. This extension captures what happens in the editor — file saves, debug sessions, build and test tasks — the activity pure terminal capture misses entirely. What it captures
None of this is sent anywhere by this extension. Every event is handed to the Last worked onWhen you open a file you last worked on more than a day ago, the status bar shows WS · 25 days ago. Point-of-need recall for "what was I doing here", without digging through git log. Files you worked on today show nothing: the point is surfacing context you've lost, not restating what you just did.
It asks the CLI again whenever you switch to a file or save it, so it never shows a stale answer. Workscribe tabThe Workscribe panel, next to Problems, Output and Terminal, shows the whole session the active file was last worked in: the repo, when it ran, its branch, how many events it had, and its full summary. With a CLI that works in threads (3.0 and later), it also shows how long the file's project was active, and lists every project worked alongside it, with when and for how long. With CLI 3.3.0 or later it adds Who changed this file, you and each coding agent with their changes and lines, and the full recap of each agent session that edited the file. Unlike the status bar item, it shows the latest session even if it was today. When there's nothing to show, it says why: Restricted Mode, the CLI not found, or no activity recorded for the file yet. Output channelOutput → Workscribe lists each event the extension sends to the CLI, one line each: when, what, and the file or folder. It reads "sent", because the CLI can still drop an event (a repeated save, or while capture is paused). Requirements
If the CLI can't be found, a Workspace TrustCapture is disabled in untrusted (Restricted Mode) workspaces, since it spawns subprocesses derived from files in the workspace. It starts automatically once you grant trust. Configuration
ContributingSee CONTRIBUTING.md for local development setup, testing, and packaging. (Not bundled in the published extension — LicenseMIT |