When you connect Slack to Composio, the dashboard asks you to pick a Managed App: Legacy or Standard. This guide explains, in plain words, what each one means, what works and what doesn't, and which one to pick.
First, a few words explained
Auth config: the saved settings that tell Composio how your users log in to Slack. You create one in the Composio dashboard.
Composio Managed: Composio uses its own Slack app for the login, so you don't have to create a Slack app yourself.
Managed App: Composio has two Slack apps. This setting picks which one your auth config uses: Legacy (the older one) or Standard (the newer one).
Tool: something your agent can do in Slack, like sending a message or listing channels.
Trigger: an alert Composio sends your agent when something happens in Slack, like a new message arriving.
Free or paid Slack: the plan your Slack workspace is on. If you're not sure, ask your Slack admin.
Rate limit: a cap Slack puts on how much an app can read, and how often. Go over it and Slack tells your agent to wait.
Which one should I pick?

Pick Legacy if your agent needs to react to new Slack messages, or needs to search messages in a free Slack workspace.
Pick Standard for everything else. Slack has approved it, and it can do everything Legacy can, except the two things above.
Good to know: the Legacy app reads message history slowly, 15 messages per call and about 1 call a minute. If your agent reads a lot of old messages, pick Standard.
Legacy vs Standard at a glance

How to pick the app in the dashboard
Step 1: Start a new auth config
1. Open the Composio dashboard and go to Auth Configs.
2. Click Create in the top-right corner.

Step 2: Choose Slack
1. Type slack in the search box.
2. Click Slack. Don't pick Slackbot; that's a different toolkit.

Step 3: Name it
1. Composio fills in a name for you, like slack-jjmdja. You can keep it or type your own.
2. Click Next.

Step 4: Read the settings screen
This screen has three parts. Here's what each one means:
Authentication Method → OAuth 2.0: your users log in through Slack's own login page. Leave this as it is.
Credentials → Composio Managed: Composio's Slack app is used. Keep this selected. Choose Your Own Credentials only if you've made your own Slack app (see how to use your own Slack app).
Managed App: which of Composio's two Slack apps to use. It starts on your project's default: Legacy for projects created before 1 December 2026, Standard for projects created after.

Step 5: Pick Legacy or Standard
1. Click the Managed App box. You'll see two choices.
2. Pick one using the chart above.

Legacy means: every Slack tool and trigger works, including message search and new-message alerts. Slack hasn't approved this app. Reading message history is slower (15 messages per call).
Standard means: Slack has approved this app. Everything works except the old search tools and the new-message alerts.
Step 6: Create it
1. Check that Managed App shows the app you want. Here it shows Standard.
2. Click Create Auth Config.

Step 7: Connect a Slack account
1. Open your new auth config and click Connect Account.
2. On the Slack page, pick your workspace and click Allow.
3. The account shows up under Accounts with an Active status. You're done.
For screenshots of these steps, see how to connect Slack to Composio.
What each app is good and bad at
Legacy app
Good:
1. Search works everywhere: SLACK_SEARCH_MESSAGES, SLACK_SEARCH_ALL and SLACK_SEARCH_FILES work on free and paid Slack.
2. New-message alerts work: CHANNEL_MESSAGE_RECEIVED, DIRECT_MESSAGE_RECEIVED, RECEIVE_MESSAGE and RECEIVE_BOT_MESSAGE.
3. If you already use Slack with Composio, you're on this app and nothing changes.
Not so good:
1. Slack hasn't approved it.
2. It asks for permission to read every message the user can see (the search:read permission). Slack no longer approves this for new apps.
3. Reading message history is slow: 15 messages per call, and about 1 call a minute. Go faster and Slack returns error 429 (ratelimited). Details are below.
Standard app
Good:
1. Slack has approved it.
2. It asks for narrower search permissions instead of search:read.
3. All other 162 tools and all other triggers work, the same as Legacy.
4. Reads message history at full speed: up to 999 messages per call.
Not so good:
1. The three old search tools don't work. They fail with a missing_scope error. Use SLACK_ASSISTANT_SEARCH_CONTEXT instead (see below).
2. New-message alerts don't work. Composio lets you create them, but they never fire, and it doesn't warn you.
Searching Slack with the Standard app
SLACK_ASSISTANT_SEARCH_CONTEXT is the new way to search Slack. It uses Slack's newer search, called Real-time Search. Here's what to know:
1. It works on paid Slack plans only. On a free plan it fails with feature_not_enabled.
2. It gives up to 20 results at a time. To get more, pass the cursor from the last answer; page numbers don't work.
3. Each user can search about 10 times a minute.
4. Guest users in a Slack workspace can't use it.
5. Slack doesn't allow saving the search results.
Reading messages is slower on the Legacy app
Slack limits apps it hasn't approved when they read old messages. This affects SLACK_FETCH_CONVERSATION_HISTORY (messages in a channel) and SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION (replies in a thread). The Standard app is approved, so it doesn't have this limit.
1. 15 messages per call. Even if you ask for more, Slack sends back at most 15. To get the next 15, pass the cursor from the last answer.
2. About 1 call a minute. Slack may let a few quick calls through, but if you keep calling faster, it can refuse.
3. What the error looks like: Slack answers with HTTP 429 Too Many Requests and the error ratelimited. The Retry-After header says how many seconds to wait.
4. What to do: wait the number of seconds in Retry-After, then try again. If your agent reads a lot of history, use the Standard app instead.
Slack started this on 29 May 2025 for apps that aren't in the Slack Marketplace (Slack's announcement). Workspaces that installed the Legacy app before that date may still get the older, faster limits.
Things that don't work on either app
Canvas tools and star tools don't work on either app, because neither app asks for the canvases or stars permissions. If you need them, use your own Slack app with those permissions.
Picking the app in code
API: when you create the auth config, pass managed_app_id to choose the app.
TypeScript SDK: choosing the app is coming soon. Until then, auth configs made with the SDK use your project's default app.
Changing your mind later
1. Existing auth configs and connections stay on the app they were made with. Nothing breaks.
2. A connection can't move from one app to the other. To switch, create a new auth config with the other app and ask each user to connect again.
3. Keep the old auth config until everyone has reconnected, so nobody loses access in between.
FAQ
My agent needs to search Slack. Which app? On a paid Slack plan, Standard with SLACK_ASSISTANT_SEARCH_CONTEXT. On a free plan, Legacy.
My agent replies when someone posts a message. Which app? Legacy. The Standard app doesn't get new-message alerts.
I already use Slack with Composio. Do I need to do anything? No. Your connections stay on the Legacy app and keep working.
My agent gets error 429 or "ratelimited" when reading messages. Why? You are probably on the Legacy app and reading message history faster than Slack allows. Wait the number of seconds in the Retry-After header and try again, or switch to the Standard app.
Why are there two apps? Slack approved a newer version of Composio's app, but without the broad search permission and message alerts. Composio kept the older app so nothing breaks for people who rely on those.