# Slack launched Slack Code for AI agents. Is it the same as Maito? And do you need both?

Source: https://maito.app/compare/maito-vs-slack-code
Date: 2026-10-13

Maito vs Slack Code: Slack Code gives a coding agent you already use a shared channel. Maito is an AI teammate for your whole company. What each one does, what it costs, and when to use both.

## Is Slack Code the same as Maito?

**No. Slack Code is a place in Slack where a coding agent you already use works on one task. Maito is an AI teammate for your whole company.**

With Maito, your whole team works with the same agent in the same thread, in Slack or the AI assistant they already use. It takes on any coding task and any business task, remembers your company, and runs recurring work. It costs $149 per workspace per month, with unlimited people. Slack Code is included in Slack, and you bring and pay for the coding agent.

## What is Slack Code?

**Slack Code is a shared Slack channel where an AI coding agent works with your team on one task.**

You mention a supported agent in Slack, and it opens a temporary code channel for the task. The channel has tabs for the conversation, the agent's plan, the code changes, and a live preview. Anyone in the channel can redirect or stop the agent, and the team reviews the changes line by line. [Salesforce's announcement](https://www.salesforce.com/ap/news/press-releases/2026/08/24/salesforce-launches-slack-code-to-make-ai-software-development-multiplayer/).

Slack Code is included in every Slack plan and is rolling out gradually. [Slack's help center](https://slack.com/help/articles/54310833022355-Build-with-AI-as-a-team-using-Slack-Code).

## So Slack Code is an AI agent?

**No. Slack Code is the place where agents work. The agent itself comes from the Slack Marketplace.**

The work is done by an agent you install from the Slack Marketplace, such as Claude, Devin, GitHub Copilot, Factory, or Replit. Some of them require their own paid account. [Supported agents](https://slack.com/help/articles/54310833022355-Build-with-AI-as-a-team-using-Slack-Code).

That makes Slack Code a good home for an agent you already use. It does not choose or replace the agent.

## And what is Maito?

**Maito is one AI teammate your whole company works with together, for coding and business work.**

Maito is one agent your team shares in Slack, Claude, ChatGPT, Cursor, Codex, Grok, and Muse. Anyone can ask it for work, join the same thread, add context, and pick up where someone else left off. You give it a name, a role, and instructions.

It does any coding task: features, bug fixes, refactors, code review, QA, and tests, each in its own sandbox with a pull request for your team. It does business work too, such as research, reports, and follow-ups in your connected tools. [How Maito works](/homepage).

## How do they compare at a glance?

**Both work in Slack. Maito adds business tasks, company knowledge, and recurring work for a flat $149 per month. Slack Code is included in Slack and relies on the coding agent you tag.**

|                   | Maito                                                                 | Slack Code                                                           |
| ----------------- | --------------------------------------------------------------------- | -------------------------------------------------------------------- |
| What it is        | An AI teammate for your company                                       | Shared channels where supported AI agents work with your team        |
| Where you use it  | Slack, Claude, ChatGPT, Cursor, Codex, Grok, and Muse                 | Slack                                                                |
| Who does the work | Maito, with the AI provider and model you choose                      | A Marketplace agent you install; some need their own paid account    |
| Working together  | Yes: The whole team works with one agent, in any thread                  | Yes: Teammates join one code channel per task                           |
| Business tasks    | Yes: Research, reports, follow-ups, and work in your connected tools     | Partly: Possible, through the coding agent you tag                         |
| Code changes      | Yes: Any coding task, in its own sandbox, with a pull request and checks | Yes: Diffs, previews, and line comments from the agent you tag          |
| Company knowledge | Yes: Remembers facts and saves workflows as skills                       | No: One channel per task, archived when done                           |
| Recurring work    | Yes: Loops on a schedule, from a webhook, or on request                  | No: Work starts when someone tags an agent                             |
| Price             | $149 per workspace per month, unlimited people                        | Included in all Slack plans; some agents need their own paid account |

## What happens when someone asks for a business task?

**Maito does business tasks with your tools and what it already knows about your company. Slack Code hands them to the coding agent you tag.**

_Illustrative conversation:_

> **Dana:** @Maito summarize the accounts that churned this week and draft a check-in email for each.
>
> **Maito:** Five accounts churned. Three mentioned the missing SSO setting in their last support conversation.
> Drafts are in the thread. Want me to send this summary every Monday?

You can tag a coding agent for non-coding work, such as a marketing plan. It works with only the access and memory its own product gives it, and the channel closes when the task is done.

## And when a customer reports a bug?

**A coding agent in Slack Code fixes the code. Maito handles the whole bug, from the report to the reply.**

_Illustrative conversation:_

> **Anna:** @Maito a customer says their CSV export stops at 10,000 rows. Ticket #4821.
>
> **Maito:** Reproduced. Here's a video of the export stopping at 10,000 rows, with the server log that shows why.
> I opened PR #482 with the fix and a test, and ran QA on exports of 5,000, 10,000, and 50,000 rows. All pass.
> A draft reply for the customer, with the video, is below.

In Slack Code, a coding agent takes the request into a code channel. Engineers watch its plan, review the diff, and open a pull request.

Maito does the rest of the work too. It reproduces the bug, records a video of it, and collects the evidence from your logs and tools. Then it writes the fix and tests, runs QA, opens the pull request, and drafts the reply to the customer. Support, product, and engineering follow it all in the original thread.

## Doesn't Slack Code remember the work too?

**No. A Slack Code channel keeps the record of one task. Maito remembers your company across all its work.**

Channels close when the work is done or after seven days without activity, and archived channels are read-only. Anything carried between tasks lives in the agent's own product, not in Slack Code. [Slack's help center](https://slack.com/help/articles/54310833022355-Build-with-AI-as-a-team-using-Slack-Code).

Maito learns facts from shared work, such as a pricing rule or how a feature behaves, and uses them in later conversations. Good results can become skills that anyone on the team can reuse. Private conversations stay private. [Maito FAQ](/faq).

## Can Slack Code run work every week?

**No. Slack Code starts work when someone tags an agent. Maito runs recurring work with Loops.**

Maito's Loops run on a schedule, from a webhook, or when you start them: the Monday update, a morning check of new errors, or a weekly summary of customer feedback. Your team can pause or change a Loop at any time.

## What does each cost?

**Maito costs $149 per workspace per month, with unlimited people. Slack Code is included in every Slack plan, and some agents need their own paid account.**

**Maito: $149 per month**

- One workspace, unlimited people
- $20 in included credits for coding sandboxes and web search
- Your AI provider bills its usage separately

**Slack Code: Included in Slack**

- Available on every Slack plan
- Some agents need their own paid account
- Agents priced per person cost more as your team grows

## When is Slack Code enough?

**Slack Code is enough when your engineers already pay for a supported coding agent and only want it inside Slack.**

Slack Code is included in every Slack plan, so it adds no subscription. It gives the agent you already use a shared channel, and nothing more: the agent stays the same, with the same access and memory it has today.

## Can we use both?

**Yes. Engineers can keep their coding agent in Slack Code while Maito works with the whole team.**

Maito does coding and business tasks for everyone, with your company's knowledge and recurring work.

Maito doesn't run inside code channels today. Code channels only accept agents from Slack's supported list, and the APIs for other agents are not open yet. Maito works in your regular channels, threads, and DMs.

## So which one should you choose?

**Choose Maito for one AI teammate across your whole company. Choose Slack Code if you only want a coding agent you already pay for inside Slack.**

**Choose Maito if:**

- Your whole team should work with one AI teammate, in the same threads
- You want any coding task done, plus business work
- It should remember your company and reuse what works
- You have work that comes back every day or week
- You want one flat price with unlimited people

**Choose Slack Code if:**

- Your engineers already pay for a supported coding agent
- You only want that agent inside Slack
- You don't want another subscription

The best test is one real task from your team. Give it to Maito and to the coding agent you'd use in Slack Code, then compare the result and how often you had to step in.