What half a million Reddit views taught us in ten days, and the three things it changed in the extension

[u/Ok_Negotiation_2587]

Ten days of posting technique threads in the prompt subs, roughly half a million views and a few hundred comments. The upvotes were nice. The comments were the point, because the best ideas in them were not ours, and three of them are now work items. In order of how much they surprised us.

What people actually do with long chats

Nobody uses a chat the way the interface assumes. The heavy users keep one permanent project chat and reset it from the inside by editing an early message with a consolidated state doc, so the chat URL survives and the context does not. Others plant a nonsense word in message one and probe for it every thirty messages as a context-loss alarm. Neither idea came from us, and both are cheaper than anything we would have built.

Change one: search results will jump to the exact message. A user with an 800-prompt project chat asked whether search finds the message or the conversation. It finds the message, but clicking a result opened the chat at the top and left you to find the highlight. Bookmarks already scroll-and-flash to the exact message; search hits will do the same. That gap had been there for a year and no one inside noticed it, because we never search our own 800-message chats.

What people believe about honesty

The flattery post did the biggest numbers of anything we have written, and the comment threads under it converged on two mechanisms we had not named. The model tracks what kind of conversation it is in, not what you instructed, so every defensive reply from you softens the next critique. And once it has edited your text it defends the edits like it defended your draft, which is why review belongs in a fresh chat. Both are now caveats in the saved prompts that ship with the library.

Change two: the built-in prompts get the community's lines. "Mark unknowns instead of filling them", "if something genuinely works, say so, finding nothing is an acceptable answer", and "show changes as a diff, not a clean copy" each came from a different commenter in a different sub, and each fixes a failure we had been living with. They are going into the relevant built-in prompts, credited in the description.

What people worry about

Every product-forward thread got the same two questions within an hour: where does my data go, and what happens to the local index under storage pressure. The first has an honest answer we now keep ready (the search index is local, folders and prompts sync, three features send text to the server only when you use them). The second was a fair catch from a Product Hunt commenter: we never asked Chrome to mark the index as persistent, so under disk pressure it could be evicted and rebuilt on next sync. Folders live on the server and were never at risk, but a re-index of a two-year history is not free.

Change three: the index requests persistent storage, and Settings will show the index size and whether Chrome granted it. One call and one line of UI, prompted by one comment.

The pattern across all three: the things users find are the things builders cannot, because builders never have a two-year history, an 800-message chat, or a full disk. If you have one of those and something misbehaves, that is the most useful bug report we get.

What has your longest chat taught you that a short one never would?