Slack agent
Your coding agent, right in Slack
Mention Hoplite in a channel or send it a DM. It answers questions about your code on the spot, starts a coding thread when something needs to change, and posts the pull request back into the conversation when the work is done.
Definition
What Is A Slack Coding Agent?
A Slack coding agent is a coding agent you work with from the place your team already talks. Instead of copying a bug report into another tool, you mention the agent where the report was posted and it picks up the context from there.
In Hoplite, the Slack agent sits in front of your coding threads. It reads the conversation, answers read-only questions directly, and creates or steers a Hoplite thread when code has to change. That thread is an ordinary cloud thread, so the whole workspace can open it, follow the run and review the diff.
Ask or assign
Questions Get Answers, Changes Get Threads
Ask where something lives or how it works and the agent reads the repository and answers in Slack. Ask for a change and it starts a coding thread instead, with the Slack conversation and any attached screenshots, PDFs or code files carried over.
The right project
It Knows Where The Work Belongs
A channel bound to a project tells the agent where work from that channel usually goes, and a Slack thread already linked to a Hoplite thread keeps talking to it. When the target is still unclear, the agent asks one short question instead of guessing.
Steer from the thread
Reply In Slack, Change The Run
The agent follows the Slack threads it's part of. Reply with a correction or an extra requirement and it sends the message to the running coding thread, or stops it if you ask, without anyone opening a browser.
Done means done
The Pull Request, Back Where You Asked
When a thread started from Slack has an open pull request that's ready to merge, the agent comes back to the Slack thread with a short summary and the PR link. Thread titles and PR links come straight from Hoplite's records, not from the model.
Comparison
Copy-Paste Vs. Slack Agent
| Question | Pasting into a coding agent | Hoplite Slack agent |
|---|---|---|
| Starting work | Copy the report into another tool | Mention @Hoplite where it was posted |
| Context | Whatever you remembered to paste | The Slack thread plus screenshots, PDFs and files |
| Follow-ups | Switch tools and find the session | Reply in the same Slack thread |
| Who can start it | Whoever has the agent open | Any workspace member in the channel |
| Visibility | One person's session | A Hoplite thread the whole workspace can open |
| The result | A link you have to go and post | The PR link posted back to Slack |
FAQ
The Slack Agent, Answered
- How do we install the Slack agent?
A workspace owner or admin connects your Slack workspace to Hoplite from the integrations settings. One Slack workspace connects to one Hoplite workspace, and admins can bind channels to projects there too.
- Who can use it?
Anyone in Slack whose verified email matches a member of the linked Hoplite workspace. Slack users without a Hoplite account get a message explaining that, with a link to request an invite.
- How do I talk to it?
Mention @Hoplite in a channel, send it a direct message, or reply in a Slack thread it's already part of. There are no slash commands to learn.
- Will it post progress updates while it works?
It posts when the work is done, with the pull request link. To follow a run as it happens, open the linked Hoplite thread, where the tool calls, diff and tests stream live.
- Can it read screenshots and files?
Yes. Images, PDFs and text or code files are shown to the model, and videos come through as a few sampled frames. Files carry over into the coding threads it starts.
- Can I approve tool calls from Slack?
Not today. Approvals happen in the Hoplite thread, where any owner, admin or member of the workspace can answer them.
Bring your coding agent into Slack
Connect a GitHub repository, add Hoplite to your Slack workspace and mention it in a channel. Try Pro free for 14 days.