v0.1.1

agent-runtime-mcp v0.1.1

v0.1.1 is the first formal GitHub Release path for the accepted Channel MCP and packages the reliability work integrated after the initial runtime-bundle baseline. The public MCP contract remains unchanged at exactly six Tools.

What changed

Structured tmux Channel identity

Successful tmux Channels expose backend-owned mechanical identity through:

backend_metadata.tmux
├── session_name
├── window_id
├── window_index
├── pane_id
└── pane_index

This lets an upper layer select the intended host tmux Channel without parsing title, cwd or terminal output. channel_id remains the mutation address and the six public Tool names are unchanged.

Stdio compatibility regression coverage

The release includes the accepted regression coverage for stale/pre-initialize stdio traffic. A claim-less pre-initialize tools/list response is bounded, the same stdio child remains alive, later initialization on that same connection succeeds, and ordinary MCP traffic continues afterward.

This is server-side compatibility evidence. It does not claim ownership of ChatGPT conversation binding, reconnect/rebind behavior, transport supervision, or provider lifecycle.

Deployment-layer tmux keeper/recovery

The runtime bundle now includes the accepted operator-side helper:

deployment/tmux-endpoint-keeper.sh

ensure idempotently restores the reserved keeper session when the configured tmux endpoint is missing; status reports availability without mutation. Endpoint creation, supervision and recovery policy remain deployment/operator responsibilities. The MCP itself never creates, restarts or destroys tmux endpoints.

Runtime package and release path

The package/runtime version is 0.1.1. Runtime archive names derive from package.json rather than a hard-coded historical version. The release bundle contains:

compiled dist/src runtime
production package.json + package-lock.json
README deployment/runtime guidance
deployment/tmux-endpoint-keeper.sh
optional repository LICENSE when present

It excludes source, tests, repository scripts, build configuration, development dependencies and preinstalled node_modules.

Normal CI clean-room installs the extracted archive with npm ci --omit=dev, exercises the compiled stdio server, verifies the exact six public Tools, and proves keeper recovery using the helper from the extracted package path.

Formal publication is tag-driven. A v*.*.* tag must exactly match v${package.json.version} and must have a matching checked-in docs/releases/<tag>.md before the release workflow can build and publish assets from that exact tagged commit.

Compatibility boundary

The public MCP Tool surface remains exactly:

list_channels
get_channel
read_channel
write_text
send_control
health

This release does not add:

• Worker, Agent, Task or application semantics;
• product-owned tmux/session/process lifecycle;
• a raw shell or raw tmux public Tool;
• tunnel, proxy, network, TLS, DNS, firewall or provider configuration;
• npm registry publication.

package.json remains private: true.

Upgrade / installation

Download the release .tar.gz and matching .sha256 asset, then verify and extract them:

sha256sum -c agent-runtime-mcp-v0.1.1.tar.gz.sha256
tar -xzf agent-runtime-mcp-v0.1.1.tar.gz
cd agent-runtime-mcp-v0.1.1
npm ci --omit=dev

Prepare an application tmux endpoint outside the MCP, or use the packaged deployment helper to establish the reserved keeper endpoint:

TMUX_SOCKET_NAME=agent-runtime ./deployment/tmux-endpoint-keeper.sh ensure
TMUX_SOCKET_NAME=agent-runtime ./deployment/tmux-endpoint-keeper.sh status

Then start the stdio MCP server with the desired tmux visibility configuration:

TMUX_SOCKET_NAME=agent-runtime npm start

See the packaged README.md for the full runtime/deployment boundary and configuration variables.

Known limitations

• tmux session names and window/pane indices are current mechanical snapshots and may change under native tmux rename, reindex or layout operations.
• A deployment supervisor/operator must decide when to invoke keeper ensure; this release does not install systemd, Docker, a scheduler, or another generic supervisor.
• Network exposure, authentication and transport security remain deployment concerns outside the Channel MCP.
• The release workflow verifies the generated SHA-256 from the actual archive. This note intentionally does not contain a precomputed artifact checksum; the authoritative checksum is the .sha256 release asset produced from the tagged commit.