Mention the bot in a channel it has been invited to, or write in a channel it listens to, and the answer comes back in the thread. Behind the thread, a real agent session runs in a real terminal on your team's Mac, and the same work appears on the board for people with access. Nothing here needs an install or a Push account; it needs the owner to have connected your Slack account.

What reaches Slack by default

• A short acknowledgement when Push picks your message up: a reaction, or one line.
• The agent's answer, in the thread where you asked, with any files the agent chose to share.
• The agent's questions, and permission prompts on work you started (see Approvals).

Nothing else. No receipt line, no footer, no link back into Push, no "Completed" or "Reopened" notice. The owner can turn each of those on. Links into Push are off by default because opening one needs workspace access. Answers, questions and anything that needs a person are never held back.

Where a request goes

A mention in a channel, or a plain message in a listening channel, is a request. Push picks the session it belongs to, or starts new work in a folder you may run in. When it cannot tell, it asks you privately whether to start a new session or connect to an existing one. New work starts right away; the owner can set Push to ask first instead.

Direct messages to the bot, group messages and Slack Connect channels are not supported.

Follow-ups and questions

Reply in the same thread and the same session continues. A plain message in the thread is a request. When the agent asked a question, your reply is matched to that question.

A session that has gone to sleep is restored to its exact conversation. A session that was completed reopens when your follow-up changes the result; a question about the result is answered without reopening it. If a session cannot be restored, Push tells you once and suggests starting new work or resuming.

Files

Attach files to your message and they reach the agent. Files the agent selects — a screenshot, a document it wrote — come back in the thread.

Approvals

When a Claude Code or OpenCode session you started from Slack asks for a permission, the prompt reaches you as a private message with Approve and Deny buttons. It is sent to the person who started the work. Answer within ten minutes; after that the prompt is denied.

Prompts from other runtimes do not reach Slack. They are answered on the Mac or from the iPhone.

Who can act

Push acts on a message only when the Slack account behind it is connected to a Push person: you linked your own Slack identity, or the owner mapped your account onto a member and lent you that member's permissions. Either way your Slack name stays on every message, and what you may do is decided for each message from the permissions the owner gave, so a change takes effect immediately.

If your account is not connected, Push tells you once: "Push can't act on this, because your Slack account isn't connected." Your words are kept on the thread as context. Context never becomes an instruction later, and it never wakes a sleeping session. Ask the owner to connect your account, then ask again.

Configuration never changes through Slack. Connecting accounts, choosing channels and turning notices on or off are the owner's to do, on the Mac.

When the bot is quiet

The Mac is asleep, offline, or Push is not open. Requests wait with their sender and are delivered when the Mac reconnects, as the person who sent them. Keeping the Mac awake and Push open is the operator's job: Always On and the notes under Choose the Mac.

If a reply you expected never came and the Mac is up, the operator can see where it stopped with push communication inspect.

Setting it up

The operator's steps — push slack setup, approving the install in Slack, pasting the two tokens, mapping accounts — are in Set up Push for a team.