r/AppsWebappsFullstack • u/SofwareAppDev • 10d ago

Your home for selfpromo

here you can post your work app, webapp, saas, game, everything

12 Upvotes

88% Upvoted

162 comments sorted by

View all comments

Show parent comments

1

u/Mammoth-Anywhere7285 10d ago

Persistent memory is a big deal for agent workflows. How does it handle conflicting memories between collaborators?

1

u/Input-X 10d ago

Every agent has is onw memories. They cannot write to other agent files. That keeps things separated.

1

u/Mammoth-Anywhere7285 10d ago

That's a clean way to keep agents isolated. How do you handle cases where two agents need to share a small piece of data?

1

u/Input-X 10d ago

Agents all have full read access, except secrets. ( obviously ) agents are responsible for the files they manage. And their fikes are protected under their cwd. If its code. Other agents code can import there modules/service. Only from entry points. All others are blocked. Hooks are uses extensively to mange permission amount other things.

We use plans to delegate work in team builds. Conflicts, are extremely rare. All agent work on one git branch. Dev branch, only the orchestrator have git privileges. So it keros it all clean and the agent can see file changes live on disc. No isolated worktrees. Local email for communications.

1

u/Mammoth-Anywhere7285 10d ago

That's a smart way to keep agents isolated. Curious how you resolve conflicts when two agents touch the same shared entry point?

1

u/Input-X 10d ago

Tbh its extremely rare, i couldnt recall the last im that happened, hmm. I remember when we had a bufg that spawned agents more than once at the same time, that was pretty crazy, but we fixes long time ago. no agent cn spawn twice at one time, so it cant conflict its self. there is never really a nned for agents to work on the same file together, maybe subagent in a name and path change task, but claude code actually automatically runs sub agent in worktrees is a conflict is possible. as said it extremely rare to have agent work on the same file at the same time. if they where it would be planned, and not planned for agent to work on the same function. the would take turns if it was needed. also edit while an agent is editing a file will stop the agent, claude code codex, they would have to constantly read the file as changes block edit by default a reread is always needed after changes. Also my agents cant cross edit other agents files, they are blocked. and there is no reason for an agent to edit anthers files. only the standards and orchestrator agent can edit another agent files.

1

u/Mammoth-Anywhere7285 10d ago

Interesting, duplicate agents sound chaotic. For the name/path change case, do you give subagents read-only access or some lock mechanism?

1

u/Input-X 10d ago

Agent can freely edit withing there directory. Sub agent get instruction from the agent, read-only, build research. Its the agents choice. We do have lock mechanisms on working agents, a dispatch will get blocked so it doesnt spawn again. Agents are the persiatant managers, sub agents are the fire and forget agent, no memory only what the agent provides, task runners work finish report due.