---
title: "Troubleshooting"
description: "What to do when Indent is stuck, takes a wrong approach, hits failing checks, suspends a session, or lacks access."
---

> 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.

# Troubleshooting

You fix most problems by telling Indent, in the session, what to do differently. Indent shows its
work as it goes, so you can see where it went wrong and redirect it.

## Indent is stuck or took a wrong approach

Send a message in the same session or Slack thread. You don't need to start over — Indent keeps the
full context and adjusts.

- **Point it at the problem.** "That's the wrong file — the handler lives in `src/api/`, not
  `src/routes/`."
- **Correct the approach.** "Don't add a new dependency for this; use the existing helper in
  `lib/http.ts`."
- **Reset the direction** when it has drifted. "Stop — let's step back. The goal is only to fix the
  timeout, not refactor the client."

Indent records corrections as [memory](/learning/memory), so the same misstep is less likely next
time.

## A review or CI check keeps failing

When a check on the pull request fails, Indent reads the logs and pushes a fix on its own. If it
doesn't catch one, or a fix doesn't clear the check:

- Ask Indent to make all checks pass — comment on the pull request or message the session.
- Tell Indent when a failure is unrelated to the change (a flaky test, a pre-existing break), and it
  won't chase it.
- Comment `@indent rebase` on the pull request to rebase a stale branch.

See [Writing code](/working-with-indent/writing-code) for how the session stays connected to the
pull request.

## A session has suspended

Sessions suspend when they've been idle. This is normal and nothing is lost. Send a new message and
the session resumes with all its context intact — the same repository, findings, and connected
integrations.

## Indent lacks access to something

If Indent says it can't reach a repository, database, or tool, the integration isn't connected or
isn't in scope for the session:

- **Connect the integration** from
  [**Settings → Integrations**](https://app.indent.com/settings/integrations). See
  [Connecting MCP servers](/connecting/mcp-servers) and the specific setup pages for
  [GitHub](/connecting/github), [Slack](/connecting/slack), and [databases](/connecting/databases).
- **Personal integrations require a private session.** GitHub, Slack, and databases are always
  organization-scoped, but MCP servers can be personal. Using a personal integration makes the
  session private. See [Private sessions](/collaborating/personal-and-private).

> **Note**
>
> If a task needs your application built and running and Indent only has a bare sandbox, set up an
> [environment](/getting-started/environments) and start the session there.

Source: https://docs.indent.com/working-with-indent/troubleshooting/index.mdx