Build an ACP editor

​

What you will have

• An ACP app with one Reason provider.
• A thread that runs pwd on this Mac and on a Reason cloud computer, with both results in the reply.
• That thread visible in the Reason app, and continuable with reason send.

​

Prerequisites

curl -fsSL https://reasonmachines.com/install.sh | bash
reason login --pair CODE     # CODE from Settings > Network; picks the Workspace
reason whoami                # must name the Workspace the app should use
reason connect               # this computer runs Sessions that use it
reason acp --help            # confirms the installed reason acp

​

Configure the provider (T3 Code example)

command -v reason

{
  "providerInstances": {
    "reason": {
      "driver": "acpRegistry",
      "displayName": "Reason",
      "config": {
        "source": "local",
        "commandPath": "/absolute/path/to/reason",
        "commandArgs": ["--workspace", "your-workspace-slug", "acp", "-y"]
      }
    }
  }
}

• commandPath is the absolute path from command -v reason.
• commandArgs is hidden in T3’s settings screen. It is --workspace SLUG acp -y: --workspace names the Workspace slug (check it with reason whoami), and -y accepts the defaults so a thread does not stop to ask.
• The REASON_WORKSPACE environment variable does the same job. It arrives in the next CLI release; until then, use the --workspace argument above.

​

Verify

1. Start one thread and send: Run pwd on this Mac and on a Reason cloud computer. Report both results.
2. The reply shows two paths: one from this Mac, one from a cloud computer.
3. The Session appears in the Reason app.
4. Continue it from a terminal: reason send SESSION_ID "Run whoami." The reply appears in the thread after you reopen it.

​

Optional: your own fork identity

• bundle identifier,
• data directory,
• Electron profile,
• and no update feed, so it never installs the upstream build over itself.

​

Reference fork

• Repository: svemyh/t3code, branch reason-provider.
• The Reason-specific code is in seedReasonInstances in apps/server/src/provider/ProviderInstanceRegistryHydration.ts. Everything else is upstream T3 Code.

​

ACP Registry