Anyway, thanks for sharing. It doesn't look like it handles cli auth though (aws, npm, etc. all leave tokens sitting in your home directory). What do you use for those?
757 karma · joined March 20, 2015
Anyway, thanks for sharing. It doesn't look like it handles cli auth though (aws, npm, etc. all leave tokens sitting in your home directory). What do you use for those?
I wonder if it could be local storage and you could provide your own Open Router endpoint? That way it could be a local model or your own deployment of GPT/Claude in Azure/Bedrock/Vertex etc where you can control retention policies etc.
Basically, I want to know that you guys don't have access to view my stuff. I get that that limits your ability to improve the product and support issues, but when I'm sending everything it really starts to matter. Just thought I'd share what held me back from immediately signing up despite really wanting to use a product like this!
I guess the difference is the fact that the intermediary server doesn't need a port open (as standard nat punching will work)? Or are there other big differences?
- a heartbeat, so it was able to 'think'/work throughout the day, even if you weren't interacting with it - a clever and simple way to retain 'memory' across sessions (though maybe claude code has this now) - a 'soul' text file, which isn't necessarily innovative in itself, but the ability for the agent to edit its own configuration on the fly is pretty neat
Oh, and it's open source
You can run it on a raspberry pi (or ideally an N100+), and for the microphone/speaker part, you can make your own or buy their off the shelf voice hardware, which works really well.
My only wish is that I hope it preserves the audio file, in case the transcription is wrong, so you don't lose the thought. Google Keep does this well and it's a life saver sometimes, when the transcription comes through as "Eat the cat" or something ridiculous.