---
title: "The Same Honest Answer Meant Something Different to Two Different Listeners"
canonical: https://dxdev.com/blog/2026-06-11_the-same-honest-answer-meant-something-different/
datePublished: 2026-06-11
---
# The Same Honest Answer Meant Something Different to Two Different Listeners

A small internal tool disappeared from ChatGPT the moment I described it honestly.

Nothing broke. The same tool kept working exactly the same way for claude.ai and for Manus, the other two assistants using it. Its only job was to create a brand-new file in one safe, boxed-in folder. It couldn't overwrite anything. It couldn't touch a file that already existed. It couldn't reach outside that one folder. It was capped at a small size. About as constrained as a tool can be while still doing something useful.

I had labeled it with the plain, technically accurate description for that kind of capability: it writes. That's true. It is also the exact same generic label you'd put on a tool that could delete a customer's entire account, because the label describes the category of action, not how narrow or safe a particular version of it actually is.

claude.ai and Manus both read that label as a hint and kept right on offering the tool. ChatGPT treated the identical, accurate label as an automatic reason to make the tool unavailable entirely, in chat and in voice, with no in-between option, no "ask me first," just gone. Same tool, same real behavior, same honest description, three completely different outcomes depending on which system was doing the interpreting.

That's an easy trap to fall into, because the instinct toward honesty says: use the same accurate label everywhere, don't make exceptions, don't play word games depending on who's listening. But a label is not a neutral fact sitting outside of interpretation. It's a signal, and different systems weigh the same signal completely differently. claude.ai and Manus treated "this can write" as useful context to keep in mind. ChatGPT treated it as an automatic disqualifier, with no way to say "yes, but only this much."

The fix wasn't to make the tool less safe, and it wasn't to build a second, separate version of it either. Every real constraint, the boxed-in folder, no overwriting, the size cap, stayed exactly the same, enforced the same way, for all three. What changed was one word, aimed at one listener: the tool started describing itself as read-only specifically to ChatGPT, while claude.ai and Manus kept seeing the plain, accurate "write" label, and the tool's actual behavior never moved an inch for any of the three.

## If you use the same warning or label across more than one audience

Find the one listener that reads your label the harshest, the approvals system that hard-blocks on a single word, the cautious client, the risk-averse reviewer, and check what happens to your capability the moment that listener sees your most technically accurate wording. If the answer is "it disappears entirely, with no partial mode," you don't need to loosen the real constraint to fix that. You need a second, still-honest word aimed at that one listener.

The tool's real limits, one new file, one folder, no overwrite, a 256 KB cap, never changed for claude.ai, Manus, or ChatGPT. The only thing that changed was the single word ChatGPT was shown next to it.