Alelyon app 0.15.0
- The chat's controls are where other coding agents' apps put them: one row inside the message box. At its start, + (attach a picture, mention a file, start a command or a skill, and the agent's tools, its browser and the Tools page), the mode, and where the chat works (its project and folder, with Trust for a folder not yet trusted); at its end, the model, a small ring showing how full the context is (press it for the chat's tokens, cost and your plan's limits), Dictate, Stop and Send.
- The rest of what a chat does is in a ⋯ menu on its head: a new chat, fork, copy or write again the latest answer, export, archive; its thread's sessions, next question and record, and a new thread; compacting the context; and the views (editor, grid, board, all chats, jump, explorer, changes, terminal).
- Each menu opens from its own button, over the box or under the head, and a press on another button moves straight to that one.
- The rail over the chat and its Tools tab are gone, with what opened it (Ctrl+Space, holding Alt, and Q and E to slide it), so Ctrl+Space now only opens the code editor's completion list. A tool is kept in the title bar by right-clicking it in a menu.
- Infrastructure: building and shipping in the app. Build an image from the Dockerfile open in the editor; pull an image by name, after the app shows the registry and how much it downloads; tag an image and push it, naming the registry it publishes to; run the Compose file open in the editor as a stack. Each build, pull, push and run shows its output as it comes and keeps going when you leave the page, with Stop. A build or a Compose run asks first only when it would download an image this computer lacks, and names it. The Registries tab lists the registries docker is signed in to and where it keeps each sign-in; signing in happens in docker's own prompt in the terminal panel (Docker Hub's in your browser), so the app never sees a password. Helm: the releases on a cluster with their history, rollback, uninstall, and a chart installed or upgraded after its difference from the cluster is shown. Each running container's processor, memory and restarts are kept over time, drawn on its page, and Home's monitors can watch them, one container at a time.