Commit Graph

6 Commits

Author SHA1 Message Date
Charles Packer
6dc041711c fix: patch messages route + unify all the api/agents API routes to use {agent_id} via path parameter (#1129)
Co-authored-by: Robin Goetz <35136007+goetzrobin@users.noreply.github.com>
2024-03-11 14:30:58 -07:00
Robin Goetz
e0e031795a feat: allow admin to access all API routes & add back auth (#1047) 2024-02-25 07:16:45 -08:00
Charles Packer
dd209a3132 feat: Add API keys to memgpt server REST API (#1014) 2024-02-16 13:14:35 -08:00
cpacker
646f0e8593 various patches related to UUID usernames to make chatui work 2024-01-15 18:09:25 -08:00
Charles Packer
83973ecfc8 feat: Update REST API (#647)
* 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
2024-01-11 14:48:10 +01:00
Robin Goetz
39ada91fe7 feat: next iteration of chat ui (#637)
* 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
2024-01-11 14:47:51 +01:00