Earlier quoted context omitted.
Interesting, would you mind sharing your architectural setup? How does your index communicate to your agent server, what is the main agent framework/engine used? Sounds like a cool concept to speak into your watch/wearable which automatically saves or performs tasks on the fly. What is the general execution time from: Prompt received -> final task executed?
So basically there's a /chat endpoint that goes to the LLM (a Pi agent), which has access to call specific tools (web search, SQL execution, cron) but doesn't have filesystem access, so the only thing it can do is exfiltrate data it can see (pretty big, but you can't really avoid that, and it doesn't have access to anything on the host system). There's a Signal bridge that runs on another container to connect to Sign…
I'm really liking it, I created a page to show my favorite restaurants per city, for example:
https://stavrobot.home.stavros.io/pages/restaurants
That's dynamic, loading from the database, and updating live when the assistant creates new entries.
This page was created just by telling the assistant "make me a page to show my favorite restaurants, with their ratings, groupped by city".