<?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>Forem: Vasilescu David</title>
    <description>The latest articles on Forem by Vasilescu David (@buildingwwdavid).</description>
    <link>https://forem.com/buildingwwdavid</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3758881%2F710fec76-2eca-4f42-a4ba-f8522d8fa7f5.jpg</url>
      <title>Forem: Vasilescu David</title>
      <link>https://forem.com/buildingwwdavid</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/buildingwwdavid"/>
    <language>en</language>
    <item>
      <title>We had 20 Claude terminals open. So we built an orchestration layer.</title>
      <dc:creator>Vasilescu David</dc:creator>
      <pubDate>Sat, 07 Feb 2026 18:09:13 +0000</pubDate>
      <link>https://forem.com/buildingwwdavid/we-had-20-claude-terminals-open-so-we-built-an-orchestration-layer-l38</link>
      <guid>https://forem.com/buildingwwdavid/we-had-20-claude-terminals-open-so-we-built-an-orchestration-layer-l38</guid>
      <description>&lt;p&gt;Last month, my co-founder Ciprian and I hit peak chaos.&lt;/p&gt;

&lt;p&gt;We had 20 Claude Code terminals running. Twenty. Each working on a different part of our codebase. Tab after tab, terminal after terminal.&lt;/p&gt;

&lt;p&gt;•⁠  ⁠"Wait, which agent was working on the API?"&lt;br&gt;
•⁠  ⁠"Did I already give this one the updated context?"&lt;br&gt;
•⁠  ⁠"These two just edited the same file on different branches..."&lt;/p&gt;

&lt;p&gt;We were spending more time managing AI agents than actually building.&lt;/p&gt;

&lt;p&gt;The irony wasn't lost on us.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Breaking Point
&lt;/h2&gt;

&lt;p&gt;Here's what our workflow looked like:&lt;/p&gt;

&lt;p&gt;1.⁠ ⁠Open Claude terminal #1 for frontend&lt;br&gt;
2.⁠ ⁠Open Claude terminal #2 for backend&lt;br&gt;
3.⁠ ⁠Open Claude terminal #3 for tests&lt;br&gt;
4.⁠ ⁠Copy context between them manually&lt;br&gt;
5.⁠ ⁠Track which branch each was on (in our heads)&lt;br&gt;
6.⁠ ⁠Merge conflicts. So many merge conflicts.&lt;br&gt;
7.⁠ ⁠Lose track of everything&lt;br&gt;
8.⁠ ⁠Repeat&lt;/p&gt;

&lt;p&gt;We thought: if AI agents are supposed to 10x our productivity, why does managing them feel like a full-time job?&lt;/p&gt;

&lt;h2&gt;
  
  
  The Solution: Orcha
&lt;/h2&gt;

&lt;p&gt;So we built what we needed — an orchestration layer for AI coding agents.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;One dashboard. Multiple agents. Zero chaos.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Here's how it works:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Specialized Agents
&lt;/h3&gt;

&lt;p&gt;Instead of one AI doing everything, you deploy specialists:&lt;br&gt;
•⁠  ⁠React Developer&lt;br&gt;
•⁠  ⁠API Developer&lt;br&gt;&lt;br&gt;
•⁠  ⁠Database Expert&lt;br&gt;
•⁠  ⁠DevOps Engineer&lt;br&gt;
•⁠  ⁠QA Tester&lt;/p&gt;

&lt;p&gt;Each has their own terminal, their own branch, their own expertise.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Visual Workflows
&lt;/h3&gt;

&lt;p&gt;Define how tasks flow between agents. Drag and drop. Connect the dots.&lt;/p&gt;

&lt;p&gt;Frontend Dev → React Developer → API Developer&lt;br&gt;
                    ↓&lt;br&gt;
              Database Expert&lt;/p&gt;

&lt;p&gt;When one finishes, the next picks up automatically.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Everything Local
&lt;/h3&gt;

&lt;p&gt;Your API keys stay on your machine. Your code never touches our servers. 100% local, 100% private.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Learned
&lt;/h2&gt;

&lt;p&gt;Building this taught us a few things:&lt;/p&gt;

&lt;p&gt;1.⁠ ⁠&lt;em&gt;AI agents work better as specialists&lt;/em&gt; — A "React Developer" agent writes better React than a general-purpose agent.&lt;/p&gt;

&lt;p&gt;2.⁠ ⁠&lt;em&gt;Parallel &amp;gt; Sequential&lt;/em&gt; — Five agents working simultaneously beats one agent doing five tasks.&lt;/p&gt;

&lt;p&gt;3.⁠ ⁠&lt;em&gt;Visibility matters&lt;/em&gt; — You can't manage what you can't see. One dashboard changes everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try It Out
&lt;/h2&gt;

&lt;p&gt;We're in private beta right now, and it's free.&lt;/p&gt;

&lt;p&gt;👉 &lt;em&gt;&lt;a href="https://orcha.nl" rel="noopener noreferrer"&gt;orcha.nl&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Would love feedback from the dev community:&lt;br&gt;
•⁠  ⁠What agents would you want?&lt;br&gt;
•⁠  ⁠What workflows would save you the most time?&lt;/p&gt;

&lt;p&gt;Drop a comment or reach out. Let's figure this out together.&lt;/p&gt;




&lt;p&gt;Built by David &amp;amp; Ciprian, two devs who got tired of tab chaos.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
