Befehle in Studio
Umfang der Befehlsausführung und interaktive Alternative.
Technical reference synchronized with Yard’s source. File names and development commands refer to the native app repository.
Keep the current command-runner contract for this release. Interactive shells, REPL input and full-screen programs need a separate PTY feature; calling the existing panel a terminal does not supply those capabilities. No PTY dependency, input endpoint or terminal rewrite was added.
Herd documents a project-directory command terminal, but does not specify a PTY, editable stdin, resize protocol or persistence after application exit. Herd.app is not installed on this validation machine, so every competitor scenario below is unverified, rather than inferred from its name. Herd Studio tools.
Reproducible behavior matrix
The fixture uses StreamHub.run, temporary directories and a private StudioAdmission gate.
ZDOTDIR points to the empty fixture so test commands do not load the user's shell startup files.
No shared services, remote repository or model is involved.
| Scenario | Yard behavior / evidence | Workflow consequence | Herd runtime |
|---|---|---|---|
| Interactive prompt | A shell read immediately reports EOF (read=1, empty answer); test -t 0 is false. StudioTerminalAssessmentTests.testPromptREPLAndResizeExposeClosedInputAndNoTTY. |
Commands must accept flags/noninteractive input. Password and confirmation prompts cannot be answered here. | Unverified |
| REPL | /usr/bin/python3 -q exits cleanly with closed stdin; it does not remain an interactive session. Same test. |
Use the existing external Terminal action for REPLs. | Unverified |
| Long-lived command | First output appears before a delayed second output; both remain replayable and the same stream object is retained. testLongLivedOutputCanReconnectWithoutStartingAnotherProcess. |
Dev/watch output fits the command runner. | Unverified |
| Resize | stty size reports failure because no TTY exists. There is no frontend/backend rows/columns route. Executed fixture plus route inspection. |
Full-screen terminal programs cannot lay out against the panel. | Unverified |
| Cancel | A real owned parent and grandchild ignoring TERM are killed with escalation; independent sentinel remains alive. StudioLifecycleTests.testShutdownKillsIgnoredTermParentAndGrandchildAndKeepsIndependentSentinel. |
Cancel and Studio disable own the whole captured process group. | Unverified |
| Reconnect | Buffered output can be read from the prior monotonic cursor without starting another process. Retention is the latest 5000 chunks; history beyond that and app restart are not durable terminal sessions. Reconnect fixture and testStreamReconnectCursorContinuesAfterBoundedHistoryIsTrimmed. |
Reconnect within the open Yard session works; retained-tail limits are explicit. | Unverified |
The assessment exposed the pre-existing fixed-cursor bug after 5000 chunks. HD006's stream lifecycle changes include a small monotonic-cursor fix and a regression; this does not change stdin or add a PTY.
The native project's Terminal action already opens the user's preferred external terminal in the
project directory (Opener.terminal). It is sufficient for an occasional interactive workflow today;
it does not preserve that interactive session inside Studio. No external terminal was opened during
this assessment.
Bounded follow-up option
If users require interaction inside Studio, a separately selectable PTY task should include:
- A Swift-owned
openpty/spawn wrapper with a controlling terminal, verified process group, pinned project runtime environment, loopback-only ownership and the same bounded shutdown semantics. - A terminal renderer such as xterm.js, pinned with SHA-256, provenance and third-party license notices. Its upstream license is MIT; no package is installed by this assessment. xterm.js license.
- A bidirectional input/resize protocol with existing Host/Origin checks, a per-session capability, task handoff lease checks on creation and writes, bounded scrollback and no transcript/secret logging by default. Decide disconnect grace, explicit close and application-exit behavior.
- Tests for control keys, paste, password prompts, REPL, resize, duplicate attachment, reconnect, lease transfer and hostile/closed origins, plus native/web accessibility and keyboard handling.
This is a medium-sized cross-layer feature (process plumbing, authenticated transport, renderer, ownership and UI), not a label or textarea change. An initial disposable prototype should measure memory, scrollback growth and cancellation before production scope is chosen. No parity or effort estimate is derived from untested competitor behavior.
Executed validation
Both terminal assessment tests and the buffer-retention regression passed in
/tmp/yard-hd005-018-final-tests.log (2026-11-08). The ignored-TERM subprocess fixture passed in
the same run. No terminal assessment case was skipped; interactive Herd comparison remains unverified.