[stavros]

I'm really excited about the Index. I don't love that it's disposable, but I really like the UX. I couldn't wait, so I made my own (obviously not a ring, but airtag-sized), and it's amazing. I have it in my pocket, I take it out, speak a little note, and it goes off to my AI assistant for whatever needs doing.

That and the AI assistant have really changed how I operate day to day. I'm super excited about the Index, and I hope it has the same capability my app has (mostly, sending a webhook with the transcription with exponential backoff, so I'm sure all my notes will eventually be sent).

[richardlblair]

I too am very excited. I had a voice recorder laying around and have worked that into my workflow over the past few months. Although, my AI assistant is a cobbled together set of python scripts.

What are you using for your AI assistant?

[stavros]

I made my own, as I thought OpenClaw was a bit too insecure:

https://github.com/skorokithakis/stavrobot

I love it, it's amazing. I want to add a small section to the README about how to use it well (how to manage memory and the database, basically), but it's just fantastic. It has had basically zero bugs, as well.

[justanotherunit]

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?

[stavros]

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 Signal, a Telegram webhook, and the other big component is a coding agent and a tool container. The coding agent can write files to a directory that's also mounted in the tool container, and the tool container can run the tools. That way you separate the coder from everything else, and nothing has access to any of your keys.

You can't really avoid the coder exfiltrating your tool secrets, but at least it's separated. I also want to add a secondary container of "trusted" tool that the main LLM can call but no other LLM can change.

This way you're assured that, for example, the agent can't contact anyone that you don't want it contact, or it can read your emails but not send/delete, things like that. It makes it very easy to enforce ACLs for things you don't want LLM-coded, but also enables LLM coding of less-trusted programs.

[stavros]

And now it can even make private (and public!) dynamic websites that have access to data from your database, while exposing only the data you want exposed.

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".

[justanotherunit]

Fascinating, thanks for responding. If k may ask, what is your monthly (or any other interval) token usage? And are you finding a pi to be a bottleneck in regards of any performance?

[p1nkpineapple]

can you give some more detail about the airtag-sized device you made? This is exactly what I've been thinking about doing to test the "idea" of the Index, but haven't figured out how to go about doing it.

(Tried looking on your blog, but ended up instead reading your article about the little ESP8266 clock which convinced me to buy one to play with myself, thanks!)

[stavros]

Sure, I haven't written it up, but the code is here:

https://github.com/skorokithakis/middle

I'll take some photos, it's larger now than it will be, because I don't have a MEMS mic (and a small battery). It looks like this now:

https://imgz.org/iACAKWj2/