> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# Delegations

> Ask Islo to start or continue factory work from Slack, GitHub, and Linear.

After the [quickstart](/getting-started/quick-start), use delegations to send work to your existing [factory](/getting-started/glossary#factory). Prepare a Machine and deploy a Line before sending a request.

Delegate work by mentioning Islo in a connected tool. The factory Delegator reads the request, finds the right Line or existing run, and routes the work. You can follow progress and reply in the same conversation.

## Connect your tools

Open [Manage → Integrations](https://app.islo.dev/integrations) and connect the tools your team uses. A code task needs access to its GitHub repository. A ticket task needs the Linear connection; Slack requests need the Islo Slack app in the channel.

You can also connect a tool with `islo login --tool github`, `islo login --tool slack`, or `islo login --tool linear`. See [Authentication](/cli/authentication) for team and personal connection scope.

Each Agent also needs a [Machine](/concepts/machines) with the repository and tools for its work. Deploy a [Suggested Line](/use-cases/suggested-lines) or a [custom Line](/use-cases/custom-lines) before asking Islo to run it.

## Send a request

| Where                        | What to do                                                                                                        |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Slack channel                | Mention the Islo app and describe the work. Include an issue, pull request, or repository link when you have one. |
| Slack direct message         | Message the Islo app with the task and relevant links.                                                            |
| GitHub issue or pull request | Mention `@islo-agent` in a new issue comment, pull request review comment, or submitted review.                   |
| Linear issue                 | Mention `@islo-agent` in a new issue comment.                                                                     |

For a bug report, include what happened, how to reproduce it, and the repository. For a feature, link the planned ticket. The [issue triage](/use-cases/issue-triage), [feature delivery](/use-cases/feature-delivery), and [bug fix](/use-cases/bug-fix) guides show which Lines handle those requests.

On GitHub, Islo ignores comments that do not mention `@islo-agent`. The Delegator uses the issue or pull request context to find related work. On Linear, it uses the issue context the same way.

## Follow the delegation

The Delegator can start a Line run, pass your message to the Manager of an existing run, or answer a question directly. When it finds a run for the issue or pull request, your follow-up goes to that run's Manager. A reply in a Slack thread already tied to a run can go to its Manager without another triage step.

Progress, questions, and results appear in the originating Slack thread, GitHub conversation, or Linear issue. The platform sends those replies; Stage Agents do not need to post them. You can also open the factory's **Runs** page to inspect stages and events. Reply to a question in the thread, or use the run conversation and controls in the dashboard. See [Operate a run](/operate/runs) for stop, steer, and retry.

The [Manager and Delegator](/concepts/manager) guide explains their roles. Stage Agents use the connected tools through the [gateway](/cli/gateways) when they need repository, issue, or attachment data.

## Conversation and automatic triggers

An @ mention starts a conversation with the Delegator, which can answer, start a Line, or route the request to an existing run. An [integration trigger](/concepts/triggers) instead starts a Line when a configured provider event matches its selector. A [Line webhook](/concepts/triggers) starts a Line from an HTTP request. You can use an integration trigger to start work on a new pull request and mention `@islo-agent` on that pull request later to continue its run.