CLIs live in the same namespace as the agent, so any secrets the CLI needs access to, the agent can also exfiltrate. And access control is lightly gated by the agent's tool call policy.

For an enterprise-level deployment, it becomes quickly desirable to have a centralized MCP backbone, on which each MCP is attached to. A place you can attach policies to, log activity, and reason about access control.

Otherwise it's just FUD.

We need this also for normal usage like development environments. Or when invoking a command on a remote server.

Are you going to add support for services that don't support OIDC or this going to be a known limitation?

    nix run github:numtide/llm-agents.nix#mistral-vibe

See https://gerrit-review.googlesource.com/Documentation/note-db...

The content of the AGENTS.md is the same as what humans are looking for when contributing to a project.

https://github.com/marionebl/svg-term-cli

`nixos-rebuild build-image --image-variant vmware`

See https://nixos.org/manual/nixos/stable/#sec-image-nixos-rebui...

My assumption was that a tool like this will make it easier to keep the README.md in sync while the project evolves. Think of a `--help` section. That assumption holds true to me.

You can see it in action for example here: https://github.com/numtide/treefmt-nix?tab=readme-ov-file#su...

The best part is that it makes it easy to keep the README.md in sync when the project evolves. Just add it to the CI

There are tools like Jupyter notebooks that have all the functionalities, but their file format isn't very readable or diffable using standard terminal tools.

A while back I wrote https://github.com/zimbatm/mdsh to explore the space. Voiden.md looks like a fancier version of that.

The main reason even Microsoft gave up and rebased their browser on top of Chrome is because of the breakneck speed at which Google introduces new standards and features to the ecosystem. Having them be forced to slow down might be a good thing for browser diversity and the future of the Internet.

I'm not going to invoke the slippery slope argument, but what distinguishes Go from the pack is how explicit it is. It can make it more tedious to write, but also much easier to follow as a reader.