I'm going to chock this one up as a yet-another "X is your agentic coding hub" PR nonsense.
What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but it still feels like tooling for agent teaming is quite lacking and unergonomic.
Two things: (1) models are far more autonomous and run for longer coherently, (2) visibility into the development process was lost in local development.
Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore.
Regarding visibility, developers now think in high level architecture rather than lines of code, but implementation details are still important to document. We also want to understand when agents are hitting pain points. Both of these basically require archiving agent outputs more deeply than just code changes and commits.
I see. What would the proper solution then look like for when we should consider moving our teams? Sounds like you you said they're all current ones are missing ergonomics. Do you think it's slack code?
Comments
I'm going to chock this one up as a yet-another "X is your agentic coding hub" PR nonsense.
What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but it still feels like tooling for agent teaming is quite lacking and unergonomic.
Why did you move from on-dev-machine coding to @claude in GitHub if it's a weaker capability?
Im not convinced of any of these cloud or tagging solutions where I get to the point of moving coding away from my dev's machines.
Two things: (1) models are far more autonomous and run for longer coherently, (2) visibility into the development process was lost in local development.
Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore.
Regarding visibility, developers now think in high level architecture rather than lines of code, but implementation details are still important to document. We also want to understand when agents are hitting pain points. Both of these basically require archiving agent outputs more deeply than just code changes and commits.
I see. What would the proper solution then look like for when we should consider moving our teams? Sounds like you you said they're all current ones are missing ergonomics. Do you think it's slack code?