Thread Notes: The Private Context Layer Your Inbox Was Always Missing
workcmd sticky notes let you attach a private, floating note to any email thread - draggable, colour-customisable, and visible only to you. Here's why that matters more than it sounds.
Email threads are a terrible place to store context about an email thread. The actual information - why this customer is upset, what was agreed on the last call, which version of the contract is current, who owns the next step - lives in Slack, in a Google Doc, in someone's calendar notes, or just in the head of the person who was on the call. workcmd thread notes create a direct line between that context and the inbox conversation where you actually need it.
How to add a note to a thread - step by step
Open any email thread in Gmail. Click the 📌 button that appears in the thread header. A sticky note floats over the thread - you can drag it anywhere on screen. Type whatever context belongs here: who you spoke to on the call, what was agreed, what the next step is. The note persists between sessions, attached to that specific conversation. It's local to your device, not visible to anyone else, and never transmitted anywhere. A yellow dot appears on that thread's inbox row so you can see at a glance which conversations have notes waiting.
What a sticky note actually is
It's a floating note that appears over any open Gmail thread, draggable to wherever on screen is out of your way. You click the pin button, type your context - 'client is waiting on legal to review, don't chase until Monday' or 'this is the person who asked about the enterprise plan on the call last Tuesday' - and it stays there, every time you open that conversation. A yellow dot marks the thread row in your inbox so you can see which conversations have notes before you open them. Nothing goes to any server. It's yours, on your device.
The handoff problem this solves
Email is terrible for handoffs partly because the thread contains everything that was said and nothing about what it means or what happens next. When someone else picks up the conversation - or when you come back to it after two weeks - the context is gone. A thread note turns a bare email chain into something with actual working memory attached to it.
What to put in notes versus what to put in replies
Put information in a note that you'd never put in the actual email. Internal pricing exceptions. Relationship history. Red flags. Your honest read of whether a deal is going well. The note from your Zoom call that explains why this client is genuinely difficult. This is the layer of context that usually lives in Slack DMs or in no-man's land - thread notes give it a permanent home next to the conversation it belongs to.
Colour the note and set a reminder from it
workcmd lets you customise a sticky note's background and text colour before saving, so notes serve as a quick visual status layer. More usefully, each note has a bell icon - tap it to set a timed reminder directly on that note. When the reminder fires, a red badge appears on the workcmd button and the Reminders tab so nothing goes unnoticed. This means you don't have to go to a separate reminders panel; the note and the follow-up schedule live together.
This works with GitHub and Google Docs threads too
When a GitHub code review comment gets forwarded to your email, or when Google Docs sends you a comment notification, those land as threads in Gmail. A thread note on that conversation can hold the context from the broader PR discussion or document conversation that the email excerpt doesn't carry. You stop losing the thread between platforms.
Make inbox cleanup repeatable
workcmd helps teams reduce recurring noise, keep local context, and move faster across the tabs where work already happens.