Never open another tool. Mention it in the thread and it files the work.
The Slack Agent lives in your workspace. Mention @choji to create a ticket, write a fix, or open a pull request — without ever leaving the thread the conversation started in.
What it takes off you
The ask lands in Slack, not in the tracker. Somebody has to see it, answer it, and remember to file it before it scrolls away.
File tickets without leaving Slack
DM @choji or hit the message shortcut on any thread to draft a structured ticket in your team's format. No tab switching, no copy-pasting context.
Kick off code from a message
Ask Choji to write the fix and the Coding Agent runs in the cloud — Slack stays the conversation, GitHub gets the work.
Draft PRs from a thread
Choji opens the pull request, replies with the link, and posts status updates back in the thread so the conversation and the change stay together.
How a run goes.
- 01 @-mention Choji Mention @choji in any channel, DM the bot directly, or use the message shortcut on an existing thread.
- 02 Pick an action Ask for a ticket, code, a PR, or just an answer — Choji picks the right agent and runs it for you.
- 03 Choji works in the background Ticket, code, and PR runs execute in the cloud. Slack shows live status so the team knows what's happening.
- 04 Outcome posted back in-thread Links to the ticket, PR, and any preview artifacts land back where the conversation started.
Watch it run
A Slack thread to a ready-to-merge PR.
How a run goes
Mention it in the thread. Never leave the thread.
What happens between the mention and the pull request. Scroll it.
You mention @choji
In the thread the conversation already started in.
It answers in channel
Not a DM, not a dashboard — where the people asking are.
It files the ticket
Structured, in your format, linked back to the thread.
And starts the work
A run on Choji’s own infrastructure, reporting back here.
@Choji can you take this one?
be present.
Put the slack agent on it, and get the rest of your day back.