# fak Issue #11425 — PTY Substrate for Interactive Prompt Detection ## Metadata | Field | Value | |---|---| | Institute | Molodetz Institute — Research & Retrieval Division | | Subject | shell-multiplexer-auto-attach | | Document type | Source Dossier | | Tier | 1 | | Source title | feat(codetools): terminal PTY substrate for shell execution with interactive prompt detection | | Source URL | https://github.com/anthony-chaudhary/fak/issues/11425 | | Source publisher / author | anthony-chaudhary/fak (GitHub 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 feature request/issue proposing a dedicated PTY substrate purpose-built for "interactive prompt detection" as its own named engineering problem within a coding-tools project — direct evidence that another project independently identified this as a distinct, non-trivial piece of infrastructure worth building deliberately, not a one-line check. ## Key findings - The issue frames "interactive prompt detection" as requiring its own substrate/abstraction layer, not a quick heuristic bolted onto existing shell-execution code. - This mirrors the earlier finding (from the agent's own prior work this session, building `tai_test.py`) that correctly driving/detecting interactive terminal state is substantial enough to warrant a dedicated framework rather than ad hoc code per call site. ## Pros / strengths - Independent confirmation, from a completely different project tackling an adjacent problem (AI coding tool shell execution), that this is recognized, real engineering work. ## Cons / limitations / caveats - A single open issue/feature request, not a shipped, documented solution — there is no implementation to inspect here, only the problem statement. ## Relevance to tai Validates treating the detection logic in this proposal as a first-class, carefully-designed component (with its own tests and an explicit bypass, per the santini dossier) rather than a quick inline shell snippet in `.bashrc` — the same seriousness this project already applied to `tai_test.py`'s pty handling should apply here too. ## Changelog | Date | Change | |---|---| | 2026-10-09 | Initial dossier created. |