tamux tamux daemon-first runtime

External interfaces

Gateway & MCP

Daemon-backed access for chat platforms and MCP clients, all routed through one shared runtime.

Chat gateways

The gateway layer lets Slack, Discord, Telegram, WhatsApp, and similar channels become operator entry points into the daemon. This means the user can launch or steer work from messaging platforms without creating a separate execution model.

MCP access

tamux-mcp exposes daemon capabilities to MCP-capable agents and toolchains. This lets external agent environments treat tamux as a durable system component rather than reimplementing sessions, tasks, or goal runners on their own.

{
  "mcpServers": {
    "tamux": {
      "command": "tamux-mcp"
    }
  }
}

One runtime

Whether a request comes from Electron, the TUI, the CLI, an MCP client, or a chat gateway, it still lands in the same runtime. That means goals, approvals, tasks, threads, and memory remain coherent across all of those entry points.

Operational benefits

  • Use Discord or Slack as a control channel without creating disconnected bot state.
  • Use MCP to let other agents drive tamux’s terminals, goals, and memory responsibly.
  • Keep approvals and provenance in the same governance model regardless of entry channel.