Clarify your intention
Know what was decided, what's deferred, and what comes next. Every session builds on the last. temper your context.
Knowledge work deserves structure
Code is an expression of intent. So are specifications, plans, and decisions. But the context behind them — the why, the alternatives considered, the constraints that shaped the choice — scatters across conversations, documents, and memory.
Temper gives that context a home. Every goal, task, session, research thread, and decision lives as markdown with frontmatter in your vault. The frontmatter carries the throughline. The content carries the thinking.
Write markdown. Let temper do the rest.
The vocabulary of structured knowledge work
Every file in your vault has a doc type that temper understands. These aren't arbitrary tags — they're the building blocks of how work actually progresses.
The outcome you're working toward. Tasks and sessions roll up to goals.
Discrete units of work with mode (plan/build) and effort (small/medium/large).
What happened in a working session — decisions made, context discovered, next steps.
Investigation and analysis. Design explorations, comparisons, architectural options.
The choice, the alternatives, the constraints. Captured so you never re-litigate.
Domain knowledge. The vocabulary of your project that humans and agents share.
Context that's always ready to hand
Agentic tools like Claude Code and Cursor are powerful — but only when they have context. Temper gives agents the same throughline that humans carry in their heads: what we're building, why, what we've decided, and what's deferred.
Subscribe to contexts across projects. Everything arrives as markdown in your vault — no special tooling, no vendor lock-in. If it can read files, it can use temper.
Your vault, everywhere
Work on your laptop. Pick up on your desktop. Let a cloud agent contribute while you sleep. Temper Cloud syncs your vault across machines and team members with semantic search built in.