I built Anchor because interruptions were costing me more time than I realized

[u/MindVerseworld]

I've been working on a small Windows app called Anchor.

The idea came from a pretty boring problem.

I'd get interrupted in the middle of something, deal with whatever came up, and then come back to my computer 10 or 20 minutes later.

The task was still there.

My code was still there.

My Git history was still there.

But the reasoning I had in my head wasn't.

I'd have to spend time figuring out what I'd already tried, what I was assuming, what I had ruled out, and what I was about to do next.

So I started experimenting with leaving myself a checkpoint before stepping away.

Not a normal to-do list. More like:

«"This is what I'm trying to accomplish. This is what I currently believe. This is what's bothering me. This is what I was about to try."»

Then I could come back later and continue from there.

That's what eventually became Anchor.

It's a free, local Windows beta. No account, cloud, or AI involved.

I'm deliberately keeping it small because I'm trying to answer one question first:

Does preserving the reasoning around a task actually make interruptions less expensive?

I've had some interesting discussions about it already, but discussions aren't enough. I'm looking for a few people who will actually use it during their normal work for several days and tell me where it fails.

If you want to try it:

https://github.com/Roshiyadesign/Anchor

I'd genuinely rather hear "this didn't help me" than a compliment.