208 Commits

Author SHA1 Message Date
28a4b37dde feat: showing the lists which an image is a part of 2025-07-29 15:54:51 +01:00
4de4431390 feat: getting list that an image belongs in 2025-07-29 15:48:41 +01:00
13170a33e8 fix: adding wait group so we can concurrently call these 2025-07-29 15:40:18 +01:00
5024933852 feat: making the description markdown 2025-07-29 15:40:11 +01:00
a0bf27dd16 Haystack V2: Removing entities completely 2025-07-29 14:52:33 +01:00
3d05ff708e feat: giving agent enough information to add to list instead of creating one 2025-07-29 12:14:45 +01:00
ee109f05a0 feat: showing table on frontend for pages 2025-07-29 12:01:35 +01:00
f4d8c9f083 feat: getting schema information from images 2025-07-29 11:44:08 +01:00
a1af3feb1d chore: removing deadcode 2025-07-29 11:37:53 +01:00
8597584cf0 feat: initial draft of generating a schema from one image
fix: error formatting
2025-07-29 11:37:23 +01:00
88d033314e feat: initial attempt to create a schema 2025-07-29 09:47:59 +01:00
9cae780431 fix: column generation 2025-07-29 09:47:47 +01:00
0058cdce40 feat: showing description on image page in frontend 2025-07-24 14:23:20 +01:00
37f966e508 feat: finishing description agent infrastructure on backend 2025-07-24 14:12:41 +01:00
59bf884f5d refactor: changing notes to be a simple image description
Notes would generate too often and not be very useful. This is much
better.
2025-07-24 13:59:24 +01:00
e19e6562bb feat: getting new lists onto the frontend 2025-07-22 19:49:36 +01:00
a283bc1bcd feat: new AI generated lists
I think this could be how we generate other lists

Problems:
- Knowing it's a location is good because you can do nice stuff on the
frontend.
- Same for contacts & events.

So a good alternative, is to still use this type, but perhaps change the
database such that all lists live within the new tables (lists,
image_lists). But have special tags.

This would also make it easier on the AI I think.
2025-07-22 19:40:56 +01:00
1b816e512a fix: using tagged switch 2025-07-22 18:52:26 +01:00
6482a76a51 feat: processing images and notification centre 2025-07-02 14:12:19 +01:00
c632487d7e feat: sending processing images on app load 2025-07-02 12:04:16 +01:00
019c4c6b0c chore: removing unnecessary comment 2025-05-12 20:51:21 +01:00
ad2a70aaf3 feat: multiple listeners on channels
Multiple device notifications supported.

Actually beautiful
2025-05-12 20:51:06 +01:00
076e230a01 feat: making SSE work on mobiles 2025-05-12 20:11:58 +01:00
636bd9df0e wipwipwip 2025-05-12 19:54:09 +01:00
64879ac9d6 wip 2025-05-11 16:16:18 +01:00
e674043daa wip 2025-05-11 16:15:15 +01:00
e8a51ecc52 fix: the reason this wasn't working
This was also silent failing, so should probably have a look at it
2025-05-11 14:30:31 +01:00
5a2b990c0c fix: adding extension hack
fix
2025-05-10 22:05:24 +01:00
b97eae10a3 hack: allowing demo@email.com to login straight away for test flight submittion 2025-05-10 21:03:32 +01:00
a4b94fc6c2 feat: frontend receiving processing images and showing them as such 2025-05-10 17:39:09 +01:00
64439d9041 feat: using struct to send notification and improved image model 2025-05-10 16:03:31 +01:00
2f3d643278 feat: not deleting images to process 2025-05-10 15:12:25 +01:00
8e6424aa63 feat: sending notifications 2025-05-10 15:04:11 +01:00
c69ca7da5c chore: adding log to check error 2025-05-10 14:30:26 +01:00
7b0c84e88e feat: adding allowed keys to only send when we have a userId
This is to prevent users that aren't connected to the socket (somehow),
to not fill up memory with buffered messages we'll never need.
2025-05-10 14:29:48 +01:00
ff7960e2dd feat: notifier module with buffered channels 2025-05-10 14:21:18 +01:00
52cb50b168 hack: using prod url 2025-05-08 09:52:46 +01:00
eaa029cce1 fix 2025-05-08 09:52:04 +01:00
9a7654ae2d fix: logs 2025-05-08 09:44:44 +01:00
07b83aa728 feat: allowing user to get a list of their images
feat: UI to show and organise user images
2025-05-05 16:24:15 +01:00
9c325c7799 feat: adding timestamps to all important tables 2025-05-05 15:38:05 +01:00
6119938e52 mini just is better :( 2025-05-04 10:19:39 +01:00
ce8d546447 fix: not sleeping 2025-05-04 10:07:31 +01:00
b046a928b0 feat: using gpt-4.1-mini
feat: createExistingContact

feat: using nano instead of mini so I don't run out of money instantly
2025-05-03 18:25:35 +01:00
9860dd2dc5 feat(agents): providing a seed so it has more predictable results 2025-05-03 17:31:55 +01:00
4922df6682 fix(sse): some bugs 2025-04-27 14:56:06 +01:00
a9ecd5818a fix: re-requesting image when all agents are done
This means the agents are no longer parallel. Which will eventually be a
bottleneck, but I need to spend a bit more time on allowing for it to be
parallel, but now is not the time.

TODO: add a ticket
2025-04-27 14:45:23 +01:00
d34805030f feat: frontend responding to backend SSE and refetching images 2025-04-26 20:32:01 +01:00
7f7a2975af fix
wip

fix
2025-04-26 17:08:33 +01:00
b27e191e5c feat(processing-image): displaying initial status from response 2025-04-26 11:47:51 +01:00