* feat: new iteration of chatui - beware it is still buggy
added some error handling, but I believe this still needs a lot of improvements.
added timestamps for when messages are sent.
when changing to a new agent the agent initiates the conversation.
persisting messages for now. Storing them in localstorage so users can see their
history and don't lose it on reload. replacing this with intelligent fetching asap.
* chore: build frontend
* autogenerate openapi file on server startup
* added endpoint for paginated retrieval of in-context agent messages
* missing diff
* added ability to pass system messages via message endpoint
* patched bad depends into queries to fix the param info not showing up in get requests, fixed some bad copy paste
* adding docstrings + pydantic models to rest api for autogenerating the openapi documentation
* add tags to all endpoitns
* updated docstrings, added response type, patched runtime error
* feat: add dark mode & make minor UI improvements
added dark mode toggle & picked a color scheme that is closer to the memgpt icons
cleaned up the home page a little bit.
* feat: add thinking indicator & make minor UI improvements
we now show a thinking while the current message is loading.
removed status indicator as we do not work with websockets anymore.
also adjusted some of the chat styles to better fit the new theme.
* feat: add memory viewer and allow memory edit
* chore: build frontend
* feat: add loading indicator when creating new agent
* feat: reorder front page to avoid overflow and always show add button
* feat: display function calls
* feat: set up proxy during development & remove explicit inclusion of host/port in backend calls
* fix: introduce api prefix, split up fastapi server to become more modular, use app directly instead of subprocess
the api prefix allows us to create a proxy for frontend development that relays all /api
requests to our fastapi, while serving the development files for other paths.
splitting up the fastapi server will allow us to branch out and divide up the work better
in the future. using the application directly in our cli instead of a subprocess makes
debugging a thing in development and overall this python native way just seems cleaner.
we can discuss if we should keep the api prefix or if we should distinguish between a REST only
mode and one that also serves the static files for the GUI.
This is just my initial take on things
* chore: build latest frontend
