Building Teak in public: what I learned this year
Fourteen months of rebuilding sign-in, apps, AI and docs, and what working alongside AI coding agents taught me about proof.
Small Teak features most people never find
Keyboard shortcuts, search words, and quiet ways to save from anywhere that make Teak faster once you know they're there.
Shipping one product on web, iPhone, Android, Mac, browser extension and CLI from one monorepo
How one repository holds nine apps, keeps them on one version, and makes sure a feature lands everywhere at once.
You saved it, now what? Rediscovering ideas is the real work
Saving is the easy half. Here's how Teak helps you find, resurface and connect what you kept, months after you've forgotten it.
From a saved link to a searchable card: what happens after you hit save
A walk through the background work that turns a link into a card with a preview, tags, a summary, a saved copy and a place in search.
How to build a moodboard in Teak
Collect references from anywhere, let Teak describe them, then pull a board together by color, style and mood.
Self-hosting Teak: running your own knowledge hub
Teak is open source under the MIT license. Here's what it takes to run your own copy, and how to decide whether you should.
Let your AI agent read and write your Teak library with the CLI and MCP
Connect Claude, ChatGPT, Codex or Cursor to Teak in a minute, so your assistant can save what you find and search what you've kept.
Inside a release: how search by meaning went from idea to shipped
A feature promised as "coming soon" for almost ten months shipped in four days. Here's how I chose a model, built it, and fixed what broke.
Why I built Teak: a home for the ideas you'd otherwise lose
Design inspiration kept slipping through my fingers, so I built a calm place to keep it and a way to find it again.