workscribe

Your work, automatically documented.

Workscribe runs quietly in the background, turns your terminal activity into structured work sessions, and writes your daily summary — offline, or in prose by the coding agent you already use. You just code.

See how it works↓

Node.js 22+ · macOS · Linux · No API key needed

terminal
$workscribe summary
## workscribe (main) — 3h 10m
  • - Committed: add weekly digest to the summary command
  • - Committed: fix project name resolution via git remote origin
  • - Resolved failing tests (4 runs, now passing)
  • - Worked with Claude Code (2 sessions)

Three steps. Then it just runs.

workscribe was designed to disappear into your workflow. Set it up once, then forget it exists until you need a summary.

1

Install & init

One command to install, one to set up. Installs the shell hook and offers the Workscribe skill to your coding agents — no AI provider or API key to configure.

terminal
$npm install -g @workscribe/cli && workscribe init
[1/5] Creating data directories
[2/5] Initialising database
[3/5] Installing shell hook
[4/5] Detecting AI coding tools
[5/5] Installing the Workscribe agent skill
2

Work normally

Every command you run is silently captured, redacted, and stored locally on your machine.

terminal
$git checkout -b feature/auth
Switched to new branch 'feature/auth'
$npm test
Tests: 42 passed, 42 total
$git commit -m "Add JWT middleware"
[feature/auth 3a2f1b8] Add JWT middleware
3

Get your summary

Run workscribe summary at any time. Sessions are grouped and summarised offline, then printed as markdown — or ask your coding agent to write it up.

terminal
$workscribe summary
## api-service (feature/auth) — 2h 15m
- Committed: Add JWT middleware
- Tests passing (1 run)

Built for developers who ship.

workscribe stays out of your way. No popups, no forms, no interruptions. Just quiet, automatic documentation that appears when you need it.

Privacy-first

Your data stays local

Summaries are built offline. Nothing about your activity leaves your machine unless you ask your coding agent to summarize it — telemetry is separate, anonymous, and opt-out-able.

Credential-safe

Secrets never hit disk

Tokens, API keys, and passwords are redacted before any event is written.

Agent-ready

Works with your coding agent

Claude Code, Codex, GitHub Copilot or Cursor can write your summary in prose through the Workscribe skill — no API key to set up.

Undo anything

Made a mistake?

workscribe undo removes the last captured event. --dry-run shows you what would be deleted first.

Weekly view

Week in review

workscribe summary --week tells each project since Monday branch by branch, with the days you worked on it. --by day lists it day by day.

Standup-ready

Post to Slack

workscribe summary --slack sends your summary straight to a configured webhook.

Everything in your terminal.

No browser tabs. No context switching. Just commands.

terminal
$workscribe summary
## api-service (feature/auth) — 2h 15m
  • - Committed: add JWT validation middleware
  • - Committed: fix token expiry check
  • - Resolved failing tests (9 runs, now passing)
  • - Added dependencies: bcrypt, jsonwebtoken
  • - Pushed to origin/feature/auth
## infrastructure — 45m
  • - Note: staging was flaky after the compose upgrade
  • - Builds passing (2 runs)

Capture work from your IDE.

Extensions for your favorite editors — so file saves, refactors, and test runs show up in your summary alongside terminal activity.

Live

VS Code

Does not import @vscode/extension-telemetry. Respects your VS Code telemetry setting.

Install from Marketplace →
Coming soon

JetBrains

Does not register with JetBrains telemetry service. No usage data collected.

Coming soon

Neovim

No telemetry infrastructure exists in this ecosystem.

Coming soon

Jupyter

No telemetry infrastructure exists in this ecosystem.

No telemetry of their own.

Every extension hands events straight to the Workscribe CLI you already installed — no separate phone-home, no separate analytics. Your activity data itself never leaves your machine unless you ask your coding agent to summarize it. The CLI does send one anonymous install ping (a random ID, version, platform — never your activity); opt out anytime withworkscribe config set telemetry.enabled false.

Your coding agent writes the prose.

workscribe summary builds your summary offline — no AI provider, no API key. For a written-up version, ask the coding agent you already use. The Workscribe skill reads your sessions, writes the summary, and saves it back.

Claude Code

Type /workscribe

Codex

Ask “summarize my work today”

GitHub Copilot

Ask “write my standup”

Cursor

Ask “what did I do this week?”

Install the skill into every coding agent Workscribe detects on your machine:

terminal
$workscribe skill install
✓ Installed the Workscribe skill for Claude Code (~/.claude/skills/workscribe)
✓ Installed the Workscribe skill for Codex and GitHub Copilot (~/.agents/skills/workscribe)
✓ Installed the Workscribe skill for Cursor (~/.cursor/skills/workscribe)
Restart any agent that is already open, then ask it to "summarize my work today" (or type /workscribe in Claude Code).

workscribe init offers this too. The template engine never sends anything off your machine; the skill sends the session data it reads to your agent's model provider. Privacy details

Start capturing in two minutes.

Node.js 22+, macOS or Linux.

terminal
$npm install -g @workscribe/cli
$workscribe init
✓ Ready to capture. Run `workscribe summary` anytime.