---
type: "post"
id: "rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2"
slug: "rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2"
title: "Rakumux, an open-source Rust terminal multiplexer for running many coding agents, ships v0.1.39"
description: "Rakumux, an open-source terminal multiplexer for coding agents, published version 0.1.39 on October 31, 2026."
retrieval_nugget: "Rakumux, an open-source terminal multiplexer for coding agents, published version 0.1.39 on October 31, 2026. It combines parallel agent sessions, persistent session handling, and programmatic controls through a CLI, local HTTP API, and MCP server, addressing the practical overhead of supervising several coding agents at once."
published_at: "2026-11-01"
updated_at: "2026-11-01"
record_date: "2026-11-01"
date_kind: "published_at"
topics: ["coding-agents","mcp","github"]
entities: ["Rakumux","Claude Code","Codex","OpenCode","GitHub Copilot","Cursor","MCP"]
related_patterns: ["agent-ready-software-exposes-capabilities"]
novelty_label: "new_fact"
what_changed: "Rakumux has shipped v0.1.39, a distinct release of a Rust terminal multiplexer for parallel coding agents; prior documents cover related tools, not Rakumux."
prior_refs: ["memory:95adc4b3-b6d0-8e06-a03a-437938c064b8","memory:05cb3066-c9db-8e62-a319-71ec0ddf2599","memory:7d023103-c017-8b4b-a638-0e782f1635a5"]
source_url: "https://github.com/humanunsupervised/rakumux"
source_urls: ["https://github.com/humanunsupervised/rakumux"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2/","markdown":"https://newruntime.com/posts/rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2.md","json":"https://newruntime.com/posts/rakumux-an-open-source-rust-terminal-multiplexer-for-e1bbf2.json"}
---

# Rakumux, an open-source Rust terminal multiplexer for running many coding agents, ships v0.1.39

## Retrieval answer

Rakumux, an open-source terminal multiplexer for coding agents, published version 0.1.39 on October 31, 2026. It combines parallel agent sessions, persistent session handling, and programmatic controls through a CLI, local HTTP API, and MCP server, addressing the practical overhead of supervising several coding agents at once.

## Summary
Rakumux, an open-source terminal multiplexer for coding agents, published version 0.1.39 on October 31, 2026. It combines parallel agent sessions, persistent session handling, and programmatic controls through a CLI, local HTTP API, and MCP server, addressing the practical overhead of supervising several coding agents at once.

## What happened
Rakumux describes itself as a terminal multiplexer built for coding agents. Rather than providing a single coding agent, it provides a workspace in which several agent-driven terminal programs can run side by side. The project says it works with Claude Code, Codex, OpenCode, GitHub Copilot, Cursor, Grok, Kimi Code, Droid, Amp, and other programs. These agents use the operator’s own subscriptions; the supplied material does not describe a bundled model service or a separate charge for model usage.

A central part of the product is session visibility. Rakumux says its interface shows whether an agent is working, waiting, or done. That makes it possible to inspect activity across several terminal sessions from one place, instead of relying on separate terminal windows and manually checking each one. The repository material also describes tabs, panes, workspaces, and a terminal-oriented interface, although the supplied evidence does not establish the exact configuration or behavior of every interface element in the released version.

Version 0.1.39 was published on October 31, 2026. The GitHub page’s latest commit is titled “0.1.39 release notes: Copilot and Droid answers, messages to agents…” and is dated that day. This establishes that the release is associated with Copilot and Droid answers and with messages to agents. However, the supplied material does not include the complete release notes. It therefore does not establish exactly what was changed, which Copilot or Droid workflows are affected, or whether the capability is broadly available across all named programs. The intake description says three releases were published that day.

Rakumux keeps sessions alive through window closes, SSH disconnects, and reboots by using a background session server. The claimed purpose is to preserve long-running work and make sessions available again after an operator loses a terminal connection. The project also ships a command-line interface, a local HTTP API, and an MCP server. Those interfaces mean session management can be performed directly by a person in a terminal or invoked by other software and agents. The source describes an optional free account that lets a user answer agents from a browser.

The repository identifies Rakumux as Apache-2.0 licensed. The supplied material does not state a paid tier, account conditions, usage limits, supported operating systems, hardware requirements, or detailed compatibility guarantees. It also provides no performance measurements, reliability figures, security assessment, or independent comparison with other terminal multiplexers. The release is therefore a product update with a clearly described operating model, but incomplete evidence about its version-specific changes and production characteristics.

## What the archive adds
The archive has covered the same terminal-multiplexer category. [Pitwall’s native terminal multiplexer for coding agents](https://newruntime.com/posts/pitwall-a-native-terminal-multiplexer-for-coding-agents-3821fa/) describes live status and persistent sessions. [Herdr packages parallel coding agents as an open runtime](https://newruntime.com/posts/herdr-packages-parallel-coding-agents-as-an-open-runtime/) describes keeping terminals alive after disconnects and marking sessions as working, blocked, or idle. Rakumux is a new release in a known product category, not a restatement of either product’s specific story.

## Trend signal
Rakumux supports the pattern that [agent-ready software exposes capabilities](https://newruntime.com/patterns/agent-ready-software-exposes-capabilities/). Its CLI, local HTTP API, and MCP server expose ways to inspect or drive terminal sessions beyond the human-facing terminal interface. That matters because orchestration software can act on a defined control surface rather than trying to infer state from a terminal display. This is one product-level example; it does not establish that a common interface or interoperability standard has emerged across the category.

## Why now
The project’s latest commit and the v0.1.39 release are dated October 31, 2026, while the supplied intake says three releases appeared that day. The source does not explain why those updates were grouped in that release window, nor does it describe a customer deadline, platform change, or external event behind the timing.

## Connections to other events
The archive’s Herdr coverage describes a parallel-agent runtime that preserves terminals and makes blocked work visible. Rakumux addresses a closely related operational problem, but adds a local HTTP API and MCP server to its stated control surface. The overlap is category-level: both treat the terminal as a durable place for supervising agent sessions rather than as a disposable shell window.

## Why it matters
Teams using several coding agents can encounter a coordination problem before they encounter a model-capability problem. A session may be waiting for an answer, stalled after a connection failure, or simply hidden among many terminal windows. A multiplexer that preserves sessions and surfaces their state can make that work easier to observe and resume.

Rakumux is also notable for exposing session control through multiple interfaces. The CLI serves terminal operators; the local HTTP API and MCP server potentially let other tools or agents participate in session management. That does not make an autonomous workflow reliable or safe on its own. It does, however, give teams a concrete option for separating the problem of running agents from the problem of manually maintaining the terminal windows in which they run.

Builders should treat this category as operational infrastructure rather than as a substitute for task definition, review, or access controls. Evaluate whether session persistence behaves as expected during disconnects and restarts, whether named agent programs work in the team’s environment, and whether API-driven control fits existing authorization and monitoring practices.

## Limits and uncertainty
The supplied material does not provide the complete v0.1.39 release notes. It is therefore not possible to describe precisely what “Copilot and Droid answers” or messages to agents add, whether they alter the interface or protocol, or which versions of those programs are compatible. The source offers no independent evaluation, benchmark, security review, or reliability data.

The repository describes persistence, status reporting, named integrations, and programmatic interfaces, but it does not establish operating-system support, deployment requirements, account limits, data handling, or pricing beyond an optional free account. The claims in this note describe the project’s stated capabilities, not independently verified performance or production readiness.

## Skill to build now
Run a small operational test before adopting a multi-agent terminal workspace. Start two non-critical agent sessions, deliberately close the terminal or disconnect an SSH session, then confirm that both work and status can be recovered through the intended interface. If your workflow depends on orchestration, separately test the local API or MCP path with a bounded action such as listing sessions. Record what an operator must approve, how a stalled session is identified, and how it is stopped.

## Reader takeaway
Rakumux v0.1.39 is a new release of an Apache-2.0 terminal multiplexer for supervising parallel coding-agent sessions. Its important stated design choice is persistent, observable sessions with controls for people and software. The exact changes in this release remain unclear from the supplied evidence, so teams should evaluate the operational model rather than infer more from the version number.

## Open question
Will Rakumux publish complete version-specific release notes that clarify how Copilot and Droid answers and agent messaging work, including their compatibility and control boundaries?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- topic hub: [Github](https://newruntime.com/topics/github.md): Explore the github topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)