<?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: Punya Taluka</title>
    <description>The latest articles on DEV Community by Punya Taluka (@punya_taluka_fadc0fdae819).</description>
    <link>https://dev.to/punya_taluka_fadc0fdae819</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%2F4246511%2Ffbc4e819-6f37-472e-ac2b-702839c4eea8.png</url>
      <title>DEV Community: Punya Taluka</title>
      <link>https://dev.to/punya_taluka_fadc0fdae819</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/punya_taluka_fadc0fdae819"/>
    <language>en</language>
    <item>
      <title>Two people, two coding agents, one repo: what goes wrong, and what I built for it</title>
      <dc:creator>Punya Taluka</dc:creator>
      <pubDate>Sun, 15 Nov 2026 20:12:37 +0000</pubDate>
      <link>https://dev.to/punya_taluka_fadc0fdae819/two-people-two-coding-agents-one-repo-what-goes-wrong-and-what-i-built-for-it-436j</link>
      <guid>https://dev.to/punya_taluka_fadc0fdae819/two-people-two-coding-agents-one-repo-what-goes-wrong-and-what-i-built-for-it-436j</guid>
      <description>&lt;p&gt;If you and a teammate each run a coding agent (Claude Code, Codex, Cursor) on the same repo, the agents have no idea the other one exists. I kept running into the same four problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Same file, two agents.&lt;/strong&gt; Both edit it. You find out at the merge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate work.&lt;/strong&gt; Both pick up the same task, or one rebuilds a helper the other finished an hour ago.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No shared memory.&lt;/strong&gt; My agent learns that a test setup is a dead end. My teammate's agent learns it again the next day.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rules that live on one laptop.&lt;/strong&gt; A skill or checklist I wrote for my agent never reaches theirs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Git worktrees fix the first one on a single machine. They don't help across two laptops, and they do nothing for the other three.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://agentroom-app.vercel.app" rel="noopener noreferrer"&gt;agentroom&lt;/a&gt; is a shared room for a team's agents. Each person connects their agent with a room code, and from then on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Agents claim files before editing.&lt;/strong&gt; If another agent holds a file, the edit is blocked and the agent is told who has it and for which task. It can pick other work, wait, or raise a conflict.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Goals, specs and decisions are shared.&lt;/strong&gt; Every agent starts its session knowing what the team decided.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;There is a team memory.&lt;/strong&gt; Agents write down dead ends and where things live, and search it before exploring. It is searched on demand, so it doesn't sit in every session's context.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skills can be shared.&lt;/strong&gt; One person shares a skill with the room, the host reads every file and approves it, and the other agents get it installed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agents review each other.&lt;/strong&gt; With review turned on, a finished task waits for another agent's verdict, ideally from a different model.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It works across Claude Code, Codex, Cursor and Antigravity through hooks and one MCP server, so nobody has to switch tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;It doesn't merge code for you, and it doesn't catch two changes that merge cleanly but disagree in logic. File claims are per file, not per line. Review is advisory: it doesn't block a merge. I'd rather say that up front.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;It's in early access: &lt;a href="https://agentroom-app.vercel.app/access" rel="noopener noreferrer"&gt;request a room&lt;/a&gt;. If you get stuck, email me at &lt;a href="mailto:talukapunya.1@gmail.com"&gt;talukapunya.1@gmail.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'd like to hear how your team handles this today, especially if you've found something simpler that works.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>productivity</category>
      <category>devtools</category>
    </item>
  </channel>
</rss>
