A manual rename only lasts until the page next changes its own title. ChatGPT and Claude both rewrite the tab title as you use them, and Docognito is built to keep reasserting the disguise instead of setting it once. A console trick or bookmarklet has no way to react the next time the page changes the title back.
What a manual rename actually does
The trick itself is simple enough. Open the browser console, or click a
saved bookmarklet, and run a line that sets document.title to something
else. For a second, the tab reads whatever you typed. Some versions go
further and swap the <link rel="icon"> element for a different image too.
Both of those are one-time writes. They change a value that exists in the page right now, and they stop there. Nothing about the script keeps running after it finishes, and nothing about it notices what the page does next.
Why the page wins the rematch
ChatGPT and Claude both set their own tab title, and they do it more than once. A new conversation gets a title once the first reply streams in. An existing conversation gets retitled if you rename it from the sidebar. Even mid-reply, some builds touch the title to reflect a loading state and then revert it once the answer finishes. Each of those is the site's own code writing to the same property your one-off script touched a minute earlier, and the site's code keeps running for as long as the tab is open.
A manual edit has no way to contest that. It ran, it finished, and it is not watching. The very first title change the page makes after your script runs puts the real name straight back, usually within seconds, and often before you have looked away.
| What people try | What actually happens |
|---|---|
| Set document.title once from the console | Reverts the next time the page sets its own title, often within seconds |
| A bookmarklet that also swaps the favicon | Same problem: a single write, no way to react to the site's next update |
| Rename the tab from a browser tab-grouping feature | Renames the group label, not the tab itself; the real title still shows |
| A continuously running extension that reasserts both | Keeps winning, because it reacts every time the page tries to change them back |
The row that separates a trick from a tool is the last one. Reacting once is not the same job as reacting every time, and only the fourth approach is built to do the second.
How Docognito wins the same fight continuously
Docognito does the same two writes a bookmarklet does, a new tab title and a new favicon, but it does them from inside a script that runs for the whole time the tab is open, watching for the moment the page tries to overwrite either one. The result is the browser tab title and the tab icon, held in place for as long as the disguise stays on, not for one instant after you clicked something.
The part that actually wins the race is timing, not persistence alone. The script that reasserts the title runs in the tab before either ChatGPT's or Claude's own code runs at all, at the earliest moment the browser allows a script to act on a page, so it never has to catch up to a title the site already set. Rather than waiting for the site to rename the tab and then racing to overwrite that, it replaces how the tab's title behaves in the first place, so a write coming from the page itself does not stick unless the disguise allows it, backed by a second check that keeps watching in case the visible title changes through some other route. A console command or a bookmarklet runs after the page, as a guest inside it. This runs ahead of the page, before the guest even arrives.
Turning it off, or back on, is Shift and Escape, which both hides the disguise and brings it back, and it needs one browser permission, storage to run in the tab at all.
The one thing neither approach touches
This is worth being direct about, because a manual method sometimes claims more than a maintained one does. the address bar, which still reads claude.ai or chatgpt.com, and no method reaches further than that, not a bookmarklet and not Docognito's own continuously running script. The full story of the one feature Docognito tried and removed, an earlier version that rewrote the visible path and broke both assistants' routing, is on the page about hiding the address bar.
When a one-off script is genuinely fine
Not every situation needs a continuously running extension. If you only ever need the title changed for a single screenshot, and you are not going to look at the tab again afterwards, a console command does that one job and there is no reason to install anything for it. The trick stops being enough the moment you actually use the tab afterwards, send another message, or leave it open, because that is exactly when the page reasserts its own title and undoes the edit.
Built to outlast a single screenshot
If you need the tab title and icon disguised for the length of an actual working session, not one screenshot, a script that runs once cannot keep up with a page that keeps changing its own title, and something that runs continuously has to win that job instead. Docognito is built to keep winning it, and it makes no claim about the address bar in the process, because that claim does not survive contact with how the assistants route their own traffic.
Use Docognito for a session that lasts longer than a single screenshot.