Resizable panel cookie saving disabled to fix HTTP 431 errors
The web application will no longer store resizable panel dimensions in cookies, resolving an issue where oversized request headers caused server rejections.
The web interface was occasionally locking out requests with HTTP 431 errors—a server rejection triggered when request headers grow too large. This bloat occurred because the application was meticulously saving the exact pixel dimensions of every resizable panel directly into browser cookies, which are sent back to the server on every request.
Cookies are no longer used to remember UI panel sizes. By stripping out this serialization step in the foundational UI primitives, overall cookie payload sizes are kept lean. The application remains stable and accessible, dropping the dead weight of layout preferences from network requests.