Slack & Discord — the agent, in your chat app
Link your account once and the bot becomes a front door to your agent: DM it a task or @mention it in a channel, and results come back to the same place.
Connect in a minute
Slack — one install, then each person links
A workspace admin installs the OnePress bot once. Then each person opens Settings → Chat apps → Slack → Connect to get a one-time code, and DMs the
bot link <code> (no slash — Slack treats leading slashes as commands). To use it in a channel, invite the
bot there first, then @OnePress.
Discord — one OAuth popup
Settings → Chat apps → Discord → Connect opens Discord's authorize page —
pick the server the bot should join and approve. From then on, DM the bot or @OnePress it in that server;
anything you send becomes a task for your agent — same skills, same workspace, same memory
as the web app.
What a chat task looks like
Any instruction — "draft the follow-up email", "summarize yesterday's numbers". It runs as a normal task.
The bot replies "⏳ On it…" right away, so you always know the task landed — then you can walk away.
The answer lands in the same DM or as a reply under your mention — plus a link to the full conversation in the app.
Results come back to the chat
When a run finishes, the reply lands in the same chat — the agent's answer plus the finished file when there's one worth sending (or a link to it in your workspace). Automations report there too, so your Monday brief can find you before you open the laptop.
Slack and Discord each get their own conversation in your list — chat history doesn't mix with your web conversations, and everything stays readable in the app later.
Telegram support is built and in final testing — coming soon.
Safety notes
Inbound messages are rate-limited and billed exactly like web chat. Unlink any time from Settings → Chat apps — the bot immediately stops accepting tasks from your account.
Meet your agent where you already are
Settings → Chat apps → connect Slack or Discord. Then just message the bot.
Open the app