10 Commits

Author SHA1 Message Date
221afb599b BIG MASSIVE REFACTOR OMG
Ripped out literally everything to simplify the backend as much as
possible.

Some of the code was so horrifically complicated it's insaneeee
2025-09-21 21:31:44 +01:00
2dd9f33303 feat: allowing users to delete images from lists 2025-08-30 21:38:01 +01:00
70161da3ed opencode: delete method for stacks 2025-08-25 15:30:34 +01:00
3a182fc49b working notifications across backend and frontend 2025-08-25 15:22:24 +01:00
ec7bd469f9 sending notifications about new stacks 2025-08-25 15:13:29 +01:00
10cea769bf creating stacks using a user request 2025-08-20 21:38:55 +01:00
390a216260 implementing get list items 2025-08-19 21:44:11 +01:00
3d05ff708e feat: giving agent enough information to add to list instead of creating one 2025-07-29 12:14:45 +01:00
8597584cf0 feat: initial draft of generating a schema from one image
fix: error formatting
2025-07-29 11:37:23 +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