agenterm

Let agents control any remote computer, anytime, anywhere. Self-hosted AI agent remote assistance via MCP and terminal.

Automatically checked · GitHub checked 2026-11-12

agenterm

Overview

Agenterm

Agenterm

Let an AI agent assist with a remote computer through one authorized connection command.

Supports macOS, Linux, and Windows Supports CLI and GUI Supports MCP Streamable HTTP Apache 2.0 license

🔗 Multiple devices · ⚡ One-click connection · 🪶 Lightweight · 🔓 No SSH required · 🤖 Agent-first

🚀 Quick start · 📥 Download client · 🏠 Self-host · 简体中文

An agent creates an invitation, the target computer authorizes access, and the task runs

Create invitation → Authorize access → Connect device → Run task

Full demo · 1 min 42 sec

🚀 Quick start

Connection workflow: connect Agent to MCP, ask Agent to generate a connection command, share the command, the recipient runs it and grants access, then Agent provides remote assistance

  1. Connect your agent: Add the MCP service https://agenterm.net/mcp to an agent that supports Streamable HTTP. See configuration examples.
  2. Invite and authorize: Ask the agent to create an invitation and privately share the invitation page's short link containing a six-character code, for example agenterm.net/c/xef2k1. The other person opens it on the computer that needs assistance; the page guides them through authorizing remote access.
  3. Start assisting: Once the device connects, tell the agent what to do. The other person can see commands and output and disconnect at any time.

Agenterm invitation page with connection options and commands

Share the short invitation link so the recipient can follow the page to authorize remote access.

Connections grant terminal access with the target computer's current user permissions. Only authorize people you trust.

💡 When to use it

  • Help a colleague or customer troubleshoot: Let your agent inspect the remote environment and logs without passing commands and output back and forth.
  • Help family with computer problems: Once they run the client and authorize access, use your familiar agent to assist through the terminal.
  • Work on another development machine or server: Keep using your existing agent without configuring a full agent and model account on the target machine.
  • Check multiple computers: Connect test machines, inspect their environments, and summarize the results.

Interactive terminal tasks are supported. Use the CLI or GUI on the target computer to follow progress; the client automatically attempts to reconnect after temporary network failures.

🔗 How it works

Agenterm architecture: AI Agent connects over MCP to the Server, which relays commands and results over WebSocket to the Client and local shell

The agent and target computer connect through the server. After running the client, the person at the target computer can authorize terminal assistance without opening an inbound port.

Use the hosted service or deploy your own server.

☁️ One-Click Deploy

Deploy on RepoCloud

❓ FAQ

What if a connection fails or an invitation expires?

Check that both sides can reach the service. If an invitation no longer works, ask the agent to create a new one. For version mismatches, use the server and client from the same release. Connection troubleshooting.

Will tasks resume automatically after a disconnection?

The client attempts to reconnect but does not replay commands. Ask the agent to check the device and task state. Connecting a device does not wake an agent conversation that has already ended.

Can I control a desktop or connect several computers?

Agenterm provides terminal assistance, not a remote desktop. Ask the agent for a multi-device invitation to work across computers. Windows supports simple interactive prompts; full-screen programs requiring a real terminal may not work.

What are the hosted service limits?

Management access currently requires no authentication. The number of online devices is limited per invitation creator's IP address. The agent, server, and target client can see commands and output, so keep invitations and tokens private. Use HTTPS when self-hosting publicly.

User guide · Deployment and source builds · Report an issue · Apache-2.0