Feature Requests

Can we get that 50mb file limit upload increased? Thanks!

It was much easier to scroll back through chats to find the one you want. Now you have to view them a page at a time and if you pick the wrong one, you have to start back on page one again. The search is not great at finding chats (or certain words are blocked perhaps?)

The copy button is unreliable. Most of the time you cannot copy from the code context.

In chat, Improving input box so that during long prompts it does not cover up output we are trying to respond to. Many times I am trying to respond to output questions and trying to answer questions, and as the prompt gets longer it starts to cover up the output more and more. Please put a scroll on the input box so it does not get so big

Since the apps don't allow you to continue the chat, it would be nice if you could have saved prompts for the chat - maybe create a prompt library.

Heavy users of other LLMs will want a seamless integration from their personal AI of choice into Hatz. Currently there is no migration at all. Processes are extremely manual. Most LLMs have built in channels for digesting context and chat feeds from other LLMs.

After prompting in hatz, you can not currently type while its thinking. Often times other thoughts will jump in my head that I want to get out to prepare for my next prompt and you are not able to type while its thinking. Claude can do this, so it would be another nice feature to have.

Occasionally, when I cancel/stop an in-progress LLM response, the conversation appears to reset and all prior context is lost. The UI shows only the most recent prompt/response, and subsequent model replies behave as if the earlier chat never happened (it no longer references or uses any previous messages). This is intermittent but effectively wipes the thread’s context after a cancellation.

Problem: Chat Folders are flat and personal-only: no subfolders, one folder per chat, no sorting controls, and no way to share folders with anyone. As an MSP managing dozens of clients (I'm at 36 folders and growing and with another 25 chats that need to be filed away - yikes!), flat folders don't scale, and there's no way to organize or share content at the team level. Requested capabilities: Full tree structure with subfolders - nested folders (configurable depth) shown as an expandable/collapsible tree in the sidebar, with drag/drop to move chats and folders between levels. Sorting options for folders and chats within them: Alphabetical (A-Z / Z-A) Numerical / natural sort (so "Chat 2" precedes "Chat 10") By date/time - oldest -> newest and vice-versa, like File Explorer or Outlook Manual ordering as an alternative, applied recursively to subfolders Granular sharing - share any folder, subfolder, or individual chat to any group, team, or the organization, with inherited permissions from parent folders (overridable at any level) and role-based access (view / comment / manage). Date-based organization - surface chat created/last-activity timestamps so date sorting and date-range filtering are possible. Use case: As an MSP, we organize chats by client, department, and project. A hierarchical tree with proper sorting (especially date-based, like Outlook) and org/team-level sharing would let us structure content the way our clients actually work, and let teams share curated chat libraries instead of one-off snapshot links. Related: Builds on "Unified 'Project' Folders (Shared Context)" https://hatz-ai.canny.io/feature-requests/p/unified-project-folders-shared-context - this extends that idea with nesting, sorting, and per-level sharing controls.

When using hatz for long build sessions I find that I run out of space for additional files. The conversation gets littered with multiple versions. It would be great if there was a way to compact the conversation so that it can continue without all of the files still in the sandbox. Or a way to start a new conversation but pick up where the last one left off.