Hundreds of Claude Code sessions. Thousands of file touches. Invisible patterns holding your codebase together. Tastematter reveals them.
Before AI coding tools, you typed every line. You knew what happened.
With Claude Code, you ship 10x faster — but the agent touches files you don't track, builds things you forget about, and your plan diverges from reality without anyone catching it.
The more agentic your workflow, the more invisible your context becomes.
It's there. It's holding everything together. You just can't see it.
Not what you think you're working on — what the data says. 47 touches across 12 sessions this week. That's where your attention actually went.
Your plan said API redesign. Your trails say 89% of work went to auth. The pivot happened Tuesday. Nobody noticed.
routes.ts was hot two weeks ago. Now it's cold. The migration hasn't been touched in 11 days. Work cooled off and nobody flagged it.
Every time you touch middleware.ts, you also touch jwt.ts. They're implicitly connected. Your agent should know that. Without trails, it doesn't.
You: What was I working on this week? Claude: Let me check your context trails... [runs: tastematter context "my-project"] Your trails show: HOT middleware.ts ##############...... 47 · 12 sessions HOT jwt.ts ##########.......... 31 · w/ middleware WARM auth.test.ts ######.............. 22 · 6 sessions COLD routes.ts ##.................. 3 · 8 days silent DRIFT Plan: "API redesign" -> Reality: 89% auth/ routes.ts abandoned since day 11 Continuing from middleware.ts?
One install. Background daemon indexes automatically. Your agent sees what you actually built — not just what the docs say you planned.
irm https://install.tastematter.dev/install.ps1 | iex
Requires Claude Code. Get Claude Code