<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>AXME Blog</title><description>Technical articles about AI agent infrastructure — durable execution, observability, and developer tools.</description><link>https://blog.axme.ai/</link><language>en-us</language><item><title>After 100 Sessions: What Persistent Memory Changed About How I Use Claude Code</title><link>https://blog.axme.ai/after-100-sessions/</link><guid isPermaLink="true">https://blog.axme.ai/after-100-sessions/</guid><description>Before: re-explain the project every session, watch the same mistakes, fix the same bugs twice. After 100 sessions with persistent memory: different patterns, measurable time savings, one problem I did not expect.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>productivity</category></item><item><title>CLAUDE.md Is a Read-Only File. Your Coding Agent Needs Writable Memory.</title><link>https://blog.axme.ai/claude-md-is-read-only/</link><guid isPermaLink="true">https://blog.axme.ai/claude-md-is-read-only/</guid><description>Everyone puts project context in CLAUDE.md. It&apos;s static, it grows, nobody maintains it, and it becomes a graveyard of stale rules. Writable memory with an audit trail is a different shape of solution.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>memory</category></item><item><title>You&apos;ve Had This Conversation With Claude Code 47 Times</title><link>https://blog.axme.ai/conversation-with-claude-code-47-times/</link><guid isPermaLink="true">https://blog.axme.ai/conversation-with-claude-code-47-times/</guid><description>Every session starts the same way: explaining your stack, your deploy flow, your conventions. You&apos;ve said it forty times. The agent keeps nodding. Here&apos;s why re-explaining every session is the wrong fix.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>productivity</category></item><item><title>Decisions Are Not Memories. Most Agent Memory Systems Confuse Them.</title><link>https://blog.axme.ai/decisions-are-not-memories/</link><guid isPermaLink="true">https://blog.axme.ai/decisions-are-not-memories/</guid><description>&apos;I learned we use Postgres&apos; and &apos;we decided Postgres over MySQL because of JSON support&apos; are different data. One is a fact. The other is a contract. Mixing them is why agent memory drifts.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>ai</category><category>agents</category><category>memory</category><category>architecture</category></item><item><title>The First Session With a New Codebase: What AXME Code Does Before the Agent Starts</title><link>https://blog.axme.ai/first-session-new-codebase/</link><guid isPermaLink="true">https://blog.axme.ai/first-session-new-codebase/</guid><description>Stack detection, structure scanning, glossary extraction, safety rule seeding. What happens in the first 30 seconds of a new AXME Code setup, why each step matters, and what happens if you skip it.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>onboarding</category></item><item><title>The 4 Types of Context Your AI Coding Agent Needs</title><link>https://blog.axme.ai/four-types-of-context/</link><guid isPermaLink="true">https://blog.axme.ai/four-types-of-context/</guid><description>Most agents treat all context as &apos;stuff in the context window&apos;. But facts, patterns, project state, and references have different lifecycles and different retrieval rules. Mixing them is why agents feel dumb.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>ai</category><category>agents</category><category>memory</category><category>context</category></item><item><title>Multi-Repo Workspaces Break Claude Code. Here&apos;s the Fix.</title><link>https://blog.axme.ai/multi-repo-workspaces-break-claude-code/</link><guid isPermaLink="true">https://blog.axme.ai/multi-repo-workspaces-break-claude-code/</guid><description>You have 5 repos in one workspace. Each has its own conventions. A single CLAUDE.md is the wrong shape. Per-repo storage with a workspace root is the pattern that actually scales.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>monorepo</category></item><item><title>Your AI Coding Agent Keeps Running `git push --force`. Prompts Don&apos;t Fix This.</title><link>https://blog.axme.ai/prompts-dont-stop-force-push/</link><guid isPermaLink="true">https://blog.axme.ai/prompts-dont-stop-force-push/</guid><description>You put &apos;never force push&apos; in CLAUDE.md. The agent force-pushed anyway. Here&apos;s why prompt-level safety rules fail and what tool-level enforcement actually looks like.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>safety</category></item><item><title>Stop Writing CLAUDE.md Files. Write Decisions Instead.</title><link>https://blog.axme.ai/stop-writing-claude-md/</link><guid isPermaLink="true">https://blog.axme.ai/stop-writing-claude-md/</guid><description>CLAUDE.md is a passive artifact. Decisions are active rules with enforcement levels, supersede chains, and audit history. Here&apos;s why I stopped maintaining CLAUDE.md and what I switched to.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>workflow</category></item><item><title>Subagents Without Context: Claude Code&apos;s Silent Bug</title><link>https://blog.axme.ai/subagents-lose-context/</link><guid isPermaLink="true">https://blog.axme.ai/subagents-lose-context/</guid><description>When Claude Code spawns a subagent to run a task in parallel, the subagent starts fresh. It doesn&apos;t inherit the parent&apos;s memory. Work gets done, but context is lost. Here&apos;s the fix, and why it&apos;s fragile.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>subagents</category></item><item><title>I Went on Vacation. My Agent Came Back to an Empty Project.</title><link>https://blog.axme.ai/vacation-empty-project-session-handoff/</link><guid isPermaLink="true">https://blog.axme.ai/vacation-empty-project-session-handoff/</guid><description>Five days off. Session handoff gone. Half a week of decisions forgotten. Here&apos;s the &apos;what was I doing yesterday&apos; problem and why session close is a ritual that matters.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>workflow</category></item><item><title>We Built AXME Code With AXME Code. Here&apos;s What the Memory File Looks Like.</title><link>https://blog.axme.ai/we-built-axme-code-with-axme-code/</link><guid isPermaLink="true">https://blog.axme.ai/we-built-axme-code-with-axme-code/</guid><description>Six months of dogfooding. Real memories, real decisions, real safety rules from our own repo. What patterns emerged. What we threw away. What surprised us.</description><pubDate>Sat, 11 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>dogfood</category></item><item><title>Your AI Agent Crashed at Step 47. Why Isn&apos;t Crash Recovery the Default?</title><link>https://blog.axme.ai/ai-agent-crash-recovery-default/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-crash-recovery-default/</guid><description>Your agent ran 47 steps of a 50-step pipeline. Then it crashed. The state is gone. Every framework says you should have configured checkpointing. Why isn&apos;t durability built in?</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>durability</category></item><item><title>How I Fixed Claude Code&apos;s Amnesia (Actually)</title><link>https://blog.axme.ai/claude-code-amnesia/</link><guid isPermaLink="true">https://blog.axme.ai/claude-code-amnesia/</guid><description>Claude Code forgets your project every session. CLAUDE.md helps, but it doesn&apos;t scale. I built an MCP server plugin that gives Claude Code persistent memory, decisions, and safety guardrails.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>code</category><category>claude</category><category>ai</category><category>devtools</category><category>productivity</category></item><item><title>How to Add Human Approval to AI Agent Workflows Without Building It Yourself</title><link>https://blog.axme.ai/human-approval-ai-agent-workflow/</link><guid isPermaLink="true">https://blog.axme.ai/human-approval-ai-agent-workflow/</guid><description>Adding a human approval step to an AI agent workflow means building a notification service, reminder scheduler, escalation chain, and webhook handler. Or you can use 4 lines of code.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>humanintheloop</category></item><item><title>How to Stop a Rogue AI Agent in Production</title><link>https://blog.axme.ai/stop-rogue-ai-agent-production/</link><guid isPermaLink="true">https://blog.axme.ai/stop-rogue-ai-agent-production/</guid><description>Your AI agent went rogue at 3am. It&apos;s running on multiple instances across regions. There&apos;s no terminal to Ctrl+C. You need a kill switch that works in under 1 second, enforced at the infrastructure level.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>python</category><category>agents</category><category>monitoring</category></item><item><title>Temporal Alternative Without the Cluster and Determinism Constraints</title><link>https://blog.axme.ai/temporal-alternative-no-cluster/</link><guid isPermaLink="true">https://blog.axme.ai/temporal-alternative-no-cluster/</guid><description>Temporal is the go-to for durable execution. But it requires a cluster and forces determinism constraints on your workflow code. Here&apos;s an alternative that gives you durability through a managed API with none of those trade-offs.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>cloud</category><category>temporal</category><category>python</category><category>durableexecution</category><category>workflow</category></item><item><title>You Have 50 AI Agents Running. Can You Name Them All?</title><link>https://blog.axme.ai/ai-agent-fleet-dashboard/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-fleet-dashboard/</guid><description>AI agents are multiplying across your org. Different clouds, different frameworks, different teams. Without a fleet dashboard, you&apos;re flying blind.</description><pubDate>Sun, 05 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>dashboard</category><category>monitoring</category><category>agents</category></item><item><title>Your AI Agent Spent $500 Overnight and Nobody Noticed</title><link>https://blog.axme.ai/ai-agent-cost-monitoring/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-cost-monitoring/</guid><description>AI agents call LLMs. LLMs cost money per token. Nobody tracks it per agent. One runaway loop and your OpenAI bill is a disaster.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>python</category><category>llm</category><category>monitoring</category></item><item><title>You Deployed 30 AI Agents. Can You Answer These 5 Questions About Them?</title><link>https://blog.axme.ai/ai-agent-governance-platform/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-governance-platform/</guid><description>Most teams can&apos;t tell you which agents are running, how much they&apos;ve spent, or how to shut one down. Here&apos;s what a governance platform for AI agents looks like.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>governance</category><category>agents</category><category>enterprise</category></item><item><title>3 of Your AI Agents Crashed and You Found Out From Customers</title><link>https://blog.axme.ai/ai-agent-health-monitoring/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-health-monitoring/</guid><description>Your agents are running across 4 machines. One dies. No alert. No log. You find out 3 hours later from a customer complaint. Here&apos;s how to fix that.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>python</category><category>monitoring</category><category>devops</category></item><item><title>Your AI Agent Stopped Responding 2 Hours Ago. Nobody Noticed.</title><link>https://blog.axme.ai/ai-agent-heartbeat-monitoring/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-heartbeat-monitoring/</guid><description>Container is green. Process is running. But your agent stopped processing work 2 hours ago. Heartbeat monitoring catches what health checks miss.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>monitoring</category><category>python</category><category>agents</category></item><item><title>Your AI Agent Is Running Wild and You Can&apos;t Stop It</title><link>https://blog.axme.ai/ai-agent-kill-switch/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-kill-switch/</guid><description>AI agents go rogue. They send thousands of emails, make unauthorized API calls, burn through budgets. You need a kill switch that works in under 1 second.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>python</category><category>agents</category><category>monitoring</category></item><item><title>Your AI Agent Did Something It Wasn&apos;t Supposed To. Now What?</title><link>https://blog.axme.ai/ai-agent-policy-enforcement/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-policy-enforcement/</guid><description>AI agents ignore restrictions in prompts. Gateway-enforced action policies block unauthorized actions before they reach the agent - no prompt injection can bypass it.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>security</category><category>agents</category><category>governance</category></item><item><title>Your AI Agent Made 10,000 API Calls in an Hour. Here&apos;s How to Stop That.</title><link>https://blog.axme.ai/ai-agent-rate-limiting/</link><guid isPermaLink="true">https://blog.axme.ai/ai-agent-rate-limiting/</guid><description>One runaway retry loop. 10,000 API calls. $130 in LLM costs. No rate limit fired because you never built one. Here&apos;s how to add centralized rate and cost limiting to AI agents.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>mesh</category><category>ai</category><category>ratelimiting</category><category>python</category><category>agents</category></item><item><title>A2A Tells Agents How to Talk. It Doesn&apos;t Tell Them What Happens When Things Break.</title><link>https://blog.axme.ai/a2a-without-durable-lifecycle/</link><guid isPermaLink="true">https://blog.axme.ai/a2a-without-durable-lifecycle/</guid><description>Google&apos;s A2A protocol handles agent communication. But crash recovery, retries, timeouts, and human approval gates? That&apos;s still on you. Unless you add a lifecycle layer.</description><pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>a2a</category></item><item><title>Your Agent Has Been Stuck for 3 Hours and Nobody Knows</title><link>https://blog.axme.ai/agent-timeout-escalation/</link><guid isPermaLink="true">https://blog.axme.ai/agent-timeout-escalation/</guid><description>API call hangs. Agent blocks. No timeout fires. No one gets paged. The default behavior in most agent frameworks is silence. Here&apos;s how to fix that.</description><pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>reliability</category></item><item><title>A Two-Step Approval Chain Shouldn&apos;t Need a Workflow Engine</title><link>https://blog.axme.ai/approval-chain-without-workflow-engine/</link><guid isPermaLink="true">https://blog.axme.ai/approval-chain-without-workflow-engine/</guid><description>Manager approves, then finance approves. Simple enough to describe. 300 lines of code to build. Unless your platform handles approval chains natively.</description><pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>workflow</category><category>python</category><category>backend</category><category>architecture</category></item><item><title>Your AutoGen Agents Can&apos;t Talk Across Machines. Here&apos;s the Missing Piece.</title><link>https://blog.axme.ai/autogen-agents-different-machines/</link><guid isPermaLink="true">https://blog.axme.ai/autogen-agents-different-machines/</guid><description>AutoGen handles multi-agent conversations beautifully - inside one process. Put agents on different machines and you&apos;re back to building message brokers from scratch.</description><pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>autogen</category></item><item><title>I Stopped Building Webhook Retry Logic. Here&apos;s What I Use Instead.</title><link>https://blog.axme.ai/stopped-building-webhook-retry/</link><guid isPermaLink="true">https://blog.axme.ai/stopped-building-webhook-retry/</guid><description>Exponential backoff, jitter, dead letter queues, idempotency keys, HMAC verification - all to deliver one message reliably. There are better options now.</description><pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>webhooks</category><category>python</category><category>backend</category><category>architecture</category></item><item><title>Your AI Agent Crashed at Step 47. Now What?</title><link>https://blog.axme.ai/agent-crashed-at-step-47/</link><guid isPermaLink="true">https://blog.axme.ai/agent-crashed-at-step-47/</guid><description>AI agents do multi-step work. They crash. The state is gone. Here&apos;s how to make agent operations durable without writing checkpoint code.</description><pubDate>Thu, 26 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>durability</category></item><item><title>Why Your AI Agent Shouldn&apos;t Block When It Needs Human Approval</title><link>https://blog.axme.ai/agent-shouldnt-block-on-approval/</link><guid isPermaLink="true">https://blog.axme.ai/agent-shouldnt-block-on-approval/</guid><description>AI agents get stuck waiting for humans. There&apos;s a better pattern than blocking - async approval with reminders, escalation, and timeout.</description><pubDate>Thu, 26 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>ai</category><category>python</category><category>agents</category><category>humanintheloop</category></item><item><title>What Temporal Can&apos;t Do: Human Approval Mid-Workflow</title><link>https://blog.axme.ai/what-temporal-cant-do/</link><guid isPermaLink="true">https://blog.axme.ai/what-temporal-cant-do/</guid><description>Temporal gives you durable execution. But adding a human approval step mid-workflow requires building a signal handler, notification service, and UI. There&apos;s a simpler way.</description><pubDate>Thu, 26 Mar 2026 00:00:00 GMT</pubDate><category>cloud</category><category>temporal</category><category>python</category><category>workflow</category><category>durableexecution</category></item></channel></rss>