Files

T

retoorandClaude Sonnet 5 9dbd1fe667 Add plexer subsystem, container test infra, and last-resort opencode box backend

- Plexer: always-active terminal multiplexing. NativePlexerController/
  TmuxPlexerController share one interface, chosen by which env var is
  already set (TAI_PLEXER_SOCKET vs TMUX_PANE); NativePlexerBackend is
  the pty.fork()-based wrapper (raw mode, SIGWINCH resize forwarding,
  a Unix-socket control protocol, continuous session logging, a
  Ctrl+A prefix key distinct from tmux's own Ctrl+B). Auto-wraps new
  interactive shells via a .bashrc hook mirroring the existing
  command-not-found install pattern, gated on $TMUX/$TAI_PLEXER_ACTIVE/
  a $HOME/.tai-no-plexer bypass. New plexer_send/read/type/status
  tools, env-gated on a detected controller.
- tests/container.py + docker-compose.yml + tests/docker/Dockerfile:
  a disposable podman/docker image for the tests that must never touch
  a real machine (installing the plexer hook into a real ~/.bashrc, a
  live tmux session). Required suite (test_seal.py, test_tai.py,
  tests/plexer.py, tests/bashrc.py) gates the result; tests/rag.py
  runs as best-effort since its real-LLM dependency can't be satisfied
  inside a disposable container with no nested engine.
- tests/bashrc.py: real end-to-end hook install + bash -i auto-wrap,
  anti-recursion, tmux-active skip, non-interactive skip, a live
  TmuxPlexerController test, and an install/uninstall round-trip.
- tests/plexer.py: NativePlexerBackend under a real pty, plus a
  dedicated robustness pass (file permissions, >64KB payload framing,
  a malformed control request, a genuine self-deadlock fix in the
  write-to-child path).
- tai_test.py: the shared async process-driving framework (pipe/pty
  transport, group-wide kill-and-reap, a StdinBridge for --interactive)
  both test files build on.
- ChatClient last-resort backend: when there's no local opencode CLI
  but the sandbox box is already running, install opencode into it
  (official Node tarball, not apt -- apt's nodejs/npm pull in
  webpack/babel/jest as transitive deps) and route through it instead
  of giving up. Only reachable after the first retry round already
  failed everything else; never creates the box itself. TmuxPlexerController.status()
  fixed to use `list-panes` instead of `display-message -p`, which
  silently fell back to the default pane instead of erroring against
  a dead target.
- Fix 4 pre-existing test_tai.py bugs surfaced by running it in a
  clean environment for the first time: two stale mock signatures
  (subprocess.run's stdout= kwarg, Chat.complete's deadline= kwarg),
  one $TMUX-dependent catalog assertion, one tty-dependent color
  assertion.
- research/: a sourced research archive (Source Dossier/Citation
  Card/Conclusion tiers) backing the above design decisions, with its
  own audit.py consistency checker.
- .gitignore: fix a blanket *.md rule that was about to silently drop
  the entire research/ archive from version control; add __pycache__/
  and the one-off debug transcript this session started from.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-10-10 04:36:05 +02:00

2.3 KiB

Raw Blame History

Remote TTY with Terminal Resize (StalkR/misc/pty, Go)

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	shell-multiplexer-auto-attach
Document type	Source Dossier
Tier	1
Source title	Remote TTY with terminal resize (Linux)
Source URL	https://beta.pkg.go.dev/github.com/StalkR/misc/pty
Source publisher / author	StalkR (GitHub, misc repository)
Source type	repository
Source date (published)	Unknown — not stated
Date researched	2026-10-09
Researched by	tai (agent), model: Claude Sonnet 5, on behalf of retoor
Research method	web search synthesis
Confidence	Medium
Status	Active

Summary

A Go package design for a remote pty with working resize support: on SIGWINCH, read the new size via the TIOCGWINSZ ioctl, forward it over a control channel to the remote side, which applies it to its own pty master via TIOCSWINSZ.

Key findings

The ioctl pair (TIOCGWINSZ read locally, TIOCSWINSZ set remotely) is the standard mechanism for propagating terminal size across a process boundary (local terminal to a remote/forwarded pty).
A control channel, separate from the raw data stream, is needed to carry resize (and other non-data) events — the write-up notes this explicitly as a multiplexing requirement on the socket design.

Pros / strengths

Names the exact two ioctls needed and the data flow between them, which is precise, directly implementable guidance rather than a vague description.

Cons / limitations / caveats

A documentation page for a Go package, not Python — the ioctl calls (fcntl.ioctl in Python, per the search synthesis's own sketch) are the same underlying kernel interface, but the surrounding code shape differs by language.

Relevance to tai

If a tai layer ever forwards resize events itself (rather than letting tmux handle resize natively, which it already does), this is the exact mechanism: signal.SIGWINCH handler -> fcntl.ioctl(fd, termios.TIOCGWINSZ, ...) to read -> send over the control socket -> TIOCSWINSZ on the far end. Using tmux (which already does all of this internally) avoids needing to implement it at all.

Changelog

Date	Change
2026-10-09	Initial dossier created.

2.3 KiB Raw Blame History