Lesson 1.1
Why Worktale exists.
WHAT YOU'LL LEARN
The problem Worktale solves, so the rest of the course makes sense. No setup yet — just the shape of the thing.
Most serious software gets built inside private repos. Under NDAs. Behind firewalls. At clients. At employers. When the engagement ends or you move on, the record doesn't come with you — and six months later you can't reconstruct what you shipped.
The same thing is happening with your AI spend. You're burning real money on Claude, GPT, and Copilot, split across four different agents and however many projects, and the only record is your monthly invoice.
Worktale is a personal, local-first record of what you built, what it cost, and why. It stays on your machine and moves with you when you change jobs.
What it actually is
- A CLI tool you install once with
npm install -g worktale - A local SQLite database at
~/.worktale/data.dbthat only you can read - Silent git hooks that snapshot every commit's metadata (never contents)
- A TUI dashboard (
worktale) and an optional desktop app - An opt-in cloud profile at
worktale.dev/{username}you control
What it is not
- Not a surveillance tool. It has no team view. No manager can see your data.
- Not a time tracker. It doesn't watch keystrokes or track mouse movement.
- Not SaaS. Everything runs locally. The cloud is optional and opt-in.
- Not reading your source. Only git metadata: commit hashes, messages, diff stats.
KEY INSIGHT
Your Worktale data lives at ~/.worktale/data.db — outside any repo, on your own machine. If you lose access to a company's repos, your record of what you shipped stays with you. That's the whole point.