From 35be5bd1d82f6420f8199893da6945d6b5b52fec Mon Sep 17 00:00:00 2001 From: jester Date: Sat, 14 Mar 2026 22:30:13 +0000 Subject: [PATCH] =?UTF-8?q?Remove=20misplaced=20file=20=E2=80=94=20belongs?= =?UTF-8?q?=20in=20knowledge-base=20not=20zlh-grind?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Frontend/TerminalView_Component.md | 46 ------------------------------ 1 file changed, 46 deletions(-) delete mode 100644 Frontend/TerminalView_Component.md diff --git a/Frontend/TerminalView_Component.md b/Frontend/TerminalView_Component.md deleted file mode 100644 index c6ad515..0000000 --- a/Frontend/TerminalView_Component.md +++ /dev/null @@ -1,46 +0,0 @@ -# TerminalView Component - -> Status: ✅ Operational - ---- - -## Overview - -The terminal console is implemented using: - -- **xterm.js** — frontend terminal renderer -- **WebSocket transport** — connects portal to agent -- **PTY session** — managed by the agent via `creack/pty` - -`TerminalView` owns the WebSocket lifecycle. `ServerConsole` owns policy and session gating. - -The file panel does not interrupt the console lifecycle. - ---- - -## Reconnect Behavior - -The terminal automatically reconnects when the WebSocket closes unexpectedly. - -Behavior: - -- Reconnect delay: 1–5 seconds -- Backoff capped at 5 seconds -- Console session recreated automatically - -The user no longer needs to refresh the page to regain console access after navigating away from the console tab or after a transient disconnect. - ---- - -## Agent Side - -- One PTY read loop per `{vmid, container_type}` -- PTY-backed WebSocket served at `/console/ws` -- Commands sent via `GET /console/command?cmd=` to server stdin - ---- - -## Constraints - -- Portal never calls the agent directly — all traffic through API -- Console does not enforce real policy — agent enforces