9b95ffb59e
feat(contact-agent): using createContact with an ID field to provide updates
2025-04-17 18:57:13 +01:00
5ab0d13b21
fix(location-events): adding location id to the database from agent call
2025-04-17 15:32:50 +01:00
51d36bf15b
more prompt
2025-04-14 10:36:21 +01:00
d7ab3f56dc
stupid
2025-04-14 10:30:46 +01:00
1f83b721a6
fix: prompts
2025-04-14 10:28:31 +01:00
0596ea2b1e
debug
2025-04-14 10:22:54 +01:00
0ed6b4c123
debug
2025-04-14 09:44:19 +01:00
30143019d6
feat: making all codes upper case + fetching fixes
2025-04-14 09:28:08 +01:00
cd5dd347d3
fix
2025-04-14 09:15:48 +01:00
ab09378fcd
chore: removing SQL debug
2025-04-14 09:12:16 +01:00
4f6c198307
feat: registering users if their email is not known
2025-04-13 22:29:25 +01:00
3156cea904
feat(event): seperate event agent
2025-04-13 16:30:20 +01:00
d432d16752
feat(location): agent to create locations
2025-04-13 16:30:20 +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
9660c99a14
feat: contacts working
2025-04-11 20:31:51 +01:00
6290c4b843
feat: checking user authorization on image retrieval
2025-04-11 19:41:36 +01:00
3294c1854c
feat(jwt): adding access and refresh token generation
2025-04-10 15:35:35 +01:00
393eaea2f4
feat(notes): allowing frontend to save
2025-04-01 20:54:15 +00:00
a385ef21cf
feat(notes): saving the notes for any images for easy text searching
2025-04-01 20:45:43 +00:00
a37818fc49
feat(events): search through organizer
2025-04-01 19:59:17 +00:00
1b2a99a3c8
fix: adding location to general query
2025-04-01 19:32:55 +00:00
c5278554cc
feat(contacts): events can now have organizers
2025-03-31 18:40:36 +00:00
c817654f3e
feat(events): adding start and end times
2025-03-31 17:32:55 +00:00
254edf3421
fix(backend): SQL statements without returns
2025-03-26 16:51:46 +00:00
382a1f53bd
feat: attaching both to image
2025-03-26 16:22:23 +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
13e5ed9f9e
feat(locations): allowing AI to attach it to the image
2025-03-22 17:47:02 +00:00
dfb4b34de3
feat(location): working e2e with tool calling
2025-03-22 12:22:31 +00:00
7b6c7090f8
feat(tool-calls): listLocation tool call handling
2025-03-22 11:14:00 +00:00
3541a4755c
wip(frontend): adding more information
2025-03-21 14:36:03 +00:00
cf703f3eee
fix: re-adding location to event
...
Figured it out
2025-03-21 14:08:06 +00:00
84881c5c2d
fix: simplifying query
...
I do have some learning to do about go-jet specifically.
I can't include the Location field on events, because the QRM will add
any location to the events
2025-03-21 14:01:21 +00:00
f7382b0d2b
feat: returning events and locations from end point
2025-03-20 18:34:11 +00:00
47dd025ae3
feat: working e2e solution
2025-03-20 17:59:00 +00:00
9932568986
feat(events): also working
2025-03-18 18:37:12 +00:00
3a0f93e406
feat(locations): now working
2025-03-18 18:18:01 +00:00
b09063f74a
refactor(text,tags,links): to foreign key to image instead of user_image
2025-03-18 17:48:38 +00:00
4b120982d0
fix: returning whole tag object
2025-03-16 18:29:15 +00:00
7582e4d8d9
fix: returns correct image ID
2025-03-16 18:20:29 +00:00
8acf25a2a7
refactor(models): using more organised structure
2025-03-16 18:13:30 +00:00
536a49fe1c
feat(tags): correctly inserting new tags and adding them to images
2025-03-11 22:47:28 +00:00
40e854fb87
feat(tags): creating and getting user tags
2025-03-11 21:23:41 +00:00
53ebbb6e8d
feat: sending images and receiving them is now working
2025-03-08 13:13:05 +00:00
bf07c18fd7
feat: sending base64 image to backend
...
This is silly, but binary is apparently hard to do????
2025-03-08 12:30:16 +00:00
d1d6ee6762
fix: some spam from get images request
2025-02-26 20:48:52 +00:00
ad61b8e1fa
fix: getting user images
2025-02-26 20:09:19 +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
410270e217
refactor: using chi router + bug fixes
2025-02-26 18:04:30 +00:00
5bec6c9590
fix: actually saving to the correct db table
2025-02-26 15:54:27 +00:00
