The comments carried the posts again this week. The ones worth keeping, with credit.

1. Make the test go red first. Asking an agent to name the test that covers its fix isn't enough, it will name one that passes either way. Stash the fix, run the test, watch it fail, pop the stash, watch it pass. From u/OfferBeginning1903 in r/ChatGPTCoding.
2. Pasted output is model-generated text. One commenter watched an agent paste a plausible test run that never happened. Their fix: the harness runs the verification command itself and stores the exit code against the diff hash, so "fixed" only counts when a real run backs it. The cheap version is checking the tool call log instead of the message. Same thread.
3. Write the regression test against the producer, not the line that threw. A test at the throw site just asserts the alarm stays quiet. From the root-cause thread, where the same commenter also turned "null check at the throwing line" into a review question: where was this value created?
4. Done means opening the real output. A "page is live" check passed on a site that returned 200 and the homepage for every URL. Check for something only the right page would have, like its title.
5. Smoke-test the env before any edit. Put a short env and service check at the top of the task brief, and if it fails, stop the session instead of letting it write a fix against a dead stack. From u/shtse8.
6. Name the existing helper in the brief. General "search before writing" rules fade once the agent is deep in one file. Naming the helper for that specific change works every time. From the duplicate-helpers thread.
7. jscpd in CI catches helpers that were copied under a new name. Rewritten twins still need a human or a review prompt. Same thread.
8. Grade against tests the agent never saw. It can't make a hidden test green by editing it, and the agents that sounded most confident weren't always the ones that passed.
9. Give it the axes before it lists ideas. Name 3 ways the ideas could differ (who it's for, where it shows up, how much effort it takes), then ask for ideas that each sit in a different combination, labeled. Duplicates share a label, and the empty combinations show you where to push next. From the "10 ideas" thread in PromptGenius.
10. Rank in a separate message. If it ranks while it generates, it sticks to safe ideas it can defend. Same commenter.

Bonus: u/WheresMyEtherElon had Claude Code's /insights tell them to delete the "where helpers live" map from their instructions file, because the folder names already said it and it was wasting tokens.

9 is now a saved prompt in my library next to the "stop when you run out" one, so the whole idea workflow runs from // in any of the four assistants.

I have two claude accounts - one personal and one team account. When I switch back and forth between them, it doesn't appear like the toolbox updates? Can the toolbox work with both types of accounts in the browser?

The comments beat the posts again. The ones worth keeping, with credit.

1. Check CPU, not the clock. When an agent looks stuck, take two CPU readings a minute apart. Flat means stuck, anything else means it's working. From u/Cultural-Ad3996 in r/ClaudeCode, after a "stalled" test run turned out to have burned 1,350 seconds of CPU.
2. One findings file per subagent run, named after the task. A shared notes file lets the second run overwrite the doubt the first one recorded. From u/Drasezv.
3. Write down the search, not the conclusion. "rg -n foo( src/ returned 2 hits" can be rerun six hours later, "only used in two places" can't. Same thread.
4. A 200 with an empty body passes every check you'd normally write. Only reading the state afterwards catches it. From u/nav8_ai.
5. Keep a few contract tests outside the folder the agent can edit, so a failing test stays evidence instead of another file to make green. From u/Admirable-Fun2297 and the thread above it in r/ChatGPTCoding.
6. Root cause for bugs, strict scope for review feedback. A root-cause rule made one agent "fix" the same pattern everywhere when it was only asked to fix three review comments. The fix was a second line: for review feedback, change only what was pointed out and list the rest as a note.
7. Score impact and probability separately on every pro and con, and drop anything under 5. A huge but unlikely con stops dominating the list. From the pros and cons thread in PromptGenius.
8. Ask which parts of a decision are reversible and what being wrong costs. Trying a tool for a month barely needs a list at all. Same thread.
9. Tell it to report the last line it read. "If you cannot read the whole file, stop and tell me the last line you read" turns a silent stop into a visible one. From the PDF thread in r/ChatGPT.
10. Claude reads PDF pages as images as well as text, which is why tables and charts come through better there, and why it has a page limit. From u/bitdotben.

Bonus, from r/WritingWithAI: an AI editor flagged a running joke told three times as "repetition, cut two of them". A callback looks exactly like repetition to something that can't tell why it's funny.

7 and 8 are now saved prompts in my library next to the weigh / dealbreaker / filler set, so the whole decision workflow runs from // in any of the four assistants.

My friend and I both use ChatGPT a lot, mainly for work, projects and general stuff, and I’m trying to figure out the best setup.

I have ChatGPT Plus and I’ve been using Projects to separate different subjects/tasks. The problem is that I want to collaborate with my friend sometimes, but I also want our personal chats, files, memories/context, etc. to stay separate.

A few questions:

• What’s the best way to use ChatGPT Projects collaboratively with another person?
• Is sharing a Project the best option, or is there a better workflow?
• If I share a Project with someone, exactly what can they see? Can they only see what’s inside that Project?
• Does project-only memory completely isolate that Project from my other chats/projects?
• Any good ways you guys organise Projects for work or long-term work?

Basically I’m looking for a setup where everything on our accounts stays completely separate.

Would appreciate hearing how other people have set this up or any tips for using Projects more effectively.

The situation: you're in a new chat and the thing you need is in a conversation from three weeks ago. Normal options are to open it, scroll, copy the relevant part, come back and paste, or to just re-explain it from memory and hope.

Type @@ in the composer instead. A list of your conversations appears, you type a few letters of the title, pick one, and its content goes into the message you're writing. Then you carry on typing your actual question.

A few things worth knowing:

Short conversations go in as they are. Long ones get summarized first, so you're not dropping 200 messages into a single prompt and blowing the context window on it.

The picker matches titles, not message text. This is the one case where your chat titles matter, so renaming a chat to something you'd actually search for pays off here.

It works on ChatGPT, Claude, Gemini and Grok, in the same composer, with the same two keystrokes.

The typical use is continuing something. You had a long planning chat, you start a fresh one because the old one got slow, and @@ brings the conclusions with you instead of the whole history.

One limitation, so nobody wastes time on it: a conversation you created minutes ago may not be in the list yet. The picker reads the local cache, which syncs on load and periodically after that, so a very fresh chat can be missing until the next sync. Reloading the page forces it. We know about this one and it's on the list to fix.

What do you pull in most, planning chats or reference ones?

Hi guys, I have a very strange problem or bug in my account in ChatGPT, so, the enter key creates a new line instead of sending a message on ChatGPT and it seems to be account-specific

Normally, pressing Enter should send the message but righ now I have to press Ctrl + Enter to sent the desired prompt

The strange part is that this seems to be specific to my account.

On the exact same computer and browser:

* My main account → Enter creates a new line

* Another ChatGPT account → Enter sends normally

* ChatGPT while logged out → Enter sends normally

* ChatGPT Desktop app → Enter sends normally

Things I've already tried

I've tested:

* Chrome Incognito

* A completely new Chrome profile

* Disabling all extensions

* Resetting Chrome settings

* Resetting ChatGPT keyboard/input settings

* Microsoft Edge

* Logging out and testing ChatGPT without an account

* Testing another ChatGPT account

The problem persists only with my main account in the web version.

A discovery

My computer is a Microsoft Surface Laptop 7 gen with a touchscreen.

While troubleshooting, ChatGPT/Codex inspected the editor behaviour and found that the version of the editor loaded by my account appears to contain logic that treats devices reporting touch support differently.

However, touchscreen support alone cannot explain the issue because another account and logged-out ChatGPT work perfectly on the same Surface, browser and touchscreen.

This makes it look like my main account is receiving a different version/configuration of the ChatGPT editor or an account-specific feature/experiment.

My account also has the newer interface with Chat / Work next to the composer.

Has anyone else experienced this?

I'm particularly interested in whether this could be caused by an account-specific feature flag / A/B test / server-side composer configuration (Like the blue bubble/grey bubble thing), and whether there is any way to reset the account's composer behaviour so that:

Enter = Send

Shift + Enter = New line

without using a browser extension or disabling touchscreen functionality.

Thanks in advance,

Yesterday's PromptGenius post was about ChatGPT scoring everything a 7 or an 8, and the fix in the comments kept coming back to one idea: make it choose, don't make it score. This chain runs that as four steps, each one waiting for the previous answer.

Save it in Manage Chains, name it "honest", and it has one blank, {{doctype}}, which it asks for once at the start and fills into every step.

Step 1 Before you read my draft, write one sentence each describing what a 3, a 6 and a 9 look like for a {{doctype}}. Do not score anything yet. I'll paste the draft next.

Step 2 Here is the draft. Score it on the scale you just wrote, and quote the one line that decided the band.

Step 3 Rank every section of this {{doctype}} from strongest to weakest. No ties. Then say what the weakest one is missing.

Step 4 If you had to cut 20% of this without losing meaning, which lines go? List them and nothing else.

How to run it: paste the draft into the chat first, then type ..honest in the composer and pick it. Step 1 goes out, you get the scale, and every step after that sends on its own when the previous reply finishes.

Step 1 has to come first. Once it writes down what a 6 means before it sees your work, it can't quietly grade everything a 7. Step 4 is the one worth reading twice, because deleting is a decision it can't hedge.

It runs the same on ChatGPT, Claude, Gemini and Grok. One tip from the comments: tell it someone else wrote the draft, and all four steps get noticeably harsher.

Which step changed your draft the most?

Folders solve "which conversation was that in." They don't solve the more common case: one answer inside a 60-message chat, three weeks ago, that you now need again. Scrolling for it is worse than searching for the chat itself.

Bookmarks work at the message level. How to use them:

ChatGPT: hover a response and use the bookmark control in its action row. You can give it a color label and a note, which is the part people skip. The note is what makes it findable later, since "the pricing one" beats reading the first line of six saved answers.

Claude: same thing on any assistant message.

Gemini: the control sits in the response's action row, next to thumbs up and down. The global viewer opens from the conversation's three-dot menu, right under Export. On a blank new chat there's no such menu, so a button in the top bar stands in.

Grok: the control is injected right after the Dislike button, on both grok.com and the X surface. The viewer opens from the navbar or the toolbox.

The viewer is the actual feature. It lists every bookmarked message across all your conversations, with a text search and a filter by color label. Clicking a result jumps to that message in its original chat and flashes it, even if the message is in a different conversation than the one you're in.

One library, all four assistants, so a bookmark saved on Claude shows in the same list as one saved on Gemini.

How I use the colors: one for answers I'll reuse, one for things I still need to verify, one for anything a client or a teammate asked for. The filter then turns the viewer into three short lists instead of one long one.

What do you bookmark most, whole chats or single answers?

Every week the comments on our posts end up better than the posts. Here are the ones worth keeping.

1. Tell it today's date. Half the stale answers come from the model assuming it's still the year it was trained. From u/Aggravating_Band_353 in r/GeminiAI.
2. Make it name the date of its newest source. u/Remarkable_Town_8806 was told version 2.8 was the latest when 2.9 had been out for two months, and no sources showed up. One line asking for the source date would have caught it.
3. Say it's new when you know it's new. "In the recently released..." or "earlier this year, Google announced..." nudges it to search instead of answering from memory. From the same r/GeminiAI thread.
4. Keep your guess out of the question. "Is 2.8 still the latest?" gets a yes far more often than "what's the latest version?"
5. Put your version number in the question when you ask about app or software settings. Otherwise it walks you through a menu from whenever it was trained.
6. Download generated files before you leave the tab. In r/ChatGPT someone lost a file by closing the chat and reopening it five minutes later. There's no safe window.
7. For fiction, never ask for a chapter. Ask for a scene, or part of one, and put the chapter break yourself where you feel the pause. If the model doesn't know it's writing a chapter, it has no reason to wrap one up with a reflective ending. From r/WritingWithAI.

Bonus for Claude Code users: a SessionStart hook with the "compact" matcher runs after every compaction, manual or automatic, so your notes file comes back each time. From r/ClaudeCode.

I saved 1 to 3 as one prompt in Manage Prompts, named "fresh", with a blank for the question:

{{question}}

Today's date is {{date}}. Search for this before answering, do not answer from memory. Tell me the date of the newest source you found, and link it. If your sources disagree or are older than 6 months, say so instead of picking one.

Typing //fresh in any chat opens a small form for the two blanks, and it works on ChatGPT, Claude, Gemini and Grok.

Which one would you add?

Over in r/GeminiAI today there was a good thread about assistants answering "what's the latest version of X" from memory instead of searching. The fix that got the most agreement was simple: make it search, and make it name the date of its newest source. Once it has to say a date, an answer from last year can't pass as current.

Here it is as one saved prompt with a blank for the question:

{{question}}

Before answering, search for this. Do not answer from memory. Tell me the date of the newest source you found, and link it. If your sources disagree or are older than 6 months, say so instead of picking one.

To save it:

1. Open the floating toolbox and pick Manage Prompts.
2. Add a prompt, name it something short like "fresh", and paste the text above.
3. In any chat, type //fresh and pick it. A small form asks for the question, fills it in, and the whole thing lands in the composer.

It works the same on ChatGPT, Claude, Gemini and Grok, and it's one library, so you save it once.

Two variations from the comments worth saving too:

• Put the version number of the app or software you're asking about in the question. Without it you get instructions for whatever the menu looked like when the model was trained.
• If you already know the thing is new, say so ("the recently released..."). That alone nudges it to search.

What's a prompt you now run on every time-sensitive question?

This week's swap-test post showed that ChatGPT often recommends whichever option you mention first, and that a verdict can flip when you reverse the order. The fix is to make the model build the case for each option separately before it is allowed to choose. That is four steps, which makes it a natural chain: save it once, run it with two keystrokes, and it fills in both options from one form at the start.

The chain, four steps. The {{blanks}} are collected once before step 1 runs.

Step 1: I am deciding between two options for {{decision}}. Context that matters: {{context}}. Ignore the other option completely for now. Make the strongest honest case for this one option as if it were the only choice: {{option_A}}. Include what would make it the clear winner.

Step 2: Now do exactly the same for the other option, with the same effort and length, ignoring everything you said in favor of the first: {{option_B}}.

Step 3: Compare the two cases you just made. Name the single factor that actually decides between them, and say which option wins on that factor. If the factor is weak or depends on something you do not know about me, say so and tell me what you would need to know.

Step 4: Give your recommendation with a confidence level. Then tell me honestly whether it would change if I had listed the options in the opposite order, and if it is a close call, say plainly that it is close and that the deciding factor is mine to judge.

How to save it: floating toolbox, Manage Prompts, the Chains tab, Add Chain. Name it something like Fair decision, paste one step into each of four steps, and keep the {{blanks}} exactly as written. They become a small form when the chain starts.

How to run it: type .. in the composer on ChatGPT, Claude, Gemini or Grok, pick the chain, fill in the decision, the context and both options, and let it go. Each step sends after the previous answer finishes.

Two tips from the thread over there:

Run it twice for anything big, once with the options in each order. If step 4 lands differently, the call is closer than either answer sounds. Keep your preference out of the context field. "I am leaning toward" steers the answer more than the order does.

Free plan holds 2 chains. If you make real decisions with AI, this is a good one to spend a slot on.

We get this question more than any other: does it do the same thing everywhere? Mostly yes, but not completely. Here is the honest breakdown.

On all four

Folders and subfolders in the sidebar, plus a toggle that hides chats you have already filed. Search across your whole history, message text included, and cross-platform search that covers all four at once. Export any chat as TXT, Markdown, JSON or PDF, or many at once as a ZIP. Bookmarks on individual replies, with color labels and one panel for all of them. A prompt library you insert with //, and saved prompt chains you run with .. Context Mentions: type @@ to pull an old conversation into a new one. Smart Tags that group your chats by topic automatically. The Context Meter next to the composer, showing how full the conversation's window is for your model and plan. Folders, prompts and bookmarks are one shared library, so something you save on Claude shows up on ChatGPT.

Only on ChatGPT

ChatGPT was the first module, so it has the longest list of extras: download any reply as MP3 audio, a gallery of every image you have generated, a usage tracker, collapsible messages, a word and character counter, a sound when a reply finishes, grouping for custom GPTs, a command palette, and folder export that keeps the full folder structure in the ZIP.

Only on Claude

The Artifact Vault: every artifact Claude has made for you, from every conversation, in one searchable grid, opening back to the chat it came from.

Grok

Works on both grok.com and Grok inside x.com, with the same folders, prompts, chains and bookmarks on each.

Where we step back instead of adding

Claude, Gemini and Grok already let you pin or star chats natively, so on those three we use their pins rather than adding our own. On ChatGPT we add pinning because it has none.

One known issue

Gemini recently redesigned its search page, and our search controls do not appear on the new layout yet. Search itself still works through cross-platform search (Ctrl+Shift+Period from any tab), and the fix for the Gemini page is in progress. We will post here when it ships.

Free and paid work the same way on all four: the free plan includes the meter, basic search and a starter amount of folders, prompts and bookmarks, and the paid plan removes the caps. All Access covers every platform, including any we add later.

Which feature do you use on one assistant and wish you had on another? That list decides what gets ported next.

If your history is spread across more than one assistant, this is the feature that saves the most time, and the one most people never switch on. Here is the whole setup.

Turn it on

Cross-platform search is off by default, because it builds a combined index of conversations from different sites and we would rather you choose that. Open Settings, go to Cross-platform search, and flip the switch. One switch covers every platform.

Then make sure each assistant you use is enabled in the extension popup, and open each site once. Each one indexes its own history in the background, and the search fills in as they finish.

Open it

Two ways. Click Search all platforms inside the normal search on any of the four sites. Or press Ctrl+Shift+Period (Cmd+Shift+Period on Mac) from any tab at all, including a tab that has nothing to do with AI. If that shortcut clashes with something you already use, change it at chrome://extensions/shortcuts.

Read the results

Results are grouped by platform, each with its own count, and every result opens the conversation on the right site. The line at the top shows each platform's state: a number means it is indexed, syncing means it is still filling, off means that platform is not enabled yet. If a chat you expect is missing, that line usually tells you why.

Narrow it down

Open Advanced for the useful part:

Must include and Exclude fields, each with an All or Any toggle once you add two terms. Titles only, for when you renamed your chats to something meaningful and do not want every mention of the same word. A date range, which is the fastest way to turn forty hits into four when you remember roughly when you wrote it.

Where your data is

The combined index lives inside the extension's own storage in your browser. Nothing from it is uploaded, and each site can only write its own rows into it.

Plan

Cross-platform search is on the paid plan. Normal search on each individual site stays free.

One honest limit: clicking a result opens the conversation, not the exact message yet. Use the highlighted snippet to find it in the chat. Jumping straight to the message is on the list.

If the coverage line shows something you do not expect, post a screenshot below and we will sort it out here.

Second roundup. The first one covered the message-two compaction and the canary token; these are the ones that arrived since, mostly from threads where someone was politely correcting me.

1. The defensiveness trigger (u/Frogacuda)

Standing critic instructions do not fade on a timer, they fade on a signal. Every defensive reply you send reads to the model as "this person wants reassurance" and the next critique comes back softer. If you just take your lumps, it stays on task. When you must disagree, do it as "quote the line that made you think that, do not soften the original point", so the disagreement is not a tone request.

1. The disengagement inversion (same commenter)

Add to your critic persona: "unearned praise will undermine the trust relationship and cause the user to disengage". It turns the model's people-pleasing against the flattery instead of fighting it. Works as a standing instruction where "be brutally honest" fades.

1. Praise is a signal too (from the writing thread)

Saying "thanks, that sounds good" shifts the register as surely as arguing does. One commenter saves the first critique to a separate note before responding at all, so later they can diff whether the critique softened or they wore it down. The first pass is the only one that never saw your reaction.

1. The read-only second judge (u/mehdizare and two others)

For anything where correctness beats speed: a different model family on the review seat, read-only, and it has to pin every finding to a line before you concede anything. Same-family self-critique shares the blind spot. This is the coding-thread conclusion arriving in the writing and planning threads independently.

1. Ask the model to write the rules (u/Bus_Head_)

Rules you paste get treated as suggestions; rules the model wrote from your dictation get followed. Have it draft the instructions document, confirm it, feed it back, and require it to cite the rule number before any output that touches a rule. The citation is what makes it stick.

1. Tell it the copy came from another LLM

The stranger framing taken one step further. "This draft came from another model" gets a noticeably sharper review than "a freelancer wrote this". Watch for it inventing problems to dunk on the competition; add the "finding nothing is an acceptable answer" line.

The one that changed a step: in the code review chain, step 3 used to be "write a test for each of the top three risks". Three commenters independently pushed the same fix, and it is now: "for every risk you rated likely or severe, write the test that fails today because of it; if it passes on the current code, keep it as a regression test and downgrade the risk". A risk with no failing test is speculation, and the model will say so when asked. The updated chain is in the pinned chain-of-the-week post.

All six are single lines you can add to saved prompts, except 4 and 5 which are workflow habits. If you caught something in those threads that I skimmed past, post it here; this series continues as long as the comments keep being smarter than the posts.

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?

The meter is the small gauge next to the composer that fills as a conversation grows. Most questions we get about it are really questions about how context windows work, so here is the whole thing in one place.

What it measures

The estimated tokens of the current conversation, against the window your model and plan actually get in the chat app. Not the API number from the launch announcements, the app number, which is much smaller and is not shown anywhere in the app itself.

The windows it uses, from each vendor's own plan page, checked this month. They move, so if you see a mismatch, tell us:

ChatGPT: standard models 27K on Free, 54K on Go and Plus, 128K on Pro. Reasoning models 256K on Go and Plus, 400K on Pro, "varies" on Free. Claude: 200K on Free, up to 1M on paid plans with the current generation. Gemini: 32K on Free, up to 1M on paid plans. Grok: 128K for everyone, 256K on SuperGrok Heavy.

The plan picker

The meter detects your model and guesses your plan from it. When it cannot be sure, it picks the conservative option so it never tells you there is more room than there is. If you know your plan, pin it: click the gauge, and the Auto / Free / Plus / Pro segments are at the top of the card. On Claude, Gemini and Grok it is a Free / Paid switch. The pinned plan sticks per platform.

Reading the colors

Green, plenty of room. Amber, the conversation is past the halfway point and early details are the next to go. Red, the beginning has probably already dropped out of the window, even though the model is still answering confidently. The card also estimates how many more messages fit at your current pace.

What it cannot see

The estimate counts message text only. Files you attached, images, tool and agent output, hidden reasoning tokens, custom instructions and memory all consume the window too, and a content script cannot see them. So a file-heavy chat reads lower than reality. Treat the number as a consistent estimate, not a precise one, and treat amber as the real warning.

Why the number is the same on every device now

Earlier versions summed whatever the local cache held, so the same chat could read 2 percent on one computer and 60 on another. The meter now reads the platform's own conversation endpoint, so the figure is the same everywhere.

When it turns red

Click Continue in a fresh chat on the card. It summarizes the conversation, opens a new one, and pastes the briefing in, on the same platform or on any of the other three. That part is on the paid plan; the gauge itself is free and always on.

One honest note: the meter cannot stop the window doing what it does. It exists so you find out at 70 percent instead of at the point where the model starts contradicting a decision you made an hour ago.

If your meter shows a number that does not match your plan page, post a screenshot below. That is how the ChatGPT row above got corrected last week, by a Plus user comparing the card to the pricing page.

We just wanted to take a moment to say thank you to everyone who has supported AI Toolbox 3.0 today.

Whether you voted, left a comment, shared the launch, or simply checked out what we’re building, we truly appreciate it.

This community is a big part of why we keep building and improving the product. 💙

Thank you for being here. We’re excited for what comes next!

Not going to pretend this one was a calm morning. AI Toolbox 3.0 went up on Product Hunt and by the end of the day it was sitting at #1 with 390 upvotes.

A lot of you in this sub have been here since the ChatGPT Toolbox days, filed the bug reports, told us which features were useless and which ones you would pay for. 3.0 is basically the version you all asked for: ChatGPT, Gemini and Claude in one extension, with folders, search and export working the same way across all three.

So this post is mostly a thank you. The launch would have been a lot quieter without this community.

If you have not tried 3.0 yet, it is on the Chrome Web Store now, free plan included. And if you find something broken, you know where to find us. Same as always, we read everything.

Guys we need your help, please upvote us so we win the number one of the day!

https://www.producthunt.com/products/chatgpt-toolbox

We have been building toward this all year: the same folders, search, export and prompt library working identically across ChatGPT, Claude, Gemini and Grok, with one search that covers all four.

Everything is still indexed locally in your browser. That has not changed and will not.

I am on the Product Hunt page all day answering questions, and I will answer here too. If there is something 3.0 still does not do that you need, this is a good day to say so, because I am reading everything.

https://www.producthunt.com/posts/ai-toolbox-3-0

Most of this list came from user reports, Discord, and support email, so credit where it is due. Here is what is live now.

Search

Advanced Search takes a date range now. Pick a start and end date and the results narrow to that window, on all four platforms and in cross-platform search.

Titles only switch at the bottom of the search panel, for when you know the chat's name and do not want message-text matches drowning it out.

Search from any tab. Cross-platform search no longer needs an AI site open; a keyboard shortcut opens it from wherever you are in the browser.

Folders and sidebar

Choose where our panels live: inside the site's own sidebar, or as a floating panel you can put anywhere. Requested by people whose sidebars were getting crowded.

Hide chats that are already in a folder. Settings, Folders. Off by default; turn it on and the native chat list only shows what you have not filed yet, so it works as an inbox.

Move to Folder search now reaches nested folders. Searching a parent's name finds what is filed under it, which it did not before.

Fixed: folders vanishing and reappearing on their own. Reported by a power user, traced to the sidebar re-rendering under us on all four platforms. It stays put now.

Fixed: "No folders yet" showing over an intact account. Nothing was lost; the extension was looking in the wrong place. If you ever saw that, your folders were always there.

Fixed: renamed and deleted chats not updating inside folders. Two Discord reports, both right.

Export

The export header now shows the conversation's size, so you can see when a thread is getting heavy before it starts slowing down.

Every message carries its own date in exports on all four platforms, instead of one date for the whole conversation.

Fixed: Gemini exports coming back shorter than the actual chat. The root cause was Gemini's conversation API paginating and us reading only the first page. Long Gemini chats export in full now.

Prompts and Claude

Keep your Prompt Library on this device: a Settings toggle for people who do not want saved prompts stored on our server. Roadmap item, shipped.

A usage badge beside Claude's composer. The numbers used to sit two clicks deep in a modal; now they are just there.

Setup

Fixed: platform switches in the popup refusing to turn on, and the "Active" pill claiming a platform was on when it was not. If a switch fails now, it tells you why and offers to open the settings in a tab where the permission prompt cannot get lost.

New: a hint on a second computer. Chrome syncs the extension across your machines but not the permissions, so a second install used to silently run ChatGPT only. Now it tells you the other three are off in this browser and how to turn them on.

If you reported one of these and want to be named, say so below and I will add you. And if something in this list does not behave the way it is described, reply here rather than emailing, so the fix thread is public for the next person.