Introducing Worktale: Your Dev Story, Told Beautifully

The problem

Most developers build in silence. Behind firewalls. Inside private repos. Under NDAs. Months of brilliant work—invisible. Even to you.

Six months from now, you won’t remember the race condition you debugged at 2 AM, the architecture you redesigned, or the migration that saved the sprint. When performance review season rolls around, you’re left scrambling through Jira tickets trying to reconstruct what you actually shipped.

“What did you ship this quarter?”
You: “Um… a lot of stuff. Let me check Jira.”

We built Worktale to fix this. It’s a CLI that reads your local git history and turns it into a personal record of what you actually built. One command. Zero setup. No code leaves your machine.

How it works

After init, a silent post-commit hook captures every commit automatically. Your dashboard updates in real-time with streaks, stats, and activity heatmaps. Run worktale digest at end of day to get a clean summary.

What’s in v1.0.10

• • worktale batch — bulk import all your repos at once. Scans recursively, imports history, installs nothing. Use --since 3m for fast scans.
• • worktale hook install/uninstall — granular control over which repos get live tracking. Add hooks to the repos you choose, remove them cleanly.
• • 13 CLI commands covering init, dashboard, today, status, log, digest, repos, batch, hook, config, capture, publish, and nudge.

Privacy by default

Worktale makes zero network requests. No account. No telemetry. Everything is stored in a local SQLite database on your machine. The only optional network call is if you use Ollama for AI-generated digests—and that’s localhost.

What’s next

Worktale Cloud is coming. Public developer profiles at worktale.dev, cross-repo timelines, weekly AI digests, standup generators, and email summaries. The CLI stays free and open source forever. Cloud will be the paid product.

---

Try it now:

GitHub · Docs · Follow on X