ChatHaiku / Support Open chat Status
Using ChatHaiku

Conversations

Every chat is saved automatically in your browser. You can rename, search, branch, and delete them — but because they live on your device rather than on a server, they do not follow you between browsers.

Stored on your device

Conversations are kept in your browser's local storage. They are not uploaded, not synced, and not visible to anyone else using ChatHaiku. They also do not appear on your phone if you started them on your laptop, and clearing your browser data erases them. See Your data and privacy.

On desktop, saved chats appear in the left sidebar, most recent first. The button at the top left toggles the sidebar; it stays collapsed between visits if you leave it that way. On mobile, tap the chevron beside the title and choose Sessions.

Sidebar
TCP versus UDP
Recovering a deleted git branch
Dinner ideas for six Branched
Explaining eigenvalues
A Branched badge marks a chat split off from another conversation. Hovering it shows which one.

Names

New chats are named automatically from the first exchange — the model writes a short title once there is enough to summarise. Until then the chat shows as untitled.

To rename one yourself, use the rename control on the conversation row. A chat you have named manually is locked: automatic naming will not overwrite it afterwards.

ChatHaiku keeps up to 256 conversations. Past that, the oldest are dropped to make room for new ones. If you have something you want to keep indefinitely, copy it out.

Press Ctrl + K (or ⌘ + K on a Mac) to open search, or use the search button at the top left. Search covers the full text of every saved conversation, not just the titles, and results show the matching phrase in context.

Move through results with ↑ and ↓, open one with Enter, and close with Esc. Opening a result jumps directly to the matching message and flashes it briefly so you can see where you landed.

The outline

The button at the top right opens an outline of the current conversation — a list of your turns, in order. Clicking one jumps straight to it. This is aimed at long chats where scrolling back to “the thing I asked about an hour ago” is tedious.

Branching

Branching copies a conversation up to a chosen point and starts a new chat from there. The original is untouched. It is the right tool when a conversation has been useful so far and you want to try a different direction without losing what you have.

Open the options menu on any of your messages and choose Branch into new chat. Everything before that message comes with you; everything after it stays behind in the original.

Branching is also a context reset

Because a branch drops everything after the chosen point, it is a good way to recover a long conversation that has hit its context limit — branch from an early message, and the new chat starts small again while keeping the setup that mattered.

Per-conversation settings

Each conversation remembers the model and response settings it was using. Switching back to an old chat restores them, so a conversation you were having with Epos 2.1 in Creative mode resumes that way rather than picking up whatever you last used somewhere else.

Deleting

Delete a single conversation from its row in the sidebar or session panel. To remove everything at once, use the clear-all option in the session panel.

Deletion is immediate and permanent

There is no archive and no undo. Because conversations exist only in your browser, there is no server-side copy to restore from. Copy anything you want to keep before deleting.

If your conversations disappear

Chats are tied to one browser on one device, under one site address. They will appear to vanish if you:

  • cleared browsing data, cookies, or site data;
  • opened ChatHaiku in a private or incognito window, which discards storage on close;
  • switched browsers, devices, or profiles;
  • use a browser setting or extension that clears site data automatically;
  • reached the 256-conversation cap, dropping the oldest.

Unfortunately none of these are recoverable — there is no server copy to restore. See Troubleshooting for related problems.