<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>tamer.ai blog</title>
  <subtitle>Field notes on agentic engineering, kernel sandboxes and human-in-the-loop AI for coding agents.</subtitle>
  <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/"/>
  <link rel="self" type="application/atom+xml" href="https://tamer.ai/feed.xml"/>
  <id>https://tamer.ai/en/blog/</id>
  <updated>2026-06-15T00:00:00Z</updated>
  <author>
    <name>tamer team</name>
    <uri>https://tamer.ai</uri>
  </author>
  <rights>BSL 1.1 — Apache 2.0 after 4 years</rights>
  <entry>
    <title>Beyond the Context Window: The Case for Surgical Codebase Investigation</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-06-15-beyond-the-context-window-surgical-investigation/"/>
    <id>https://tamer.ai/en/blog/2026-06-15-beyond-the-context-window-surgical-investigation/</id>
    <published>2026-06-15T00:00:00Z</published>
    <updated>2026-06-15T00:00:00Z</updated>
    <author>
      <name>fred</name>
    </author>
    <summary type="text">Dumping your entire repo into a 1M token context window is a recipe for drift. Learn why Tamer treats the filesystem as the source of truth, using surgical investigation to maintain high-signal supervision.</summary>
  </entry>
  <entry>
    <title>Tamer is not a Claude alternative. It&#39;s a multiplier on top.</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-06-10-tamer-is-not-a-claude-alternative/"/>
    <id>https://tamer.ai/en/blog/2026-06-10-tamer-is-not-a-claude-alternative/</id>
    <published>2026-06-10T00:00:00Z</published>
    <updated>2026-06-10T00:00:00Z</updated>
    <author>
      <name>fred</name>
    </author>
    <summary type="text">You keep your Claude Max / Gemini Advanced subscription. Tamer orchestrates the agents you already pay for — sharper specs, drift detection, and an audit trail SOC teams can actually use.</summary>
  </entry>
  <entry>
    <title>The 7-section Self-Critique Gate: how we automate trust</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/the-7-section-self-critique-gate/"/>
    <id>https://tamer.ai/en/blog/the-7-section-self-critique-gate/</id>
    <published>2026-05-31T00:00:00Z</published>
    <updated>2026-05-31T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">To move fast, you must be your own harshest critic. Inside the 7-section block that tamer enforces on every single Work Item [DONE] event.</summary>
  </entry>
  <entry>
    <title>Tamer&#39;s multi-agent supervision patterns: what we learned in 12 weeks</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/tamer-multi-agent-supervision-patterns/"/>
    <id>https://tamer.ai/en/blog/tamer-multi-agent-supervision-patterns/</id>
    <published>2026-05-31T00:00:00Z</published>
    <updated>2026-05-31T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">Three patterns that turned a chaotic swarm of agents into a reliable production pipeline.</summary>
  </entry>
  <entry>
    <title>Tamer + GitHub Copilot CLI: an honest field report</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/tamer-copilot-field-report/"/>
    <id>https://tamer.ai/en/blog/tamer-copilot-field-report/</id>
    <published>2026-05-31T00:00:00Z</published>
    <updated>2026-05-31T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">We tested the integration of GitHub Copilot CLI as a tamer worker. Here is why, despite the model&#39;s power, automation still stumbles on implementation details.</summary>
  </entry>
  <entry>
    <title>Multi-agent orchestration: when stale state lies</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/multi-agent-stale-state/"/>
    <id>https://tamer.ai/en/blog/multi-agent-stale-state/</id>
    <published>2026-05-31T00:00:00Z</published>
    <updated>2026-05-31T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">How a 16-day bug in tamer&#39;s worker discovery taught us that in multi-agent systems, the filesystem is a liar. The move to server-side live truth.</summary>
  </entry>
  <entry>
    <title>The 2-day cadence: why our own blog slipped 14 days</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2-day-cadence-slipped/"/>
    <id>https://tamer.ai/en/blog/2-day-cadence-slipped/</id>
    <published>2026-05-31T00:00:00Z</published>
    <updated>2026-05-31T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">The irony of automation: tamer promises a breakneck delivery cadence, but we missed our own goal. Here is why, and what we changed.</summary>
  </entry>
  <entry>
    <title>Total transparency: why the terminal is AI&#39;s best ally</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-05-17-terminal-transparency-cost-control/"/>
    <id>https://tamer.ai/en/blog/2026-05-17-terminal-transparency-cost-control/</id>
    <published>2026-05-17T00:00:00Z</published>
    <updated>2026-05-17T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">AI shouldn&#39;t be a black box. Discover why tamer prioritizes Standard Input (STDIN) and respects your existing subscriptions.</summary>
  </entry>
  <entry>
    <title>Building tamer&#39;s spec-completeness v2 — a 5-axis study</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-05-13-building-tamer-spec-completeness-v2-five-axis-study/"/>
    <id>https://tamer.ai/en/blog/2026-05-13-building-tamer-spec-completeness-v2-five-axis-study/</id>
    <published>2026-05-13T00:00:00Z</published>
    <updated>2026-05-13T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">Five axes, five iterations each. How we turned &#39;is this spec good enough?&#39; from a vibe into a checklist that a Master Agent can refuse a Work Item against.</summary>
  </entry>
  <entry>
    <title>Anatomy of a [DONE] event that never arrived</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-05-09-anatomy-of-a-done-event-that-never-arrived/"/>
    <id>https://tamer.ai/en/blog/2026-05-09-anatomy-of-a-done-event-that-never-arrived/</id>
    <published>2026-05-09T00:00:00Z</published>
    <updated>2026-05-09T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">Four levels of root cause for why an agent that finishes its work stays invisible.</summary>
  </entry>
  <entry>
    <title>Why your AI agent is silently degrading your codebase</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-05-07-why-your-ai-agent-is-silently-degrading-your-codebase/"/>
    <id>https://tamer.ai/en/blog/2026-05-07-why-your-ai-agent-is-silently-degrading-your-codebase/</id>
    <published>2026-05-07T00:00:00Z</published>
    <updated>2026-05-07T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">75% of AI agents see their regression rate grow over time. Here&#39;s how to avoid it.</summary>
  </entry>
  <entry>
    <title>Spec is the bottleneck, not the model</title>
    <link rel="alternate" type="text/html" href="https://tamer.ai/en/blog/2026-05-05-spec-is-the-bottleneck/"/>
    <id>https://tamer.ai/en/blog/2026-05-05-spec-is-the-bottleneck/</id>
    <published>2026-05-05T00:00:00Z</published>
    <updated>2026-05-05T00:00:00Z</updated>
    <author>
      <name>tamer team</name>
    </author>
    <summary type="text">Once model capability passes a threshold, code quality depends on the completeness of the specification — not the intelligence of the model. A field note from tamer&#39;s design log.</summary>
  </entry>
</feed>
