# Support and release stages

Source: https://libtmux.org/ja/meta/support/

> What the concept badge and the release stages on libtmux.org mean, and how to report a failing example.

Menus and install pages label each product with a badge. This page says what the badges mean.

## Concept and alpha

**Concept** is a support scope. The MCP servers and workspace builders for every language except Python are maintained examples of using libtmux in a real application. They carry no support or compatibility commitment, and their APIs, MCP tools, command output and workspace configuration can change. Pin an example and the core library together when you adapt one.

**Alpha** is a release stage. Publishing a package or adding commands does not change an example's concept scope, so an alpha core library can have concept examples beside it.

## Release stages

A badge shows the stage that the package's registry declares, or the stage of the newest version the registry lists: **pre-alpha**, **alpha**, **beta**, **rc** or **stable**. When the registry lists no release at all, the badge shows the stage of the repository's newest release tag instead, and a tag that is exactly `MAJOR.MINOR.PATCH`, with an optional leading `v` or package label, such as `v0.1.0`, reads **stable**. A tag newer than the registry's newest version does not count: a registry that lists only `0.1.0-alpha.2` shows **alpha** even after the repository tags `v0.1.0`. A package with no release and no release tag shows **unreleased**. A language without an implementation has no badge.

Python's `tmuxp` workspace loader and Python MCP server show the stage their PyPI projects declare instead of **concept**.

## Use an example

Open the MCP or Workspace Manager entry for your language. Its install page names the package or source build, the runtime it needs and the tmux endpoint it talks to.

An MCP tool can send shell input, and a workspace file can configure shell commands. Keep tmux access local or behind access controls you own. A concept badge adds no authentication, authorization or isolation. If you run an example in production, you own its configuration compatibility, upgrades, access controls and monitoring.

## Report a failure

An example has to work at its documented revision. Load a workspace and inspect the session, or connect an MCP client and call a tool, against a [separate tmux server](https://libtmux.org/en/tmux/latest/manual/full/#DESCRIPTION) so your own sessions stay untouched. A page that renders or a package that installs does not show that the example works.

Report the revision, the tmux version, the smallest input that fails and the error you saw. If the failure comes from the core library, reduce it to a core API call: an example's concept scope does not excuse a broken core contract.