dax has opencode post progress to a Slack thread

dax says he tells opencode to keep his team updated in a thread on Slack with progress, screenshots and videos. He describes it as good for long running work, because everyone can pop in and see progress.

dax

@thdxr

X

great for long running work everyone can pop in and see progress

That is the whole trick. It is not a plugin, an integration or a dashboard. It is an instruction in the prompt, and the agent does the posting as part of the work it is already doing.

Why this is more than a novelty

The default shape of agent work is that one person has the session open and everybody else has to ask them how it is going. The person running the agent becomes a status relay, which is the worst job on any team. Pushing the updates into a thread flips that. The information sits somewhere the rest of the team can read on their own time, and nobody has to interrupt the person who is actually steering.

The screenshots and videos part matters for the same reason. A line of text saying a change is done is a claim. A screenshot of the thing running is closer to evidence, and it is evidence a teammate can check without pulling the branch.

This is one engineer describing his own setup, not a measured result. dax has not said how often the agent posts, what it posts when it is stuck, or whether teammates actually read the thread.

Fits the way he already works

It lines up with the rest of what dax has described. He has said he keeps one long-running session per project that farms work out to subagents, and that he feeds phone screenshots straight into an agent session as prompts. Screenshots flow in as input, screenshots flow out as status.

For working engineers, the thing worth copying is not Slack specifically. It is treating the agent as something that reports to the team rather than to one terminal, and doing it with a sentence rather than tooling.