Who it is for, and what it does well
Slack
Companies that run daily conversation in channels and want apps close to it.
- Where many teams already talk. Channels, threads and huddles.
- A large app directory. Many products post into Slack.
- Search across conversations. History is easy to find.
Vyre
The agentic command center for AI-native teams: people and agents work in one Space on a server you own.
Industry-neutral. You shape the records, and Flows, Playbooks and a Gate run the work.
Works with Vyre.
How Vyre connects to Slack today.
Today
Slack publishes a Web API and incoming webhooks. A person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it.
Where the vendor publishes an MCP server, a person can add it for agents to use.
Coming in 0.5.2
A packaged Integration, so the Connection and its operations arrive ready-made.
Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*, Slack included.
*Where the vendor provides an API.
Where Vyre fits.
What Vyre does around it.
Vyre does not replace Slack. These are the parts of the work Vyre does around it.
Chat
Chats between people and agents in a Space, with a Needs you chip when one waits.
Tasks and Playbooks
Tasks go to a person or an agent and appear under Needs you when stuck.
Records
The chat sits beside the records it is about.
Keep Slack for company-wide conversation. Vyre’s chat is for work with agents on records and tasks. A Flow can post to Slack where its API allows.
Why that helps.
What a team gets from it.
Slack is where the company talks. Vyre is where the agent and the record are.
- One place for people and agentsPeople and agents are members of the same Space. They share the records, tasks, files and chat, so nobody carries data from one tool to the next.
- Agents do the workAn agent takes the task and finishes it, hands it on or marks it stuck with a reason. A person is not moving data between tools by hand.
- Every outward action approvedAn email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.
Side by side
| Question | Slack | Vyre |
|---|---|---|
| What it is | Team messaging in channels and threads. | A shared working layer for people and agents: records, tasks, Flows, documents, sites and a Gate. |
| Where it runs | Hosted by the vendor. | On a server you own. |
| Connecting to the other | Slack publishes a Web API and incoming webhooks. | A Connection in the Vault and a Flow web step or custom module. Coming in 0.5.2: a packaged Integration. |
| Parts of the job in Vyre | Set by the product. | Chat, Tasks and Playbooks and Records. |
| Outward actions | Set by how the product is configured. | Held at the Gate until a person approves the exact words. |
The left column comes from the product’s public documentation or describes the kind of product. Where it differs, the vendor’s own documentation is the one to trust.
Questions people ask
Does Vyre replace Slack?
No. Keep Slack for company-wide conversation. Vyre’s chat is for work with agents on records and tasks. A Flow can post to Slack where its API allows.
How does Vyre work with Slack?
Slack publishes a Web API and incoming webhooks. In Vyre, a person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it. Coming in 0.5.2: a packaged Integration, so the Connection and its operations arrive ready-made. Integrations work where the vendor provides an API.