Attyx v0.4.10

Drive Attyx from MCP clients

Attyx now speaks MCP, exposing its full command surface as typed tools so apps like Claude can drive your terminal — list and create panes and tabs, send keystrokes, read pane output, manage sessions, and check agent status. (#264)

There are two ways to connect:

attyx mcp — a stdio bridge for clients that launch a subprocess. In Claude Desktop, point it at {"command": "attyx", "args": ["mcp"]} and it talks to your running Attyx over the existing control socket. Works on every platform.
In-app HTTP server — Attyx hosts an MCP endpoint at http://127.0.0.1:7333/mcp for as long as the app is running, the same way local desktop apps like Figma Dev Mode and JetBrains expose MCP. POSIX-only for now.

Configure it under the new [mcp] section:

[mcp]
# enabled = true
# host = "127.0.0.1"
# port = 7333      # 0 disables the HTTP listener; the stdio bridge stays available

It’s enabled by default and bound to 127.0.0.1 only. Because the tools run real terminal commands, the endpoint stays on loopback and never reaches the network.

More reliable opencode status dots

The opencode agent-status integration now registers its plugin in your opencode.json(c) instead of relying only on the plugin directory, so the status dot lights up reliably across opencode releases. Existing setups are migrated automatically, and your config’s comments and formatting are preserved. (#263)