> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quadrillion.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack Integration

> Connect Qualia to Slack for agent updates and two-way chat.

Connect Qualia to Slack to receive updates from agents running in [autonomous mode](/autonomous-mode) and to chat with Qualia directly from Slack. When agents are set to Infinity independence, they post progress and results to Slack instead of asking for confirmation, and you can reply, answer questions, and start new conversations without leaving Slack.

Slack works the same in the desktop app and in Qualia Cloud: connect once from settings, then invite the bot to the channels where you want it.

## Connecting to Slack

1. Go to **Settings > Slack**
2. Click **Connect to Slack**
3. Authorize Qualia in the Slack OAuth flow

Once connected, the status shows **Connected**. Invite **@Qualia** to any channel you want it to participate in; proactive updates are posted to your direct message with the bot and to per-project threads.

In Qualia Cloud, the connection is associated with the workspace where you start the OAuth flow. New DMs and @-mentions create projects in that workspace. Reconnecting Slack from another Qualia workspace moves this new-conversation target; existing project threads continue routing to their original workspaces.

## Project threads

Each project gets its own Slack thread. Toggle **Notify in Slack** in a project's context menu to control whether that project posts updates. Projects started from Slack have it enabled automatically.

## What gets posted

Agents post:

* **Progress updates**: What they're working on
* **Findings**: Preliminary results and insights
* **Completion notices**: When tasks finish
* **Questions**: If they need guidance, with answer buttons you can click in Slack

## Chatting from Slack

* **Start a conversation**: @-mention the bot in a channel it has joined, or DM it. Qualia creates a project and replies in a thread.
* **Reply in a thread**: Anyone in the workspace can reply in an agent's thread; the agent incorporates the feedback and adjusts its work.
* **Answer questions**: When an agent asks for guidance, click the buttons or use the select menus in the Slack message.

## Where Qualia runs: cloud or your machine

Under **Where Qualia runs** in Slack settings, choose where messages from Slack execute:

* **Qualia Cloud** (default): runs in the cloud and is always available — Qualia responds whether or not your computer is on.
* **This machine**: runs on your own computer, against your local files and hardware. Use this when a Slack request needs data or compute that only lives on your machine.

When set to **This machine**, Qualia in Slack is only as available as that computer:

* It responds only while Qualia is running on your machine. If your machine is off or Qualia isn't running, Slack replies with a note asking you to start it, and the message isn't queued — send it again once you're back.
* If your machine goes to sleep **mid-response**, that run stops and may leave a partial reply in the thread. Re-ask once it's awake.

Switch back to **Qualia Cloud** any time you want always-on availability.

## Disconnecting

Click **Disconnect Slack** to revoke access:

* Agents will no longer send updates to Slack
* Agents at Infinity independence will continue working but won't report progress
* Removing the app from the workspace in Slack also disconnects it
* You can reconnect at any time

## Troubleshooting

### Bot not posting

* Verify the bot is invited to the channel
* Check that the Slack connection shows **Connected** in Settings
* Check the project's **Notify in Slack** toggle

### Bot not responding to @-mentions

* @-mentions only start a conversation for the user who connected Slack
* Thread replies work for anyone in the workspace

### Bot says your machine is offline

* This appears when **Where Qualia runs** is set to **This machine** but Qualia isn't currently running on it
* Start Qualia on that computer and send the message again, or switch **Where Qualia runs** to **Qualia Cloud** for always-on availability