# ai-agent

Every new session, your AI agent forgets everything. Claude Code's leaked source hid a three-layer memory architecture and a design principle — 'Memory is hint, not truth' — that changes how you think about building agents. Here's the full breakdown.

You spent months building a powerful AI agent. It just sits there waiting for you to say something. That's not a technical problem — it's a design philosophy problem. From KAIROS's Heartbeat Pattern to OpenClaw's background sessions, this is about when to let your agent decide to act on its own.

Anthropic engineer Thariq makes a blunt case for AI agents using the file system as state. The point is not just persistence — it is giving agents a place to search, verify, iterate, and recover instead of trying to one-shot everything from memory.

Anthropic engineer Thariq argues that even non-coding agents need bash. Saving intermediate results to files lets an agent search, compose API workflows, retry, and verify its own work — but it also raises real questions about security, data exfiltration, and container-based deployment.

Teknium announces Browser Use as an official browser tool provider for Hermes-Agent. A quoted user reports that after connecting Hermes to Browser Use, it can access their social media accounts while retaining context about their codebase, tone, and workflows.

Nvidia is rumored to unveil an AI agent-optimized CPU at this week's GTC. The bigger question: is hardware design shifting from 'for humans' to 'for AI agents'?