Projects

Projects sit beside the timeline, not instead of it. Use them when the same app can mean different work: a landing-page edit in Visual Studio Code, then a side project an hour later.

Create a personal project from the Projects tab. Give it a name and enough of a hint that classification can recognize it. Drifty then assigns captured blocks to that project using the same minimized activity it already uses for categories.

How matching works

Project matching is separate from live activity classification. The timeline still gets focus, neutral, or drift labels as usual. Projects assign those blocks to a named body of work.

Refresh covers the latest 7 days. Create at least one active project, then use Refresh latest 7 days. The matching model follows the AI route you already chose: Drifty Cloud, Local AI, OpenRouter, or a custom endpoint.

What stays local

Project names and assignments live with the local timeline. They are not a public report and they are not published to a leaderboard. Corrections and cost diagnostics stay in support controls.

If a block looks assigned to the wrong project, correct the underlying classification first. Later project refreshes follow that correction.

To inspect or delete the raw local record behind a project, use History.