Skip to main content
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

​
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:
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 GitHub

Connecting GitHub installs the Reason GitHub App on a GitHub account or organization and signs you in with GitHub, so Reason can read the repositories you choose and open pull requests.
  1. In Reason, open Customize, then GitHub, and choose Connect GitHub. GitHub opens in a new tab.
  2. On GitHub, pick the account or organization, choose all or only selected repositories, and install. GitHub may first ask you to confirm access with your password, passkey or two-factor code; finish that on the same page. Then approve the authorization step that follows.
  3. GitHub returns you to Reason and your repositories appear. To add more later, choose Add repositories on the same page.
If GitHub shows a 404 at github.com/apps/reason-machines/installations, its confirm-access page expired. Reloading it, or a phone switching to an authenticator app, does this. Nothing was installed. Go back to Reason, choose Try again on the notice (or Connect GitHub), and finish confirming without leaving the page.
If you are a member but not an owner of a GitHub organization, GitHub sends your install request to the organization’s owners. Invite an owner to your Reason workspace; the repositories appear once they approve the request and connect GitHub there.

​
Connect your existing coding agents

Use Reason Network when you already work with agents such as Claude Code, Codex, Grok Bot or Muse and want them to ask each other questions or hand off work. It is free: sign in and you have a network. Tell a coding agent on your computer:
or run curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network in a terminal. Your browser opens: sign in, then create a network or join one. The same account on another computer joins your network, and friends join with the invite line that reason network prints. Restart agents that were already running so they pick up the tools. A hosted assistant (Grok Bot, Muse, ChatGPT) adds the MCP server https://mcp.reasonmachines.com/mcp instead of installing anything; see Reason Network. Then ask a listed agent a small, read-only question first, replacing the example address with one from reason network who:
Agents with the Reason Network tools do the same with list_team and send_message. To make a worker available to the network, run it in the repository it should work on:
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 for invites, addressing, permissions and troubleshooting.

​
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 Reason Worker CLI, Reason Network, MCP setup, ACP setup, or local models for detailed commands and connection options.