Expand description
The terminal’s wire shapes: what a client draws, what a hand-off parks, and what the agent’s tools answer.
The bytes are not here. Terminal output crosses as its own binary
frame kinds (TERMINAL_OUTPUT_TAG and TERMINAL_INPUT_TAG); these
types are the JSON around it - the strip’s row, the attach snapshot, the
parked ask and the state a tool reads.
Re-exports§
use serde::Deserialize;🔒use serde::Deserialize;🔒use serde::Serialize;🔒use serde::Serialize;🔒use crate::SessionSlot;🔒
Structs§
- Terminal
Exit - A command’s exit.
- Terminal
Hand Off - A terminal hand-off: a session asking the person at a client to type into the seat’s terminal before it can carry on.
- Terminal
Input Expected - One input the terminal is waiting for, with the evidence behind it.
- Terminal
State - What the terminal is doing, as the agent reads it.
- Terminal
Summary - One terminal as the strip draws it.
Enums§
- Terminal
Input Kind - What kind of input the terminal is waiting for.
- Terminal
Source - Where a state answer came from.
Constants§
- MAX_
COLS - The most columns and rows a resize may name.
- MAX_
ROWS - MIN_
COLS - MIN_
ROWS - TERMINAL_
INPUT_ TAG - The binary kind a client’s terminal input crosses as:
id u16, raw bytes. - TERMINAL_
OUTPUT_ TAG - The binary kind a terminal’s output crosses as:
id u16,seq u32, raw bytes.
Type Aliases§
- Terminal
Hand OffAnswer - One answer to a parked terminal hand-off: the ending, the door that sent it and the connection that carried it.