Over the past months, we have noticed a recurring pattern in our support at Tuist.
User questions and reports usually happen in our #support channel on Slack. Those messages tend to fall into four categories:
- A question whose answer doesn’t exist in the docs, or is hard to find. We answer the user and usually open a PR to improve the docs so the next person can find it faster.
- A bug report, where we ask for a reproducible project and go back and forth gathering context until we can reproduce the issue on our end, then open a PR with the fix.
- A misconfiguration, where we similarly need some back and forth to understand what the user is doing before we can tell whether it’s a bug or a setup issue.
- A request for something Tuist doesn’t support yet, which we translate into an RFC if we see fit, and later map to an actual implementation with the help of agents.
Each of these can be modeled as a workflow that mixes deterministic and non-deterministic (agentic) steps. On our end, that usually means jumping between our local dev environment, agentic coding sessions, and the Slack conversation. It felt like too much friction, and for a while we knew we had to do something about it.
We have been using Dosu, but it only helps partially. Dosu can’t run xcodebuild to reproduce an issue, or open a PR against our repository with the fix.
Luckily, I came across Spacebot, which ticks all the boxes. I think of it as a framework for modeling agentic workflows. We run it from a Mac environment, so it can execute things like xcodebuild, and it gives us the configurability we need to iterate on the experience you get when using it. We just deployed it and connected it to Slack. It only triggers when you tag it @Tuist Agent, and we expect it to need some tweaking, so we’d appreciate a bit of patience early on.
The goal is for you to get better and faster answers, and even fixes or features shipped, so we can focus our energy where we add the most value: taste, and making sure the code meets the quality bar we hold ourselves to at Tuist.
If you have any questions, I’m happy to answer them.