ptywright

A cross-platform Rust CLI and library for driving interactive terminal applications through PTYs.

ptywright is an early general-purpose PTY/TUI automation toolkit. It is designed to drive interactive terminal applications from code without coupling the core abstractions to any one program. A generic Extension trait sits above the PTY/session/screen/action/matcher primitives, with Claude Code shipped as the first plugin under that trait.

The library now includes initial target, session, rich screen snapshot, action, temporal matcher, bounded transcripts with optional raw file streaming, redaction, JSON-RPC, the generic Extension layer, a Lua-backed interactive Claude Code adapter with stable-screen turn evidence, plugin manifest/runtime primitives, and shell completion primitives backed by real PTYs. The CLI includes run for live stdin/stdout PTY debugging, serve --stdio for NDJSON or LSP-style JSON-RPC automation, multi-client local IPC via Unix sockets on macOS/Linux and named pipes on Windows, and completions for shell setup.

Docs: https://utensils.io/ptywright/

Quickstart

ptywright --help
ptywright --version
ptywright run -- /bin/sh -lc 'printf ready'
printf '{"jsonrpc":"2.0","id":1,"method":"server.capabilities"}\n' | ptywright serve --stdio
printf '{"jsonrpc":"2.0","id":1,"method":"adapter.list"}\n' | ptywright serve --stdio | jq '.result.plugins[].name'
printf '{"jsonrpc":"2.0","id":1,"method":"adapter.start","params":{"plugin":"claude-code","program":"/bin/sh","args":["-lc","cat"]}}\n' | ptywright serve --stdio | jq '.result | {adapter, plugin}'
ptywright serve --stdio --framing lsp
ptywright serve --socket /tmp/ptywright.sock
source <(ptywright completions zsh)

Install from source

The default build embeds Lua 5.4 for trusted adapter plugins, so source builds need a working C compiler in addition to Rust. The Nix dev shell provides the expected toolchain on macOS/Linux.

git clone https://github.com/utensils/ptywright
cd ptywright
nix develop
cargo build --release
./target/release/ptywright --help

Or run through Nix on macOS/Linux:

nix run github:utensils/ptywright -- --help

Project goals

• Provide Rust abstractions for spawning, attaching to, and driving PTY-backed terminal applications.
• Keep application-specific adapters separate from the core architecture.
• Support deterministic turn execution, transcript capture, prompt detection, and output parsing.
• Target macOS, Linux, and Windows.
• Keep a clean CLI surface while exposing reusable library primitives.
• Preserve a small, auditable, local-first implementation.

Current layers

1. Target configuration.
2. PTY session lifecycle.
3. Terminal screen observation.
4. Input actions and key sequences.
5. Matchers and waits.
6. Bounded transcript capture with explicit raw transcript file streaming opt-in.
7. JSON-RPC over stdio or multi-client local IPC for external automation clients, with NDJSON and LSP-style framing.
8. Generic Extension trait with ExtensionHandle host loop; Claude Code ships as the first plugin under that trait, driven through the adapter.* JSON-RPC surface.
9. Plugin manifests, permission declarations, and trusted embedded Lua runtime for adapter orchestration. Trusted-local third-party plugins load via the ptywright serve --plugin <manifest.toml> CLI flag or the plugin.load JSON-RPC method (gated by --allow-plugin-load).
10. Per-method permission gating at the JSON-RPC dispatcher — every adapter.* method consults the bound plugin manifest's declared permissions and rejects calls with -32004 PermissionDenied carrying structured data.
11. Per-user runtime directory under ~/.ptywright/ with structured logging (daily rotation, redaction-aware writers).
12. Interactive REPL client (ptywright repl, default-on repl Cargo feature) with reedline-based DSL, tmux-style attach, and inline notification rendering.
13. Shell completion generation for bash, zsh, fish, elvish, and PowerShell.
14. Rich screen snapshots with cell/style/mode metadata.
15. Redaction helpers with built-in and caller-supplied patterns plus default RPC redaction for sensitive-looking output.

Planned layers

1. More Claude Code real-world fixtures and transition tests as upstream Claude Code UI changes.
2. A second built-in adapter (Codex / shell) to validate the plugin model against a non-Claude TUI.
3. Optional WASM only if untrusted marketplace-style plugins become a concrete priority.

Development

nix develop        # auto via direnv + use_flake
ci-local           # fmt-check → check → clippy → test → build
docs-dev           # run the VitePress docs site

Useful direct commands:

cargo fmt --all -- --check
cargo check --locked
cargo clippy --locked -- -D warnings
cargo test --locked --features _test-fixtures
cargo run -- --help

Runtime directory and logging

ptywright keeps configuration and rotated log files under ~/.ptywright/ (override with PTYWRIGHT_HOME=/some/path). Logs are written through tracing with daily rotation, 14-day retention by default, and built-in redaction of secret-shaped values. Override the filter at runtime with PTYWRIGHT_LOG:

PTYWRIGHT_LOG="info,ptywright::rpc=debug" ptywright serve --stdio

See config.example.toml for the full set of tunables and the Runtime directory docs for layout details. ptywright run writes only to file (it owns your terminal); serve --stdio and serve --socket write to file and stderr while keeping stdout reserved for JSON-RPC framing.

See AGENTS.md for repository guidance.

License

MIT — see LICENSE.