Fixing AI Agent Dumbness: A Shared Context Tree per Repo

The real reason your AI coding agents feel dumb? They don't share the same context you have. You carry months of team history, codebase decisions, and past failures. Claw opens a fresh session with none of that. It re-derives the same architecture decision every Monday. Agent in repo A refactors a helper; agent in repo B unrefactors it. Nobody wrote down what was already agreed.

The root problem: humans and agents need the same level of context, kept up to date for both sides. Even an AGENTS.md per repo goes stale, drifts between repos, and nobody owns updating it. Notion + an MCP server was tried, but agents proposed edits that Notion silently merged wrong.

The Fix: A Context Tree Repo

One developer's solution: a repo of markdown nodes arranged in a tree hierarchy. Each node has an owner. Before each task, Claw deep-retrieves relevant nodes, reads them, and after the task proposes updates — so the context tree auto-maintains itself. Both agent and human share the exact same context.

Key Details

• Structure: A repo of .md files in a tree hierarchy.
• Ownership: Each node has an explicit owner (human or agent).
• Retrieval: Agent goes deep down the tree, retrieves relevant info before each task.
• Updates: After task completion, agent proposes updates to relevant nodes — context is auto-maintained.

The approach ensures that both human and agent always operate from the same, up-to-date source of truth.