6b0fcf3005
wip(agent-builder): im not sure sure this is actually a good idea
2025-04-18 14:34:29 +01:00
47c871523d
feat(sse): very rough events. Not used in the client yet
...
feat(sse): very rough events. Not used in the client yet
2025-04-13 14:27:59 +01:00
3294c1854c
feat(jwt): adding access and refresh token generation
2025-04-10 15:35:35 +01:00
a385ef21cf
feat(notes): saving the notes for any images for easy text searching
2025-04-01 20:45:43 +00:00
c5278554cc
feat(contacts): events can now have organizers
2025-03-31 18:40:36 +00:00
bb5f2bc2fe
feat(schema): basic contact tables
2025-03-31 18:10:04 +00:00
3f53317c06
feat(schema): removing coordinates and adding start times to events
...
.
2025-03-31 16:44:42 +00:00
f90876f499
feat: creating events and attaching locations
2025-03-26 16:16:48 +00:00
410df01b4d
feat(tool-calling) Big refactor on how tool calling is handled
...
these commits are too big
2025-03-22 20:46:26 +00:00
3541a4755c
wip(frontend): adding more information
2025-03-21 14:36:03 +00:00
b09063f74a
refactor(text,tags,links): to foreign key to image instead of user_image
2025-03-18 17:48:38 +00:00
40e854fb87
feat(tags): creating and getting user tags
2025-03-11 21:23:41 +00:00
d8095b0c67
refactor: tables for image and processing_image
...
This allows a single table to be used to process images, meaning if
anything happens to the system we can always return to polling the
database and process these images individually.
Because of this we also want an `image` table to contain the actual
binary data for the image, so we aren't selecting and writing it each
time, as it is potentially a bottleneck.
2025-02-26 20:01:56 +00:00
b99432c202
feat: saving AI information to database
2025-02-24 21:00:05 +00:00
97b1619b01
refactor: moving all files to backend
2025-02-22 23:30:59 +00:00
