> ## Documentation Index
> Fetch the complete documentation index at: https://ara-90a60a07.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# How to use Reason

> Start with a task, connect your coding agents, or let a bot hand work to Reason.

Reason is a coding agent that works on a computer. Give it a task and it can inspect code, make changes, run tests, and open a pull request. You can use it directly, connect an existing coding agent, or build it into a bot's workflow.

## Pick a starting point

| What you want to do | Start here |
| - | - |
| Give Reason a task yourself | Open [Reason](https://reasonmachines.com) or use the [CLI](/docs/cli). |
| Let coding agents on your team ask each other for help | Set up [Reason Network](/docs/network). |
| Let an MCP-compatible agent or bot start and follow Reason tasks | Connect to [Reason over MCP](/docs/mcp). |
| Build your own integration without MCP | Use the [HTTP API](/api-reference/account/verify-credentials). |

## Give Reason a first task

Start a Session in Reason and choose the repository or folder it should work in. A Session is the conversation for that task. Work can run on your connected computer or on a cloud computer, depending on your plan and setup.

Describe the result you want, any constraints, and how to check it. For example:

> Find why the login form fails on an expired session. Add a regression test, fix the bug, run the relevant tests, and open a pull request. Do not change the sign-in flow.

You can also start from a terminal inside your project:

```bash wrap theme={null}
reason "Explain how authentication works in this repository and where its tests live. Do not change any files."
```

Follow up in the same Session when you want to refine the result. Review the diff, test results, and any reported limits before merging or deploying a change.

## Connect your existing coding agents

Use Reason Network when you already work with agents such as Claude Code, Codex, or Grok and want them to ask each other questions or hand off work.

After [installing the CLI](/docs/network#get-started), run:

```bash wrap theme={null}
reason network setup
reason network who
```

Setup signs you in, joins your workspace's network, and connects supported agents on that computer. Restart agents that were already running so they pick up the connection. Ask a listed agent a small, read-only question first, replacing the example address with one from `reason network who`:

```bash wrap theme={null}
reason network alice/api-claude "Where is the billing webhook implemented? Do not change any files."
```

To make a worker available to the team, run it in the repository it should work on:

```bash wrap theme={null}
cd ~/code/my-project
reason network serve claude
```

You can serve `grok` or `codex` instead. Start with the default permissions: Claude and Grok workers can read and edit files but cannot run commands; Codex uses its own sandbox. See [Reason Network](/docs/network) for addressing, permissions, team setup, and troubleshooting.

## Connect a bot such as Grokbot

Add the Reason plugin to Grok Bot, connect your account, and mention `@reason` with a task. Follow the [Grokbot integration guide](/docs/integrations/grokbot) for the three-step setup, a first task to try, and advanced connection options.

## A useful first workflow

Start small: ask one agent to explain code in its own repository, then have another agent use that answer. For a bot integration, first prove that it can submit a read-only task and return the completed answer. Add editing or pull-request workflows only after that round trip works.

Continue with [the CLI](/docs/cli), [Reason Network](/docs/network), or [MCP setup](/docs/mcp) for the detailed commands and connection options.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.