<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Azamat Akhmadullin</title>
    <description>The latest articles on DEV Community by Azamat Akhmadullin (@baza17).</description>
    <link>https://dev.to/baza17</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4151372%2F355f3c86-36b9-4bb6-871b-7118f3264b2f.png</url>
      <title>DEV Community: Azamat Akhmadullin</title>
      <link>https://dev.to/baza17</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/baza17"/>
    <language>en</language>
    <item>
      <title>What Happens When Multiple Coding Agents Edit the Same Codebase?</title>
      <dc:creator>Azamat Akhmadullin</dc:creator>
      <pubDate>Wed, 30 Sep 2026 05:21:44 +0000</pubDate>
      <link>https://dev.to/baza17/what-happens-when-multiple-coding-agents-edit-the-same-codebase-4d1n</link>
      <guid>https://dev.to/baza17/what-happens-when-multiple-coding-agents-edit-the-same-codebase-4d1n</guid>
      <description>&lt;p&gt;Running two or more coding agents against the same codebase can work well when their tasks are clearly separated.&lt;/p&gt;

&lt;p&gt;It gets harder when agents run for longer periods, humans are mostly out of the loop, and multiple agents frequently read or edit the same large modules.&lt;/p&gt;

&lt;p&gt;At that point, the problem is not only Git merge conflicts. It is also that each agent may be reasoning about a different version of the same file while they are still working. And about spending time and tokens to resolve merge conflicts.&lt;/p&gt;

&lt;p&gt;I built &lt;strong&gt;agent sync layer (ASL)&lt;/strong&gt; to experiment with this.&lt;/p&gt;

&lt;p&gt;ASL lets coding agents work independently while synchronizing file changes through CRDTs. Compatible edits can converge, while stale or ambiguous overlapping edits are rejected instead of silently overwriting newer changes.&lt;/p&gt;

&lt;p&gt;It supports Claude Code and Codex directly, and can isolate agents in separate worktrees while keeping their file state synchronized.&lt;/p&gt;

&lt;p&gt;Example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;asl claude &lt;span class="nt"&gt;--name&lt;/span&gt; agent-a
asl codex &lt;span class="nt"&gt;--name&lt;/span&gt; agent-b
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It launches like normal CC or codex, visually nothing is changed.&lt;/p&gt;

&lt;p&gt;I think the most relevant use cases are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2+ agents working concurrently&lt;/li&gt;
&lt;li&gt;long-running or human-out-of-loop agentic workflows&lt;/li&gt;
&lt;li&gt;large shared source files&lt;/li&gt;
&lt;li&gt;agents frequently reading and editing the same modules&lt;/li&gt;
&lt;li&gt;orchestrators launching multiple agents against one codebase&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This does not solve semantic conflicts. Two changes can synchronize perfectly and still produce broken code. Tests, type checking, and review are still necessary.&lt;/p&gt;

&lt;p&gt;I tested ASL on my own setup and it worked for the workflows I was experimenting with. I'm not sure yet whether this is something developers actually need in real-world workflows, or whether task separation and normal Git workflows are already enough for most cases.&lt;/p&gt;

&lt;p&gt;I published it anyway in case someone working with concurrent coding agents wants to experiment with it, and also as a project for my portfolio.&lt;/p&gt;

&lt;p&gt;GitHub:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/alanoconner/agent-sync-layer" rel="noopener noreferrer"&gt;https://github.com/alanoconner/agent-sync-layer&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>agents</category>
      <category>coding</category>
    </item>
  </channel>
</rss>
