Skip to main content

# Updates and Agent Integration

## App Updates​

1. Click the version entry at the top of the main screen to open the update panel.
2. Click `Check for Updates` in the panel.
3. If a new version is found, the panel shows the version comparison and release summary.
4. Click `Apply Update` after confirmation; the service downloads and replaces the new backend and frontend assets in the background.
5. When the update finishes, the app restarts automatically. In tray mode, the tray app helps complete the replacement.

## Script Run Settings​

In `Settings → Script Run Settings`, you can control:

- whether `XXTLanControl.lua` is uploaded before running scripts
- whether it is also uploaded when running `<Selected on Device>`
- whether it is uploaded during bulk script upload to devices
- whether existing `XXTLanControl.lua` files inside `Script Directory` should be updated to the version bundled in the current control center

These settings mainly affect script execution and script asset maintenance.

## Skill Install Panel​

In `Settings → Skill Install`, you can install the bundled `xxtouch-script` Skill into clients that support Agent Skills. Built-in targets include:

- Claude Code
- Codex
- Claude Desktop (macOS / Windows, local plugin install)
- Claude Desktop 3p (macOS / Windows, local plugin install)
- GitHub Copilot
- Cursor
- Windsurf
- Antigravity
- Trae
- Qoder

Claude Desktop and Claude Desktop 3p are installed using Claude Desktop's local plugin format. The plugin includes both the `xxtouch-script` Skill and the `XXTLanControl` MCP connection, and requires local Node.js / npx. The plugin uses the short internal id `xxtlc` to keep plugin-scoped MCP tool names within Claude's tool-name limit, while the visible plugin name and MCP server name remain `XXTLanControl`.

## MCP Install Panel​

In `Settings → MCP Install`, you can install or remove agent integration for common MCP-enabled tools. New installs write the current backend `/mcp` Streamable HTTP URL by default. Existing standalone `xxtlancontrol-mcpserver` configs that point to the current local backend are migrated to HTTP automatically; configs pointing to another backend are left unchanged. Built-in targets include:

- Claude Code
- Codex
- Claude Desktop
- Claude Desktop 3p
- VS Code
- GitHub Copilot
- Cursor
- Windsurf
- Antigravity
- Trae
- TRAE CN
- TRAE SOLO
- Qoder

## Toolset Modes​

The install panel offers two toolset modes:

- `Development`: better for testing and debugging workflows
- `Full`: better when you want the agent to use more control-center features directly

Both the install actions and the configuration snippets follow the currently selected toolset mode.

## Target Control Center Address and Snippets​

- By default, MCP installation points to the current XXTLanControl `/mcp` URL.
- If you want the agent to connect to another control center, enter that target address in the panel and it will generate the matching `/mcp?toolProfile=...` URL.
- One-click install is enabled only for agents that support remote HTTP MCP. Unsupported agents show an unavailable state and do not fall back to writing `xxtlancontrol-mcpserver`.
- For agents that are not shown in the target list, you can copy the JSON or TOML HTTP snippets shown in the panel.

## Before You Use It​

- The backend `/mcp` endpoint does not require an access key by default. Any agent that can reach the backend port can connect.
- If you no longer need agent integration later, it is a good idea to remove it from the same panel first.