Posts
All articles on AI-native work patterns, agent infrastructure, and what actually works when running agents as real tools.
-
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.
-
Failure Modes Are the Fingerprint
Anti-patterns are more valuable than patterns. The space of things that work is large. The space of things that fail in your specific context is small and worth encoding.
-
The AI Chief of Staff Is a Fleet, Not an Agent
The AI Chief of Staff pattern is everywhere in May 2026 — and every implementation makes the same mistake. They build one agent that generates a morning brief. A real chief of staff is a fleet.
-
Markdown Is the Operating System. Everything Else Is a Render.
The AI-native file format stack is three layers: Markdown, YAML, and CSV for authoring and agent operations; PDF, DOCX, and PPTX only exist as rendered outputs at the moment of distribution. Treating rendered formats as source creates friction that compounds across every agent interaction.
-
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 Website Is Not the Product
AI crawlers are extracting content at 60,000 pages per visitor sent back. The website is becoming a fallback UI. The real distribution layer is structured, machine-readable context — and nobody is building for it yet.