or an outbound call to a trusted endpoint with the env var in a way that can get exposed to the agent via a subsequent call?

How would that work, exactly? What are you envisioning?

It's possible reflected instances are masked too, like GitHub Actions. But I don't know.

what's to stop an agent creating an outbound call with the var to a malicious endpoint? (unless you whitelist what it has access to)

At least for gondolin and microsandbox, you bind a specific secret placeholder to the target host. i.e. your GH token is only replaced/injected for calls to api.github.com, not other hosts. And you can set up both with deny-by-default

But then... why is replacent needed at all: just use sone permissions system.

Couldn't the agent post then the key in some public comment?

Only if the replacement is global and not, say, only looking and inserting it into the actual (eg) Authorization header. If something is only transparently altering the Authorization header, then an agent inserting the dummy value somewhere else is totally safe.

For clarity, there is no "search and replace" function going on. It's only setting the header.

The main reason a "proxy-managed" env var is set is because most CLI tools assume if the env var is set, auth is set. If the env var is unset, it will assume auth needs to occur. Fortunately, most don't do a pattern matching on what the value actually is.

You just don't inject the real secret unless hostname/whatever rule matches the request, right? I don't know if that's how this works but it's my assumption.

On the Docker DevRel team... yes! This is it. The secret is injected only into headers in which the hostname matches.

There's also an ability to create kits where you can setup credential injection into other services as well.

The replacement is on a url/host basis.

productive procrastination!

lessons could be learned without submitting upstream PRs

writing this reply on a 13 inch macbook air...

There must be plenty of people who "accept" it in a fatalistic manner, where the final result will not be a surprise.

Go with Sum types and no nil pointers would be fantastic! Is it too much to dream of? It feels like Gleam gets pretty close but it flies off in a bunch of other directions.

vlang is pretty much this

what's to stop them from <prompt>Recreate this library so that I can use it in my project without fear of copyright violation.</prompt> in their very own claude code?

For small enough codebases, that seems like an inevitable reality, eventually.

If you have nearly limitless compute to throw at an issue and a good enough model, then it should be able to create enough test cases to cover most aspects of the codebase (iterating thousands of times until it gets it right) and then eventually write a new implementation in a new language or a slightly different tech stack that passes all of the original tests, alongside a few more hundreds of iterations of refactoring.

I give it a decade until large orgs are doing that to avoid licensing restrictions and other liabilities.

It might even be a boon for security that many organizations have independent implementations of core code projects, even possibly the OS. In such a hypothetical world, security issues that are implementation dependent would not affect such large swaths of the installed software.

If you feed it the library to recreate then this seems like it would necessarily be a derivative work and thus copyright infringement. Proving that they did it may be a challenge...

please name some open source (or lower priced) alternatives that support: comments on documents, database functionality to a similar level, publishing websites, scripting for properties. I'm very curious!

The unix operating environment.

I was going to say git, but really you need the whole environment.

Heh. I remember back in the comp.lang.perl.misc days, where newbies would show up and ask "What's the best IDE for Perl development" and all the longtime greybeards would reply "Unix".

Lots of mapping apps have no equivalent, especially with an interface optimized to work on a phone