Skip to main content
You will know which Reason interface to build on after this page. All four start and follow Sessions in the same Workspace, and a Session started by one shows in the others.

​
What you will have

A decision, and a link to the page that builds it.

​
Prerequisites

reason whoami names the account and Workspace. Your app’s key or sign-in must come from the same Workspace.

​
The four interfaces

ACP is not an API. It is the protocol between an editor and reason acp, and reason acp calls the HTTP API for you. Use the API directly when you need events, polling, or your own UI.

​
Decide in three questions

  1. Who starts the work? A person in an editor: ACP. A person in your product: the API. An agent that already runs your tools: MCP. A script: the CLI.
  2. Where should commands run? On this computer, on a Reason cloud computer, or both in one Session. The computers page explains each choice and what it needs. When an agent places the work itself, it runs work on your own files, apps or sign-ins on your connected computer, and heavy or long work in the cloud.
  3. Who signs in? An editor or CLI uses your reason login. A server or product uses an API key with the scopes it needs. See Authentication and scopes.

​
Check it works

Run one read-only Session from the path you chose. For the CLI:
The command prints a result and a Session ID, and the Session appears in the Reason app. The API, ACP and MCP paths each have their own check on their page.

​
Next