# From Slack

At the end, a task you said in Slack is running on your team's server, the thread shows what runs and what it may cost, and the pull request opens when you press.

## At a glance

**Time:** 5 minutes, with Slack connected.

**You need:**

- Slack connected to your team's runner: [Connect Slack](slack-connect.md)
- You in the org, matched to your Slack account (an admin sees the match in Settings → Slack)

## Steps

1. **Say a task in Slack**, such as "Fix the typo on the pricing page", one of three ways:
   - on Loopgate's **Home**, **New task** or **Give a task** beside an agent or a workflow, then **Show me what will run** and **Open thread**;
   - type `/loopgate Fix the typo on the pricing page` in a channel Loopgate is in;
   - write to `@Loopgate` in a channel, or in its **Messages** tab.

   You should see: a thread with one card: who works it, your task in your words, the workspace, each step's engine, the access and the most it may spend, with **Start**, **Customize** and **Change…**.

2. **Change it before Start, if you want.** **Customize** sets each step's model, thinking and instructions, and the run's access; then **Keep these**. **Change…** reopens the form to pick who works it.

   You should see: the card redrawn, listing every change it starts with, such as `1 chosen here`.

3. **Press Start.**

   You should see: the same card turn into the progress card, one line per step with its state and time, the cost so far and **Stop**.

4. **Reply in the thread while a step works or waits.** Start with `@<step>` to pick one.

   You should see: ✅ on your message, and your words in the step's next message.

5. **Answer what the run asks with the buttons in the thread**: approve, choose, lock a document (its first 2,800 characters show), or reply to a single question.

   You should see: the thread gain a post only for a step's reply, a question for you, a stop or the finish.

6. **Read the finish.**

   You should see: `✅ Done` with the final reply and what it cost, **Open pull request** and **Open in workbench**. The pull request opens only when you press.

## Good to know

- **Home** shows the runner's engines, what needs you, your tasks, every agent and workflow with **Give a task**, and the workspaces. Decisions are taken in the thread, never on Home.
- From your phone, Slack's own app is enough: say the task, press the buttons. There is no Loopgate phone app; a link in the thread opens the workbench in the browser.
- Picking who works it in the form costs nothing, since no copilot turn is needed.
- A task from Slack runs with Full access, shown as `⚠ Full access` on the card, unless Customize lowers it to Workspace or Read only: nobody sits beside a server to approve tool calls. An org policy can forbid it.
- Every task from Slack stops at the spending limit an admin set in Settings → Slack, in dollars and hours. The card says it before Start.
- Only the person who started a thread is heard in it, except at a gate that names a teammate: [Name who decides](who-decides.md).
- Several questions at once, a whole document, raising the spending limit after a stop, and Adjust and retry open the workbench from the post's link.
- 👀 marks a message the copilot is reading.

## If something is off

- **Slack says "Ask your Loopgate admin to map your Slack ID …"** An admin picks you on your row in Settings → Slack, or presses **Match again** after you join the org.
- **Slack says "This button has expired."** The task moved on, or the person was unmapped. Use the newest post in the thread.
- **A link from an older thread does not open.** The temporary address changed at a restart. Open the task from the portal's **Devices → Open**, or give the runner [a permanent address](address-cloudflare.md).

## Next

- [Name who decides](who-decides.md)
- [Share a run](share.md)
- [Connect Slack](slack-connect.md)