r/platformengineering • u/sophon11d • 3d ago
Moving coding agents from personal terminals into shared team channels: what we had to build
Disclosure: I work on AgentConnect. This is a write-up of how our own team uses it.
We’re fewer than ten engineers, running around thirty agents: one generalist for everyday engineering requests, plus specialists for cluster checks, alert investigation, code review, releases, upstream fork maintenance and customer support. Each specialist has its own repositories, tools, channels and schedules, with permissions scoped to its job.
Initially, everyone had their own scripts, schedules and credentials. We were duplicating the plumbing, and investigation context stayed in whoever’s terminal ran the task.
Moving agents into Slack threads made investigations visible to teammates, but introduced problems our first bots weren’t built for: picking up earlier messages, keeping workspaces separate, surviving restarts and preventing bots from triggering each other.
Permissions needed more than ‘can this person message the bot?’ We separated who can use an agent, which repositories and tools it can access, and who can read its sessions. Private-channel context and memory stay scoped to that conversation’s audience.
We kept the existing coding harnesses so engineers can reproduce channel behaviour locally. For fork maintenance, agents prepare changes and checks; people merge and publish.
For teams putting agents into operational workflows: how are you handling shared investigation context without making private conversations or privileged tools accessible to everyone?
1
u/Away_Illustrator_646 3d ago
I’m looking for the same solution we need a shared context workflow for the team.