# Implementation status

Source: https://libtmux.org/en/haskell/latest/guides/status/

> Implementation status: libtmux-haskell documentation.

Use the current package for typed input values. The public library cannot
yet observe or mutate a tmux server.

| Component | Available to consumers |
| --- | --- |
| Entity ID parsing/rendering | Yes, through [`LibTmux.Id`](<https://libtmux.org/en/haskell/latest/reference/libtmux-id/>) |
| Checked dimensions and indices | Yes, through [`LibTmux.Value`](<https://libtmux.org/en/haskell/latest/reference/libtmux-value/>) |
| Stable-release parsing and supported-range admission | Yes, through [`LibTmux.Version`](<https://libtmux.org/en/haskell/latest/reference/libtmux-version/>) |
| Client, complete captures and generation-bound references | In progress |
| Typed query evaluation and commands | Not implemented |
| Control events, streams and cancellation API | Not implemented |
| Workspace library/CLI | Planned as a separate Cabal package using the core |
| MCP integration | Excluded from this port |

The internal graph, socket pin and process owner have separate tests. Their passing results do not establish a public automation interface.
The [behavior inventory](https://github.com/libtmux/libtmux-haskell/blob/581f0ee45016ffb2283366bb1edc1658df26c5ed/docs/contracts/README.md) records the intended scope.

## Package policy

The core favors GHC boot libraries and ordinary [`IO`](<https://hackage-content.haskell.org/package/base-4.22.0.0/docs/System-IO.html#t:IO>). Additional dependencies
need a concrete requirement; JSON/YAML loading and command-line concerns
belong in the workspace package. MCP is outside this port's scope. See the
[package and dependency policy](https://github.com/libtmux/libtmux-haskell/blob/581f0ee45016ffb2283366bb1edc1658df26c5ed/.github/CONTRIBUTING.md#package-and-dependency-policy).

## Compatibility evidence

CI uses GHC 9.14.1, GHC2024 and Cabal 3.18.2.0 on Linux x86_64. Its current
integration subset exercises owned fixtures, scalar framing, private socket
pins and process ownership with one and two RTS capabilities on exact tmux
releases 3.3a and 3.8. The supported range includes all intermediate releases;
CI tests its endpoints.

The [workflow](https://github.com/libtmux/libtmux-haskell/blob/581f0ee45016ffb2283366bb1edc1658df26c5ed/.github/workflows/ci.yml) and
[test guide](https://github.com/libtmux/libtmux-haskell/blob/581f0ee45016ffb2283366bb1edc1658df26c5ed/.github/TESTING.md) describe those checks. This is evidence
for the implemented subset, not complete tmux API compatibility.

No package-performance benchmark results are published. Test and private
probe durations do not measure an installed public transport.