3 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5.5	ac0d4ce623	Terminal: a shell on the agent chat's computer, before the first message too ... The Terminal panel opens a shell on the device an agent chat works on, in its folder: for a new agent chat as soon as the device and folder are chosen (the server's /api/v2/devices/{device}/terminal/ws?directory=, which the chat's first message takes over -- the same socket carries on), and for an open agent chat from the header (/api/v2/chats/{chat}/terminal/ws, the web page's shell). Offered where GET /devices says the device opens a terminal. The socket is Rust's (src-tauri/src/terminal.rs, tungstenite on the rustls ureq already brings): the bearer token goes in the handshake and never reaches the page, which gets the frames as `terminal` events and sends keys, sizes and close through commands. 4401 signs the app out as a 401 does. xterm and its fit addon are the server's vendored build, pinned through fetch-vendor.sh like CodeMirror and loaded on the first open. Send to chat puts the selection, the last marked command and its output, or the screen into the composer, never sent. The terminal and the activity panel take turns in the panel column. Continue in a terminal stays in the chat's menu. tests/ui: seven B3 cases with a mocked socket, at 1280 and 390 px. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 09:06:01 +00:00
HomerandClaude Opus 5.5	ec32bca644	Subagents: a new chat reads /models again, so subagents switched on later show ... The Subagents chip on a new chat follows `/models` -> model.subagents.offered, the same team_run.offered the web page renders from. The app read /models once, at sign-in, and kept it while it stayed open in the tray: subagents switched on afterwards (or a model added) never reached a new chat until a restart. startNew() now re-reads it (at most every 5 s, keeping the last list if the read fails) and redraws the draft's chips (modelsChanged()). An open chat already re-reads its own `subagents` with GET /chats/{id}. tests/ui: A5 cases -- parallel model offered: chip, slider to the server's cap, no note; one-request model offered named_only: the `own` note; offered false everywhere: no chip; switched on while open: the next new chat has it; an open chat follows its `subagents`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 08:17:30 +00:00
HomerandClaude Opus 5.5	5a87eec28d	Approval cards show again: the buttons no longer throw, the command is the item's detail ... An agent chat's bash approval left "Waiting for you to allow bash…" with no card: cardOf() called append(actions, a, b, c) while append() took one array, so `children.flat` threw for every approval and plan card (questions used el.append and worked). renderCards() had already unhidden #cards, which stayed empty. append() now takes children as rest arguments too. - The editable command is `detail` (services/device_link.py puts the fixed "Run a command" in the title); it is sent back as the item's text only when changed. Non-editable approvals show the title and the device's input. `purpose` ("It says: …"), `reason` and the asking subagent (`job`) are shown, as on the web page. - renderCards() keeps a card already on the screen (by id) instead of drawing every card again on each `ask` frame, which the server re-sends whenever the countdown changes; a card that cannot be drawn shows the error instead of an empty box. - tests/ui/: headless harness with a mocked Tauri bridge; five A1 cases (device bash card shows and is visible, Allow/edit/Deny post to /chats/{id}/interactions/{card}, redraw keeps edits, reopen gets the card from the stream's first pass, 390 px). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 08:13:02 +00:00