---
title: "Your new AI coworker"
description: "Indent is an AI coworker that completes tasks by executing real tool calls on a real computer, then reports what it did and how it verified the result."
---

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

# Your new AI coworker

Indent is an AI coworker. Hand it a task the way you'd hand one to a colleague: a bug to fix, a
question about your data, a document to review. It works on a real computer with the tools your team
already uses, so it can run commands, edit files, query your databases, and click through a browser,
then shows you exactly what it did and how it verified the result.

### Indent for engineering

## Connect Indent to your environment

Every system you connect gives Indent more context to draw on, and the effect compounds: the more of
your stack it can see, the more of a task it can complete from start to finish. A development
environment ties the rest together. With your application built and its services running, Indent can
reproduce a problem, make the change across your codebase, and verify the fix against your real data
and tools before it opens a pull request. Every step below is optional and can be done whenever you
need it; each notes what Indent can't do until you complete it.

1. **Connect GitHub**

Open [**GitHub in Integrations**](https://app.indent.com/integrations/github%3Aworkspace) and select **Install GitHub app**. Install the Indent GitHub App for the repositories you want. Indent clones them to read and write code, run and test your application, and open pull requests.

Skip it and Indent can't read or write your code or open pull requests.

See [Connecting GitHub](/connecting/github).
2. **Set up an environment**

Pick a repository and select **Setup Environment** to build a reusable development environment: a Docker image, repositories to clone, build and runtime variables, and the services your application needs, with a check that confirms the setup works.

Skip it and sessions run in a bare sandbox: your code is there, but not your running application, so Indent can't build the app, start its services, or exercise it in a browser.

See [Setting up environments](/getting-started/environments).
3. **Connect your data and tools**

From [**Integrations**](https://app.indent.com/integrations), connect the systems your work depends on: PostgreSQL, BigQuery, or ClickHouse databases, plus Datadog, Sentry, Notion, Linear, and HubSpot through MCP. Each integration's page shows its available organization and personal connection options.

Skip it and Indent can't query your data or pull evidence from those tools until they're connected.

See [Connecting MCP servers](/connecting/mcp-servers) and [Permissions and data](/administration/permissions-and-data).
4. **Bring Indent into Slack**

Open [**Slack in Integrations**](https://app.indent.com/integrations/slack) and connect your workspace. Invite `@indent` to a channel with `/invite Indent`, then mention `@indent` to start.

Skip it and you work with Indent in the web app instead of from Slack.

See [Connecting Slack](/connecting/slack).
5. **Run your first task**

Start a session in the [web app](https://app.indent.com) or mention `@indent` in Slack, and hand it a task in plain language: review an open pull request, answer a question about your data, or make a small code change. Indent does the work and reports what it did and how it verified the result.

## Give Indent any task

- **Write and ship code** — Indent explores the codebase, makes the change, runs the tests, and opens a pull request.
- **Query and analyze data** — Indent writes the query, returns the numbers, and plots them.
- **Investigate an incident** — Indent follows an error through your logs, traces, and code to the root cause, then proposes a
fix.
- **Review pull requests** — Indent reads the diff, tests the change, and works with you in the comments to get it merged.

## Use Indent from anywhere

- **Web app** — Start and manage your Indent sessions from the web, with file, query, and pull-request output
rendered inline.
- **Slack** — Mention `@indent` in a channel, or send a direct message.
- **GitHub** — Indent reviews pull requests and replies in comment threads; mention it to continue in the
thread.
- **Desktop app** — Runs Indent on your own computer, in a folder you choose.

## Teach Indent to get better

Indent works best with context, and it accumulates. Each of these teaches Indent something it reuses
on every later task, so you explain your codebase, your conventions, and your workflows once instead
of every session.

- **AGENTS.md** — Repository instructions Indent reads at the start of any session that includes the repo, so it
begins knowing your architecture, build and test commands, and house conventions.
- **Skills** — Reusable workflows you commit to the repo. When a task matches, Indent pulls in the procedure
and runs your multi-step process the same way every time.
- **Memories** — Durable facts Indent records as you work, such as your preferences and how you like results
reported, then applies in later sessions. Tell it to remember or forget something directly.

See [Getting good results from Indent](/working-with-indent/getting-good-results).
### Indent for knowledge work

## Automate routine work

Some work repeats: on a schedule, or every time something lands in a channel. Describe it to Indent
once and it handles each occurrence on its own. Point it at a Slack channel and it runs whenever a
new message arrives, summarizing customer feedback as it comes in, drafting a first reply, or
researching each new signup and posting what it found in the thread. Or give it a schedule, like
every weekday at 9am, and it runs on its own and posts the result where you want it, no triggering
message needed. You set it up in plain language right from Slack: tell Indent what you want and it
configures the trigger, then sends you a link to review or change it. See
[Creating automations in Slack](/automating/automations).

## What to hand Indent

### Research a lead or a company

Give Indent a company name or a link to a [HubSpot](/connecting/mcp-servers) record. It searches the
web, pulls the account's notes and history from your CRM, and hands back a short brief with the
people, the timeline, and the open threads worth knowing before your next call.

### Review a document or spreadsheet

Attach a file to your message and tell Indent what to check. It reads the spreadsheet or doc, flags
inconsistent numbers and broken formatting, fixes what you ask it to, and returns the corrected file
for you to download.

### Answer a question about your data

Ask in plain language. Indent writes the query for you, runs it against your
[connected database](/connecting/databases), and returns the numbers as a table, a chart, or a
downloadable file, without you touching SQL.

### Turn customer feedback into next steps

Point Indent at a Slack channel or a doc full of responses. It reads through them, groups the
recurring themes, calls out what's urgent, and drafts a summary that says which team should pick up
each item.

### Draft a first version

Hand Indent the context and let it write the first pass: a reply to a customer, a summary of a
meeting, or a project update in [Notion or Linear](/connecting/mcp-servers). You review and refine
instead of starting from a blank page.

## Work with your whole team

Every session is multiplayer. Teammates can jump in and work alongside you with full context, and
Indent knows who's on your team. See [Multiplayer sessions](/collaborating/multiplayer).

## Where you work

- **Slack** — Mention `@indent` in a channel, or send a direct message. If Indent isn't in the channel yet,
invite it with `/invite Indent`.
- **Web app** — Work more closely with Indent to visualize data, fine-tune a report, or watch what it's doing in
its browser. From a Slack session, Indent links back to the session on the web, where you can
browse every past session.

## Connect your tools

Indent works with the tools your team already uses, including Slack, databases, Notion, Linear, and
HubSpot. Open [**Integrations**](https://app.indent.com/integrations) to connect them. Each
integration's page shows its available scopes. See
[Connecting MCP servers](/connecting/mcp-servers).

## Indent remembers

As you work, Indent records durable facts, such as your preferences, your team's conventions, and
how you like results reported, then applies them in later sessions. Ask it to remember or drop
something directly. See [Memories](/learning/memory).

Source: https://docs.indent.com/index.mdx