I'm not sure how much sandboxing can help here. Presumably you're giving the tool access to a repo directory, and that's where a juicy .env file can live. It will also have access to your environment variables.
I suspect a lot of people permanently allow actions and classes of commands to be run by these tools rather than clicking "yes" a bunch of times during their workflows. Ride the vibes.
I've tried the shaders in the following repo with ghostty. They definitely work. I ended up keeping a cursor trail shader. https://github.com/0xhckr/ghostty-shaders
Google renamed Bard to Gemini last year. Side note: Google's "Gemini" product name is way overloaded. They have like 6 different things that you can buy/use that are named that.
That may be true, but that's not the news I'm exposed to. I only see him pop up every few years or so when he's announcing The Next Big Thing or trying to look/act more like a human person.
Those that have their names on the high score board of capitalism are truly the Einsteins of our generation and we should be so lucky to hear every thought stream that dribbles out of their heads.
Ah, I was hoping (at least rough) coordinates were something that this would do. I have HA and have been looking at mmwave devices for that use case. For things like "turn on a light, but only once I've sat down in the chair."
It seems like I'm probably preaching to the choir, but what really is the attack surface with coreutils? I can't imagine there have been a lot of pwns as a result of the `date` command.