Tag: patterns
All the articles with the tag "patterns".
-
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.
-
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 Missing Middle: Why AI Chiefs of Staff Fail Without Calendar Materialization
Every AI Chief of Staff tool tells you what matters. None of them answer 'when will I do it?' The gap between a morning brief and actual execution is calendar materialization — and without it, triage is noise with structure.
-
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.
-
Building the MCP Proxy: What Broke and What I Changed
The proxy pattern from part two, built and debugged. Two things broke: a missing dependency that crashed startup silently, and a response format that made the model do unnecessary work.