Make long AIchats fast again.

It sets content-visibility on the element. The box keeps its size, the browser stops painting the contents, and nothing is removed from the DOM.

Still in the page, still in the archive, still searchable. Only the paint is skipped.

About a screen and a half in each direction, so scrolling never shows a blank while the browser catches up.

Here they are, with the intrinsic size that keeps the scrollbar honest:

content-visibility: auto;
contain-intrinsic-size: auto 320px;

It stays the length it was. contain-intrinsic-size reserves each message's last measured height, so the page does not jump as things sleep and wake.

Past roughly 25 messages. Below that there is nothing to win and the machinery would only add risk.

No. Mounting older messages is a button you press, and it stops the moment you scroll or press a key.

In extension-local storage only — never in a sync store. Anything that can read it can already read the plaintext archive beside it.

Putting it on a sync server adds a copy an attacker can reach without touching the device, and buys nothing, because the archive itself never syncs.

Both layers authenticate the header, so an edited parameter breaks the tag instead of being obeyed:

if (rounds < 600000) throw new Error("refused");

Fails to open. The envelope is bound to the header it was written with, so a swap is a tag failure rather than a weaker file.

Chats already archived are left alone; older ones the provider no longer lists come back. Nothing is overwritten and nothing is deleted.

The live copy wins for titles, the archive wins for messages. A title is cosmetic; a message is the thing you came back for.

A file that opens weaker than it claims, and a merge that quietly loses a chat the provider has since dropped. Both are refused now.

A once-daily full listing. Nothing else deletes, and no single failed request is treated as evidence.

It refuses to act on an implausible listing. A signed-out session can never present your whole archive for deletion.

With you: the chat is quarantined and flagged, and you keep it or mirror the deletion. Standing policies exist for both extremes.

Roughly every three hours, shortly after the browser starts, and when you open a chat site, at most once every twenty minutes.

No. Account-scoped checkpoints mean it reads only the new gap, so a reload is not a full resync.

One percentage for the whole pass across every platform, not one bar per site racing the others.

Off by default. A temporary chat is you telling that platform not to keep it, and we do not quietly overrule that.

They are archived locally, labelled temporary, with a badge on the page for as long as one is being archived. Never a silent recording.

As far as the archive goes. The page holds what the site has mounted; the archived copy holds the rest.

Both numbers: the matches on this page, and the matches further back. One number would hide the interesting half.

Eight hits on the page where the conversation held two hundred and seventeen. That gap is the feature.

Because a browser is never told when a message was sent, except where the app keeps that in its own local state.

Never. A first-seen time is labelled as such, and a message that predates the install says time unknown.

Role and content: your messages in rose, answers pale, code blocks in the lighter pink, anything starred in gold.

It is the viewport, drawn over the track. Its height is the fraction of the conversation on screen, so a long chat gives a thin lens.

No. Where the platform hands over the whole conversation, the archived copy answers instantly and the live copy corrects it a beat later.

Unknown structure means the extension does nothing rather than guessing. The worst case is the site's ordinary behaviour.

Health in the popup names which adapters are primary and which are degraded, per open tab, reading no message text.

Rate-limit response headers, and a response body only where the URL's own path says the response is about limits.

Never chat traffic, never a stream. Requests are not altered, blocked, delayed or replayed; the page gets exactly what the network gave it.

A redacted sample: every string over forty characters is replaced by its length, and no header bearing a token is kept.

A hash of the key, a device fingerprint, a hashed IP for thirty days, the trial start date, and the link between an address and a licence.

Pro keeps working and is marked overdue. Only the issuer saying the licence is gone withdraws it — an outage never does.

Five at once, released from the popup, and the oldest is freed automatically when you activate on a sixth this browser has seen before.

Nothing. It searches your local archive and puts the passages you tick into the prompt box you are already typing in.

It copies to the clipboard rather than touching a page it does not understand. A surprise insertion would be worse than a fallback.

The original ask, the messages you starred, and the last few turns. Quoted, never summarised, and nothing is sent for you.

The whole conversation with headings, lists, code fences and timestamps preserved — not the slice the page happens to hold.

Role, text and timestamp per message, re-importable, for anything you want to build on top of it.

No, and it never will. If Pro lapses or is refunded, the export still works — your archive is not held hostage.

You starred that passage. It is still in the archive, and search reaches it even where this page has unloaded the message.