The short answer
Organizing a Whizi chat history comes down to four actions: rename a chat, delete one chat or several at once, search the chat list from the sidebar search box, and group chats into projects, which are folders of conversations that also carry pinned files and per-project instructions.
The one detail that changes how you should use all four: the sidebar search matches the chat title only. Message bodies are not searched. So a chat you never renamed is findable only by scrolling, and renaming is effectively how you index your own history.
| Tool | Where it lives | What it actually does |
|---|---|---|
| Rename | The chat list | Sets the title, 1 to 120 characters. The title is also the only thing search matches |
| Delete | The chat list | Removes one chat, or several in one action |
| Search | A search box over the chat list in the sidebar | Matches titles across projects and the ungrouped list at once |
| Projects | The sidebar, listed above the chat list | A folder of chats, plus up to 10 pinned files and instructions applied to every chat in it |
Renaming a chat, and the two different length limits
A conversation title has to be between 1 and 120 characters. The backend refuses anything outside that with Conversation titles must be between 1 and 120 characters., HTTP 400, code invalid_title.
The website stops you earlier than the backend does. It refuses a blank name with the toast Chat name cannot be empty. and a long one with Chat name is too long (max 100 characters). So the practical ceiling when you rename from the website is 100 characters, while the field itself accepts 120.
If the rename call itself fails, the toast is Failed to rename chat. Please try again.
Because search matches titles, a good title is a search query you are writing for your future self. Names that work are the ones carrying the noun you will actually type: a client name, an invoice number, a file name, a project code. Names that do not work are the ones the first message generates for you, which describe the opening question rather than what the thread became.
What the search box does and does not do
The sidebar has a search box over the chat list. It matches the chat title, and it cuts across projects and the ungrouped list together, so a chat is findable by name whichever folder it sits in.
Message bodies are not searched. There is no full-text search over what was said inside a conversation, so a phrase you remember from an answer will not find the chat that contains it. This is the single most useful thing to know before you build a filing habit, because it means the work belongs in the title rather than in the folder structure.
There is also no keyboard shortcut to jump to it. Whizi binds Enter to send and Shift plus Enter to a newline, and Escape closes an open dialog, and beyond those two conventions there is no shortcut system and no shortcuts panel.
Projects: folders that carry files and instructions
A project is a folder of conversations that also holds pinned files and its own custom instructions. Projects are listed in the sidebar above the chat list, and they are available to any signed-in account including the free tier. The per-project caps are abuse guards rather than a paid gate.
A chat belongs to at most one project. Anything not in a project stays in the ordinary chat list, which is why the sidebar can show projects and an everything-else view side by side.
| Cap | Value |
|---|---|
| Projects per account | 50 |
| Project name | 120 characters |
| Project instructions | 32,000 characters |
| Pinned files per project | 10 |
| Size of one pinned file | 10 MB |
| Extracted text from one pinned file | 32,000 characters |
| The whole project prompt block | 120,000 characters |
| Creating or editing a project | 20 per minute |
| Uploading a project file | 10 per minute |
Pinned files accept PDF, plain text, Markdown, CSV, JSON, .docx and .xlsx. Images are deliberately excluded, because a pinned file rides along as prompt text on every turn rather than being looked at once.
Two consequences follow from that, and they are the reason a project is more than a folder. The first is cost of context: the project instructions and the pinned file text are rebuilt into the prompt on every single message in that project, inside the same input budget as the conversation itself. The detail on what that spends is in when the conversation is too long. The second is retention: pinned file bytes are stored until you delete them and do not expire, unlike chat attachments, which are configured to expire after up to 30 days.
Project instructions are also the only user-authored standing instructions in the product. There is no account-level custom instructions setting, so if you want the same brief applied to every chat about one piece of work, a project is where that lives.
Deleting chats, and what deletion actually removes
A chat can be deleted from the chat list, one at a time or as a bulk selection. A failed single delete shows Failed to delete chat. Please try again., and a failed bulk delete shows Failed to delete some chats, with no trailing full stop on the second one.
Deleting a conversation is not the same action as deleting your account. Individual conversations can be deleted on their own, and cancelling a subscription does not delete anything: it stops billing and ends access at the end of the paid term while the account and its contents remain. Removing the data is the separate account deletion action.
Deleted rows do not vanish from every layer at once. Cloudflare D1 keeps protected point-in-time recovery history, and deleted database records may remain in that history for up to 30 days before aging out. Where each kind of content lives and how long it is kept is set out in where Whizi stores your data.
One gotcha specific to imported history: deleting an imported chat and importing the same export again brings the chat back, rather than being skipped as a duplicate. Imports are keyed by account plus source plus source id, so re-running an import is normally safe and idempotent, but it is also the one way a chat you deleted returns. The rest of the import behavior is on chat import errors.
When organizing actions fail for a reason that is not about organizing
One error shows up across all of these and has nothing to do with the chat itself. Failed to retrieve session token. is thrown by the website whenever the token fetch returns nothing before a chat list, chat load, delete, rename or upload call. It carries no HTTP status and no error code, because the site throws it before the request is made.
Conversation not found. is the backend counterpart, HTTP 404 code not_found, returned when the conversation id does not exist or is not owned by the caller. It appears on the read, delete, rename, message-append, version-switch and share routes alike.
Both are sign-in problems rather than data problems. The fixes, and the full list of session error strings, are on login and account access.
- Search matches chat titles only, never message bodies
- Rename accepts 1 to 120 characters, though the website refuses anything over 100
- Search cuts across projects and the ungrouped list at once
- Projects are available on every plan including free, up to 50 per account
- A chat belongs to at most one project
- Pinned project files ride along on every turn, so 10 files is a context cost as well as a cap
- Pinned project files do not expire, unlike chat attachments
- Deleting an imported chat and re-importing the same export brings it back
- Deleting a chat is not the same as deleting your account
Frequently asked questions
Can I search inside my Whizi conversations?
You can search the chat list, but the match is on the chat title only. Message bodies are not searched, so a phrase you remember from an answer will not find the thread it came from. The search does cut across projects and the ungrouped chat list together, so a chat is findable by name whichever folder it is in. In practice this makes renaming the important habit: the title is the index.
How do I rename a chat in Whizi?
Rename it from the chat list. A title must be between 1 and 120 characters, and the backend refuses anything else with Conversation titles must be between 1 and 120 characters. The website is stricter and stops you at 100 with the toast Chat name is too long (max 100 characters)., and refuses an empty name with Chat name cannot be empty.
Does Whizi have folders for chats?
Yes, they are called projects. A project is a folder of conversations that also carries up to 10 pinned files and its own instructions, up to 32,000 characters, applied to every conversation in it. You can have 50 projects per account, and they are available to any signed-in account including the free tier. A chat belongs to at most one project, and anything unfiled stays in the ordinary chat list.
Do pinned project files count against the conversation length?
Yes. The project instructions and the extracted text of every pinned file are rebuilt into the prompt on every single turn in that project, inside the same input budget as the conversation. Each file contributes at most 32,000 characters of text and the whole project block is capped at 120,000 characters. If a project chat seems to lose the thread faster than an ordinary one, that is why, and unpinning what you are not asking about is the fix.
If I delete a chat, is it really gone?
The conversation is deleted from your account without touching anything else, and you do not need to delete your account to remove one chat. Deleted database rows may persist for up to 30 days in Cloudflare D1 point-in-time recovery history before aging out. The exception worth knowing is imported history: deleting an imported chat and importing the same export again restores it rather than skipping it as a duplicate.
Are there keyboard shortcuts for managing chats?
No. Enter sends a message, Shift plus Enter inserts a newline, and Escape closes an open dialog. Beyond those two conventions there is no shortcut system in Whizi, no chord bindings, and no shortcuts help panel.