ChatGPT & integrations

Start with ChatGPT. Connect the Windows PC you already use.

LocalCommander is built so an AI client can move from conversation to real work on your computer. ChatGPT is the main product path today; other MCP-compatible clients can use the same remote service where their product supports it.

Works now

ChatGPT + LocalCommander Windows

Connect LocalCommander in ChatGPT, authorize your account, pair a Windows PC and then use LocalCommander from a normal conversation.

  • ✓ Work with local files
  • ✓ Use browser pages and downloads
  • ✓ Operate supported Windows apps
  • ✓ Run approved terminal and process tasks
  • ✓ Return files and results to the conversation
Current manual setup

Until the public listing is live, connect it through ChatGPT Developer Mode.

Setup is done in ChatGPT on the web. Add the LocalCommander remote MCP endpoint, complete OAuth, let ChatGPT scan the tools and then select LocalCommander in a new conversation.

Current OpenAI limitation

OpenAI currently documents full MCP write/control actions in Developer Mode for Business and Enterprise/Edu. Pro can connect custom MCP but is currently limited to read/fetch actions.

Installation guide →
Other clients

The same remote service can be used by MCP-compatible clients.

Compatibility depends on the client: it must support authenticated remote MCP and the actions you want to use. LocalCommander does not bypass the client’s own approval or permission model.

Primary path

ChatGPT

The product flow we optimize first.

Developer workflows

Codex

Useful when coding work needs the same Windows machine.

Compatibility path

Other MCP clients

Use where the client supports remote MCP + OAuth.

What stays simple

One account. One paired PC. The AI client is just the front door.

01Account

Owns your devices, plan and authorization.

02Windows app

Runs on the machine and stays connected.

03AI client

Sends the task and receives the result.

For technical teams

Need the protocol details instead?

The production Windows app uses an authenticated remote MCP endpoint and an outbound connection from the paired Windows companion. Detailed scopes, control layers and architecture live in the docs.