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	ab0c1434c4	One approval for app and agent; /api/v2 files and show; app_api 2 ... - The app's device login asks for `app models` and, where discovery says login.device.agent_scope, `agent_scope=models memory link` in the same approval. The agent's token goes to the bundled CLI on stdin (`lembas login --token-stdin --server <url> --json`) and is never kept here; if the CLI does not take it, it is given up on the server. A computer linked already keeps its link; a server without agent_scope gets the old two steps. - The server pane reads GET /api/v2/files and /files/content (mounts open like folders; `withheld` shown in the server's words). The "not offered yet" state is gone. - A show card's file comes from GET /api/v2/chats/{chat}/show?node=&version= or ?shown= as plain text (new `api_text` command, 1 MB cap); args.path is read only for agent chats on this computer, locally. - The gate is link protocol 3 plus app_api 2 (APP_API = 2), not the server's version number, which says 1.7.2 on dev until its first beta. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-03 14:48:00 +00:00
HomerandClaude Opus 5.5	4b4e63f622	The app's own interface: agent chats first, two explorers, a viewer ... Plain HTML, CSS and ES modules in ui/, no build step. The sidebar opens on agent chats (this computer first), with chats on the server as the second tab; the transcript draws the /api/v2 steps, follows a reply as it is written, answers cards, and starts agent chats in one of the agent's folders. Two explorers kept apart (this computer's, the server's) and a viewer: Markdown drawn by a safe renderer that never parses HTML, code in read-only CodeMirror with the server's token colours, HTML in the sealed frame, show calls opened in it. Settings for the sign-in, the agent and its folders, notifications and updates; no admin pages. Layout on fixed and shared tracks; the sidebar is a drawer below 48rem, the viewer goes over the chat below 64rem. All 124 sentences in the server's nine languages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-28 04:55:03 +00:00