← All IntelClip / AI AgentsNon-technical staff triggering agent fixes via Slack
From Multiplayer agentic engineering — Arjun Singh, Superconductor · ≈12:14
“This is the key for allowing your non-technical team members to trigger real work.”
“You just ask for it and it's done.”
“Getting your full thing set up in this like kind of sandbox environment used to be really, really painful.”
“But agents have gotten better.”
What’s in it
- Shows how non-engineers can ship real fixes via Slack alone
- Explains why sandboxed dev environments finally became practical with agents
- Recommends tools (Claude Coder, CodeX) to replicate this workflow yourself
Clip transcript
And the last thing I'll mention about that is that this is the key for allowing your non-technical team members to trigger real work. Right? Your non-technical people don't have development environments set up on their computers. But we've gotten our support people or growth people to actually be meaningfully impacting the product by just talking to the users, seeing bugs, experiencing themselves, and just go to Slack or the rabbit cell and say, "Hey, fix this." They fix it. Screenshots are shown. Engineer gets it, gets merged. Without that, they'd have to put it in linear and linear would eventually pick it up and a PM would triage it or whatever. None of that here. You just ask for it and it's done. Now, the reason people didn't do this you know, up until somewhat recently, like this was really painful. Getting your full thing set up in this like kind of sandbox environment used to be really, really painful. But agents have gotten better. We have our own environment setup assistant that kind of takes your project and gets it to work in one of these sandboxes. But honestly, whether you use this or not, I highly recommend you get your project working this way and you can just get Cloud Coder or CodeX to do this for you. You don't have to use us, but you know, we think it's the best way.
Comments
Sign in to comment.
Loading comments…