mngr-ttyd
Web terminal plugin for mngr.
A plugin for mngr that automatically launches a ttyd web terminal server alongside each agent, giving you browser-based terminal access to the agent.
Requirements
ttyd must be on the host's PATH. When it is missing, the plugin installs 1.7.7 from the
upstream GitHub release, but only onto a host where that can actually work:
- Linux with a writable
/usr/local/bin, or with passwordlesssudo: installed automatically. - macOS: not installed. The upstream release ships Linux binaries only, so there is nothing
to fetch. Run
brew install ttydyourself. - Anywhere
/usr/local/binis unwritable andsudowants a password: not installed.
When the plugin cannot install ttyd, it says so and the agent comes up without its web
terminal; everything else about the agent is unaffected. The check costs a few milliseconds,
so an agent on a host that will never be installable does not pay for a download on every
mngr create.
Clipboard support
Released ttyd (1.7.7) ships a web client whose bundled xterm.js has no OSC 52
handler, so copying text inside a tmux session running in the browser terminal
never reaches the system clipboard. This plugin ships its own web client
(resources/ttyd_index.html.gz, served to the stock binary via ttyd -I) that
adds OSC 52 support, so a plain mouse-drag copy inside tmux lands on the system
clipboard while mouse on keeps wheel scroll and in-app mouse working.
The client is built from ttyd's main branch (which adds
@xterm/addon-clipboard) with a small patch so it also accepts the empty OSC 52
selection target that tmux emits. To rebuild it, run
scripts/build_patched_ttyd_client.sh (the patch lives in
scripts/ttyd_clipboard_provider.patch).
The same client also fits the terminal to its frame whenever it reconnects
(scripts/ttyd_refit_on_connect.patch). Stock ttyd drops its resize listener
while disconnected and reports the old size on reconnect, so a terminal resized
during a dropped connection would stay at its old width.
OSC 52 clipboard writes require a secure browser context (HTTPS or localhost)
and a focused tab.
Metadata
Release files for imbue-mngr-ttyd 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| imbue_mngr_ttyd-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for imbue_mngr_ttyd-0.2.1-py3-none-any.whl |
Release files / imbue_mngr_ttyd-0.2.1-py3-none-any.whl
| Download URL | imbue_mngr_ttyd-0.2.1-py3-none-any.whl |
|---|---|
| Size | 201.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05c807b48c9707ec8594f07e68dcf76e9ab166670dcbbf992fdd837ab0ab5180
|
|
BLAKE2b-256 checksum How to use checksums |
8d1ea3542cd6d3a30547cb7b04d8afb66b06f0bedb198d9a730ff0f5c96cf114
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for imbue-mngr-ttyd 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for imbue_mngr_ttyd-0.2.1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.