Agentics: AI enablement requires managed agent runtimes

Agentics: AI enablement requires managed agent runtimesAI enablement in enterprise requires nothing less than fully managed agent runtimestheahuraApr 23, 2026113ShareMy mom called me over the weekend. Normally when mom calls, it’s to lovingly tell me to throw out my entire wardrobe or to ask when I’m going to buy her a penthouse. She does this ~3 times a week. Typical mom things. Imagine my surprise when I pick up the phone and the first thing out of her mouth is “actually I’m going to call you on Whatsapp video because Claude Code isn’t working.” And then for the next hour I get my mom setup on Claude Code through a shaky horizontal phone video stream, guest starring Dad as the camera man. Apparently mom’s boss’s boss’s boss’s boss announced a company wide mandate that everyone had to install and use Claude Code, and my mom had to figure out how to make the thing work in Windows powershell. It’s official guys, AI has hit the mainstream.12 Grams of Carbon is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.SubscribeThe actual install was pretty straightforward.1 Took about 5 minutes. Explaining how to configure the thing took another 55. “Most of your configuration should be in SKILL files, which need to live in the skills directory. Also you need a CLAUDE.md file, which is basically like a SKILL file but it gets added to every prompt…what do I mean by that? No skills don’t actually get added to the prompt, the agent has to choose to read those, the skill descriptions get added to the system prompt. No they don’t exactly get added to the CLAUDE.md, but they kinda do, they are both part of the system prompt…ok yes subagents are a different thing than skills, but slash commands are the same thing as skills. But it’s all markdown. No, subagents also get access to your CLAUDE.md and your skills. But that also gets added to the CLAUDE.md. Also you have different sets of these possibly from every folder. Some of these will live in your git repo. No the agent won’t pick up the ones in the git repo automatically unless you copy the files in the right place. What’s a git repo? uh…”agent, tools, context rot, skills, mcp server, mcp client, subagents, memories, rag, AGENTS.md, hooks, rules, plugins, acp, orchestrator, yolo-mode, system prompt, chain of thought, prompt injection, extended thinking, tokens, computer use, spec-driven-development, and whatever the hell gastown isThis shit is way too hard and way too unintuitive.The problem is that there isn’t any stability. The macro environment is constantly changing, with Anthropic et al shipping new foot guns basically daily. Here’s a great example. Claude Code uses CLAUDE.md. Codex CLI uses AGENTS.md. Gemini uses both AGENTS.md and GEMINI.md. Most people have, at this point, switched to AGENTS.md support for standardization. But Claude Code, the industry leader for this sort of thing and the one that every CEO seems to insist on using, forces it’s own standard.2And it is just way too easy for a given user to totally screw their environment up. “Claude, add a skill to automatically load my AWS credentials” and now you have a security leak that in two months will take out all the data centers in Wisconsin, whoops.I can’t imagine being a TL in this setting. Every TL I know eventually reaches for some kind of stable cloud dev box environment, because debugging someone’s python env by spending 4 hours over their shoulder is a great…

This excerpt is published under fair use for community discussion. Read the full article at 12gramsofcarbon.