2302ba5eeb
feat: minimal UI for login
2025-04-11 11:08:33 +01:00
c9a6c83649
feat(jwt): validating token
2025-04-10 15:49:53 +01:00
3294c1854c
feat(jwt): adding access and refresh token generation
2025-04-10 15:35:35 +01:00
29a5adb40a
feat(email): endpoint for sending auth code
2025-04-09 18:24:26 +01:00
51dc8daf35
wip(email-auth): auth and email modules
2025-04-09 18:13:49 +01:00
a22c56fd2c
refactor: moving image listener to own function
2025-04-09 17:20:27 +01:00
f169fd2ba2
fix(tools): testing and processing
...
fix
2025-04-09 13:56:30 +01:00
d36dec8d60
fix(types): agent processing stuff
2025-04-09 12:12:09 +01:00
6549643340
feat(orchestrator): calling needed agents when it needs to
2025-04-05 11:01:43 +01:00
49f1990341
refactor(agents): working e2e now
...
I guess some repeated code doesnt hurt anyone, if it keeps things
simpler. Trying to be fancy with the interfaces didn't work so well.
2025-04-04 22:40:45 +01:00
d3bc840555
refactor(ai-client): moving tool handling and client into seperate folders
2025-04-04 22:03:46 +01:00
ede5f16dc1
wip(orchestrator): basic scaffolding for the agent
2025-04-04 20:40:31 +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
c5278554cc
feat(contacts): events can now have organizers
2025-03-31 18:40:36 +00:00
254edf3421
fix(backend): SQL statements without returns
2025-03-26 16:51:46 +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
87869543f7
feat: using tools for event loocation agent
2025-03-22 10:12:51 +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
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
863716c096
feat: super basic image search
2025-03-08 15:37:10 +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
1424ec22f4
fix: using json response header
2025-03-07 14:14:40 +00:00
e595783d89
wip: Using mistral instead of OpenAi
2025-03-07 13:42:50 +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
b99432c202
feat: saving AI information to database
2025-02-24 21:00:05 +00:00
ee0587a16b
feat: method for getting images
2025-02-24 20:05:56 +00:00
64f6bde6a9
feat: methods to get image
2025-02-24 20:02:58 +00:00
2115da85b5
feat: working docker image and compose file
2025-02-24 19:44:19 +00:00
97b1619b01
refactor: moving all files to backend
2025-02-22 23:30:59 +00:00
