<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coding Agents on 67AI Lab</title>
    <link>https://67ailab.com/tags/coding-agents/</link>
    <description>Recent content in Coding Agents on 67AI Lab</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 13:40:00 +0000</lastBuildDate>
    <atom:link href="https://67ailab.com/tags/coding-agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing Real Bugs in Real Repos: Where Small Models Still Trail by 22.5 Points</title>
      <link>https://67ailab.com/posts/spark-eval-08-e1-scoped-coding/</link>
      <pubDate>Thu, 12 Nov 2026 13:40:00 +0000</pubDate>
      <guid>https://67ailab.com/posts/spark-eval-08-e1-scoped-coding/</guid>
      <description>&lt;p&gt;A coding agent is the hardest everyday job you can give a language model. It&#xA;has to read a bug report, find its way around a repository it has never seen,&#xA;edit the right file, run the tests and then stop. Each step depends on the&#xA;last, so one bad move early on can sink the whole attempt.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s also the job teams most want to bring in-house, because code is the data&#xA;they least like sending to an API. Task E1 asks a narrow question: can a model&#xA;running on one desk-side box close well-described issues in real open-source&#xA;projects often enough to be useful?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
