> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-mobile-chat-stability-54bd7ef0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Chat capabilities

> What ADE chat agents can do inside a lane or PR context.

The exact tools depend on provider, permissions, and project setup, but most ADE chat sessions can do the following.

<CardGroup cols={2}>
  <Card title="Read and edit files" icon="file-code">
    Search the repo, inspect files, apply edits, and explain changes.
  </Card>

  <Card title="Run commands" icon="terminal">
    Use the lane terminal for tests, builds, package managers, scripts, and local tools.
  </Card>

  <Card title="Use Git" icon="code-branch">
    Check status, inspect diffs, stage files, commit, push, and manage branches.
  </Card>

  <Card title="Work with PRs" icon="code-pull-request">
    Create PRs, update descriptions, read CI failures, respond to comments, and help resolve review feedback.
  </Card>

  <Card title="Use Linear" icon="layers">
    Read linked issues, update issue context, and attach useful outcomes when Linear is connected.
  </Card>

  <Card title="Capture proof" icon="camera">
    Attach screenshots, recordings, traces, logs, or verification notes to the work.
  </Card>

  <Card title="Handle images" icon="image">
    Accept screenshots, mockups, and diagrams as message attachments.
  </Card>

  <Card title="Ask for input" icon="circle-question">
    Pause cleanly for a choice or clarification instead of guessing.
  </Card>
</CardGroup>

## Good chat requests

```text theme={null}
Find why the billing test fails and fix the smallest underlying bug.
```

```text theme={null}
Update the PR description from the current diff and include test evidence.
```

```text theme={null}
Read the auth module and explain where the redirect state is stored.
```

## Review before trusting

Agent chat is powerful because it can change real files. Treat the result like any human contribution: inspect the diff, run relevant checks, and read the final summary.