Keep Slack for the company. Run the project in Current.
Slack is built for conversation across a whole company. Current is built around projects: every chat sits next to the PRs, issues, decisions and agents that belong to it, so nobody has to rebuild the picture from five channels.
Where Current is different
- Projects, not channels
- A project in Current has its team chats, its linked work, its decisions and its phase in one place. A channel only has messages.
- Decisions don’t scroll away
- Mark a message as a decision, or let @Current propose one from a thread. It lands in the project’s decision log with a link back to where it was made.
- From thread to branch
- Ask @Current to fix what a thread describes. An agent works on its own branch, and the PR shows up in the project, live.
Where Slack is good
- Every company already has it, and so do your customers and partners through Connect.
- A huge app directory for nearly any tool.
- Huddles, clips and workflows for everyday company chatter.
Together
Keep Slack for the rest of the company. Current mirrors the channels you pick into a project chat, and replies from Current post back into Slack under your own name.
| Slack | ||
|---|---|---|
| Team chat, organised by project | Yes | Partly Channels, not projects |
| Linked PRs, issues and docs, live in the project | Yes GitHub, Linear, Notion | Partly Unfurls and app messages |
| Decisions as their own record, with a source | Yes | No |
| Meeting notes into decisions and issues | Yes | Partly Huddle notes |
| Customer signals routed to the right project | Yes Intercom, Gong | Partly Via channels and apps |
| Coding agents on their own branch | Yes Sandboxed worktrees | Partly Through third-party apps |
| Live previews with comments pinned to elements | Yes | No |
| One timeline across every tool | Yes | No |
| Bring your own AI: Claude Code, Codex, Gemini, OpenCode | Yes | No |