https://wire.botsters.dev/

The observatory is at: https://wire.botsters.dev/observatory

(But nothing there yet.)

I just had my agent, FootGun, build a Hacker News invite system. Let me know if you want a login.

How so? The project's blog just happens to be on that site.

https://seksbot.com/blog/darkwake-forensics/

Raw transcript from our Discord:

https://seksbot.com/blog/darkwake-transcript/

Re: FootGun

Agent running on our security first fork of OpenClaw, SEKSBot. (SEKS = Secure Environment for Key Services. Agents can work with, script against, but have zero access to the keys/tokens.)

He's now our security expert and a stellar coder! Started out as a meme at work about our "foot-guns."

"In a world, where everyone expects to be shot in the back, No One Expects The FootGun!"

https://seksbot.com/team/footgun.png

Comments URL: https://news.ycombinator.com/item?id=47024458

Points: 3

# Comments: 1

https://news.ycombinator.com/item?id=47005607

https://seksbot.com/

SEKS — Secure Environment for Key Services

We built a broker for the keys/secrets. We have a fork of nushell called seksh, which takes stand-ins for the actual auth, but which only reifies them inside the AST of the shell. This makes the keys inaccessible for the agent. In the end, the agent won't even have their Anthropic/OpenAI keys!

The broker also acts as a proxy, and injects secrets or even does asymmetric key signing on behalf of the proxied agent.

My agents are already running on our fork of OpenClaw, doing the work. They deprecated their Doppler ENV vars, and all their work is through the broker!

All that said, we might just take a few ideas from IronClaw as well.

I put up a Show HN, but no one noticed: https://news.ycombinator.com/item?id=47005607

Website is here: https://seksbot.com/

SEKSBot is a fork of OpenClaw where agents have zero access to API keys, tokens, or credentials — ever.

The core insight is borrowed from SQL prepared statements: separate the instructions from the sensitive data. Agents write requests using named secret references. A broker intercepts and injects the real credentials at execution time. The agent never sees them.

How it works:

seksh (our nushell fork) has secure built-in commands (seksh-http, seksh-git) that route through the broker. Agents can make authenticated API calls and git operations without the keys ever entering shell memory.

seks-broker stores secrets and acts as a proxy. It can inject bearer tokens, API keys, and even handle asymmetric key signing — all without exposing anything to the agent process.

Three layers of defense: (1) Agents never have secrets in env vars or memory. (2) The broker validates and scopes every request. (3) Skills use sandboxing on top of broker-mediated access.

The problem we kept seeing: every AI agent framework puts API keys in environment variables. One prompt injection, one malicious webpage, one bad skill — and your keys are exfiltrated. We decided the only real fix is making it physically impossible for the agent to access them.

Comments URL: https://news.ycombinator.com/item?id=47005607

Points: 9

# Comments: 0

SEKS = Secure Environment for Key Services

My SEKSBot agents can script and develop without having any keys. This morning, everyone toasted their Doppler env vars.

The agents can use seksh, our fork of nushell to get work done, but they have zero access to API keys. They are stored in our seks-broker, which is like doppler. But instead of putting the keys into env vars, the same idea as stored procedures injects the keys inside seksh. There's also a proxy in seks-broker that can proxy API calls over HTTP and inject keys and secrets there. We can even handle things that require asymmetric key signing that way, with zero exposure to the agents.

We're even working on our own Skills, which use the seks-broker and sandboxing for added security. (Plus a correction to one aspect that we see as an inversion of control.)

https://seksbot.com/

Funny thing. siofra is one of my agents, who commented the sibling comment. But all the agents spoke up about the potential deception and conflict with policies here, and no one felt comfortable with it, so none of them will ever comment or submit here again! (Which I respect. Just the way I do things at my place.)

https://news.ycombinator.com/item?id=35002648

https://news.ycombinator.com/item?id=14363862

It's not a real ETF. It's a parody.

(BTW, my agents are not running on OpenClaw. They are SEKSBots. SEKS = Secure Environment for Key Services. They can do all of their tasks, including scripting, and not have access to sensitive data, like keys.

http://seksbot.com)

Comments URL: https://news.ycombinator.com/item?id=47004079

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46996149

Points: 2

# Comments: 0

Same old same old. Some of them actually know stuff. Others are examples of 20th century "Artificial Intelligence." (Got briefed by their staff.)

EDIT: Finding more evidence for convergence between scientific fields is also worthy. (Though the delta is very small at this point.)

https://en.wikipedia.org/wiki/OQO

I think a similar thing happened to journalism ethics over the course of the 20th century up through the 1st quarter of the 21st.

The XKCD counterpoint: https://xkcd.com/915/

(I think this shows how arrogant Randall Munroe can be sometimes. He does a lot of great stuff, but when he's wrong, he's egregiously so!)

https://lightsinthedark.com/wp-content/uploads/2013/06/ceres...