01
Files, with context
Find a file, read its contents, and make a precise edit. Work inside the directories you’ve allowed.
read_file · edit_block · start_search FROM CONVERSATION TO COMPLETION
Your next idea.
Your own computer.
Connected.
Give your AI a way to work with your real files and tools. Commander connects your conversations to the computers you choose—with control at every step.
BUILT FOR REMOTE MCP
ChatGPT/Claude/Your MCP client
A CONVERSATION, IN ACTIONInteractive preview
My workstationYour registered computer
OnlineFind the project notes and summarize what changed.
↳start_search✓
/projects/notesrelease-notes.md architecture.md decisions.md
What would you like to do next?↑
◇ You choose access↗ Actions stay visible
REAL TOOLS. ONE CONNECTION.FilesTerminalGitDockerProcesses
LESS BACK-AND-FORTH. MORE DONE.
Your tools,
part of the conversation.
Move from a question to a real result without carrying files and command output between windows.
02
Commands that keep going
Start a process, follow its output, and return to the result. Long-running work stays visible in sessions.
start_process · read_process_output03
Your development workflow
Inspect Git changes and work with Docker containers using the tools already on your computer.
git_status · git_diff · docker_logs04
One place to stay in control
See connected devices, review activity, manage permissions, and revoke access when you’re done.
Devices · Activity · SecurityONE SETUP. A NEW WAY TO WORK.
Make the connection.
Your AI client, Commander, and your agent. Each has a clear role.
Create your workspace
Sign in with Google or Apple. Manage your devices and AI connections in one place.
Register your computer
Run the Commander agent, enroll with a one-time token, and choose allowed folders and command settings.
Connect your AI
Add the MCP address to your client, sign in, and review the requested permissions before starting.
YOUR MCP ENDPOINT
https://rdc-api.duckdns.org/mcpGoogle and Apple sign-in setup is in progress. Agent installation and permissions are configured separately.
Read the setup guideCAPABLE BY DESIGN. CONTROLLED BY YOU.
Give access.
Keep control.
A useful connection should be an understandable one. Know what is connected, what is allowed, and what happened.
How data is handledExplicit permissions
Set file directories on the agent. Configure terminal access and approval policies separately.
An activity trail
Review recorded tool activity and follow execution progress on your agent.
Access you can revoke
Revoke a device or an AI connection from your workspace. Your local files stay on your computer.
A FEW THINGS TO KNOW
Good questions.
Clear answers.
Does Commander control my screen?+
Commander connects AI tools to files, terminal commands, Git, Docker, and processes. It does not currently stream your screen or operate your mouse.
Where do my files go?+
Your working files remain on your computer. Requested file content and command output travel through the Commander relay to the AI service you connect. Review that AI service’s data policies too.
Can I use ChatGPT and Claude?+
Commander provides a remote MCP endpoint with OAuth. Connect it from an AI client that supports remote MCP. Available connector settings depend on your AI client and account; this is not an official OpenAI or Anthropic product.
Which computers can I connect?+
The Windows agent has been tested. Linux deployment and agent source are available; Linux/ARM validation is still limited. macOS support and Apple Silicon/Intel build scripts are prepared, with native Mac build and execution validation pending.
Are terminal commands limited to allowed folders?+
Allowed directories constrain file tools. Terminal commands run with the agent user’s operating system permissions and are separately controlled by command settings and approval policies. Enable only the capabilities you need.
THE NEXT STEP IS YOURS
Bring your ideas closer to done.
One connection between your conversations and your computer.
Open Commander