kyroon_pty 1.0.4

Native pseudo-terminal (PTY) for Flutter — spawn shells and processes with full ANSI, resize and job control. Backed by ConPTY/forkpty and ready to pair with xterm.

1.0.4

• Inherit the full environment by default — Pty.start now passes the whole parent environment to the child instead of a small allow-list (PATH/HOME/USER/…). On Windows the old behavior dropped SystemRoot/APPDATA/USERPROFILE/TEMP, which made Node/Bun-based CLIs (e.g. claude) fail to start silently — the terminal stayed blank even though shells worked. TERM/LANG are still defaulted when the parent doesn't set them, and anything passed via environment: still overrides. Callers that already passed Map.from(Platform.environment) (like the example) are unaffected.

1.0.3

• Fix blank Windows terminal (regression from 1.0.2) — 1.0.2 dropped the STARTF_USESTDHANDLES setup, which made the child process inherit the host's real console (or none) instead of attaching to the pseudoconsole. Shells like cmd, PowerShell and bash then produced no output and accepted no input — the terminal view stayed black. The child's inherited std handles are cleared again (verified against cmd both under flutter run and as a built app), so console programs route all I/O through the ConPTY as before.
• Proper ConPTY handle cleanup — the parent now closes its copies of the pipe ends duplicated into conhost (inputReadSide / outputWriteSide), frees the proc-thread attribute list (DeleteProcThreadAttributeList) and closes the process's thread handle. Without closing outputWriteSide the read loop never saw EOF on child exit.

1.0.2

• Windows ConPTY stdin change (superseded by 1.0.3) — stopped setting STARTF_USESTDHANDLES with NULL handles. This regressed plain shells (blank terminal) and is reverted in 1.0.3; avoid 1.0.2 on Windows.

1.0.1

Example app improvements (the plugin API in lib/ is unchanged):

• Input events — PtySession.onInput (Stream<String>) fires when input is sent to the process. Live typing is buffered and emitted once per committed line (on Enter); the command bar emits the whole command at once. Useful for activity tracking, audit logs or idle-timer resets.

  session.onInput.listen((line) => print('input: $line'));
  

• CLI idle detection — PtySession.onIdle (Stream<TerminalIdleEvent>) fires when the process stops producing output after a burst of activity — a heuristic for "the CLI (claude/codex/qwen/…) finished and is idle". Tunable via session.idleThreshold (default 1.5s) and an optional session.idleReadyPattern (a RegExp matched against recent output so a long silent task doesn't look idle until its prompt returns). A reactive session.busy drives the RUNNING/IDLE status badge.

  session.idleThreshold = const Duration(milliseconds: 1200);
  session.idleReadyPattern = RegExp(r'\$ $'); // fire only when the prompt is back
  session.onIdle.listen((e) => print('idle after ${e.busyFor.inMilliseconds}ms'));
  

• Accented input in the terminal — dead-key composition (´ ` ^ ~ ¨ + letter → á ã ê ç ü …) for typing directly into the PTY on desktop, where the IME path is unavailable on Windows.

• Ctrl+Enter / Shift+Enter — send a newline (LF) instead of submitting (CR), matching how CLIs like Claude/readline insert a line break.

• Command bar ⇄ direct-PTY toggle — switch between typing through the input bar and typing straight into the terminal.

• WebSocket host input event — PtyWebSocketServer.onInput (Stream<Uint8List>) notifies the host when a remote client sends input.

1.0.0

• First stable release of kyroon_pty.
• Native PTY implementation: forkpty on Linux/macOS/Android and ConPTY on Windows (Windows 10 1809+).
• Spawn a child process attached to a pseudo-terminal with full support for line editing, ANSI colors, cursor control, job control and resize.
• Core API: Pty.start, output stream, write, resize, kill, exitCode, pid and optional read acknowledgement (ackRead) for backpressure.
• Configurable working directory and environment variables.
• Designed to pair with xterm for a fully interactive terminal widget.
• Example app with tabbed local terminals, pluggable backends (local PTY vs. remote stream) and a batteries-included WebSocket transport + server for remote/web terminals.