<?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: Ritik Kumar</title>
    <description>The latest articles on DEV Community by Ritik Kumar (@ritikk_kumarr).</description>
    <link>https://dev.to/ritikk_kumarr</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%2F4144877%2Fa22cc338-bb27-4723-b844-df96470b9495.jpeg</url>
      <title>DEV Community: Ritik Kumar</title>
      <link>https://dev.to/ritikk_kumarr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ritikk_kumarr"/>
    <language>en</language>
    <item>
      <title>I run marketing with 7 AI agents. The hardest part is keeping them on the same page.</title>
      <dc:creator>Ritik Kumar</dc:creator>
      <pubDate>Sat, 26 Sep 2026 21:56:05 +0000</pubDate>
      <link>https://dev.to/ritikk_kumarr/i-run-marketing-with-7-ai-agents-the-hardest-part-is-keeping-them-on-the-same-page-34ec</link>
      <guid>https://dev.to/ritikk_kumarr/i-run-marketing-with-7-ai-agents-the-hardest-part-is-keeping-them-on-the-same-page-34ec</guid>
      <description>&lt;p&gt;I handle growth for a small AI product. To keep up with LinkedIn, X, SEO articles and outreach, I set up a separate AI agent for each job. One writes LinkedIn posts, one writes replies on X, one plans blog articles, one helps with outreach, and one plans my day.&lt;/p&gt;

&lt;p&gt;On paper this sounds like a small team. In practice, I spend a lot of my day doing one thing: explaining the same context again and again.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem I kept running into
&lt;/h2&gt;

&lt;p&gt;Every agent starts with a blank head. Each time I open a new chat, I have to tell it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What the product does&lt;/li&gt;
&lt;li&gt;Who we are trying to reach&lt;/li&gt;
&lt;li&gt;Which words we never use&lt;/li&gt;
&lt;li&gt;What we posted yesterday&lt;/li&gt;
&lt;li&gt;What changed in the plan this week&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The LinkedIn agent does not know what the X agent wrote this morning. The planning agent does not know that a launch date moved. If I forget to mention something, the output looks fine but is wrong in small ways.&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;1. One giant prompt with everything in it.&lt;/strong&gt;&lt;br&gt;
It worked for about a week. Then the plan changed, and I had to update the same text in five places. Half the time I forgot one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Shared documents inside a project.&lt;/strong&gt;&lt;br&gt;
Better. Each agent could read the same master doc. But the docs got long, some parts went stale, and agents still had no idea what the other agents had done.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Writing a short "today" note by hand.&lt;/strong&gt;&lt;br&gt;
This helped the most, but it is manual work every morning. It also depends on me remembering everything.&lt;/p&gt;

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

&lt;p&gt;After a few weeks, I noticed the agents themselves were rarely the problem. The writing quality was fine. The problem was context:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Context lives in many places.&lt;/strong&gt; The plan is in one doc, the rules in another, yesterday's posts somewhere else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Context goes stale.&lt;/strong&gt; A static brief from last week gives confident but outdated answers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;More context is not always better.&lt;/strong&gt; When I gave an agent everything, it pulled in details that had nothing to do with the task.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agents do not share what they know.&lt;/strong&gt; Each one works alone, even when they serve the same goal.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I think a better setup needs
&lt;/h2&gt;

&lt;p&gt;If I could design the ideal system, it would have four things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Selected sources.&lt;/strong&gt; I choose what each agent can see.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A clear trail.&lt;/strong&gt; When an agent uses a fact, I can see where it came from.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fresh context.&lt;/strong&gt; When the plan changes once, every agent sees the change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shared goals.&lt;/strong&gt; Agents working on the same campaign see the same current picture, while private notes stay private.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where I am now
&lt;/h2&gt;

&lt;p&gt;I still use project docs and a daily note, and it works well enough for one person. But the more agents I add, the more time goes into keeping them in sync instead of doing actual work.&lt;/p&gt;

&lt;p&gt;This problem is also the reason the team I work with is building Pryveo, a context and memory layer for people and AI tools.&lt;/p&gt;

&lt;p&gt;If you use more than one AI agent or assistant in your work, how do you keep them all working from the same context?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This post was written with help from AI for drafting and editing. The experience and setup described are my own.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>productivity</category>
      <category>mcp</category>
    </item>
  </channel>
</rss>
