Who this is for
Developers deep in a hairy bug who keep losing track of which theories they've already eliminated.
The moment this saves you
I'm three hours into a bug, I've tried fifteen things, and I genuinely can't remember whether I already checked the cache, so I waste another twenty minutes re-testing a theory I'd already eliminated.
See it work
Messy spoken thought in. A clean, structured artifact out.
Debugging the login timeout bug. So far, I checked if it was the database, ran the query directly, it was fast, so it's not the DB. I thought it might be the auth service being slow but I added timing logs and auth returns in 50 milliseconds, so not that either. Current theory is it's the session store, the Redis calls look like they're hanging, I'm seeing connection timeouts in the logs intermittently. Next thing I'm going to try is checking the Redis connection pool config, I bet it's exhausted under load. If that's not it, I'll look at network between the app and Redis.
Debug log: login timeout bug
Ruled out
- Database, ran the query directly, fast. Not the DB.
- Auth service, added timing logs, returns in ~50ms. Not auth.
Current theory
- Session store (Redis). Calls appear to hang; intermittent connection timeouts in the logs.
Next to try
- Check the Redis connection pool config (suspect exhaustion under load)
- If not that: network between app and Redis
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to narrate a debugging session in progress, what I've tried and what I'm thinking. Turn it into a running debug log with bold sections: **Ruled out** (each theory I tested and the evidence that eliminated it), **Current theory** (what I now suspect and why), and **Next to try** (a numbered list of what I'll check next, in priority order). If I report finding the fix, add a **Fix** section. Keep my exact technical observations, timings, and log details. Don't invent results or eliminate a theory I only suspected. Output only the log.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One tap adds it to your clipboard. Open Contextli and paste to add it.
Next, open Contextli, Contexts, Import, paste.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
On-Call Incident Note
You just fought a fire at 2am and the postmortem is tomorrow, when half the timeline will be gone. Talk through what broke, what you did, and what fixed it, right now. You get a postmortem-ready note while the details are still sharp and real.
Product Bug Report
You just watched something break mid-demo. Don't lose the repro hunting for the tracker. Mutter what happened, what you clicked, what you expected, and walk away with a report engineering can actually act on.
Code Decision Log
Right after you make the call, while the tradeoffs are still fresh, talk through why you went this way and what you rejected. Three months from now when someone asks 'why a queue here?', the answer is already written down.