Tag: infrastructure
All the articles with the tag "infrastructure".
-
What Happens When an AI Agent Manages Your Password Vault
I used Claude Code and the 1Password CLI to reorganize 690 credentials — four vaults, 400+ tagged items, a GitHub issue filed from the terminal. Here's what worked, what broke, and what it means for AI-native credential management.
-
1Password Is Infrastructure, Not a Password Manager
1Password just announced credential infrastructure for AI agents. The pattern already works today — personal account, existing CLI, GitHub Actions pulling exactly the credentials each workflow needs from a vault scoped to its purpose. Here's what that looks like and why it matters.
-
The Builder Stack Nobody Told You 1Password Covers
1Password gets described as a password manager. It also replaces SSH key files, GPG for git signing, .env files, AWS credential storage, and scattered Secrets Manager entries — all from one vault, all behind a single biometric prompt.
-
The Enterprise MCP Pattern: Proxy, Aggregate, Host
There are 58 public MCP servers in the awslabs catalog covering cloud infrastructure, databases, AI/ML, and ops tooling. Here's the enterprise pattern: proxy them locally, then host the proxy behind a gateway so every developer in your org gets them without setup.
-
The Meta-Tool Pattern: Teaching Your Agent to Discover Its Own Tools
The MCP token tax has a fix. The solution isn't fewer tools — it's a smarter way to load them. Here's the pattern.
-
Build vs. Buy for AI Knowledge Infrastructure: Capability First, Cost Second
SaaS platforms auto-generate MCP servers. But auto-generated MCP does text search. If your use case requires metadata-filtered retrieval, you're comparing different architectures — not different feature sets. Capability first, cost second.
-
Docs-as-Code Is Now the Standard for Knowledge Distribution
Engineering teams have used docs-as-code for a decade. In 2025, AI closed both the write path and the read path — contribution friction dropped to zero, and MCP plus llms.txt made knowledge retrievable at the point of work. For the first time, GTM and knowledge teams can match engineering velocity for maintaining artifacts. Docs-as-code is no longer an engineering practice. It's the de facto standard.
-
llms.txt — Making Your Site Navigable by Agents
HTML was designed for browsers. llms.txt is the interface layer that makes your site a first-class citizen in agent workflows — discoverable, consumable, and citable in a single request.