Alelyon app 0.11.0
- Developer console: a Projects tab, when the service offers it. It lists your projects by what needs a look and what is coming due, and a project's page holds its web addresses with their domain, certificate, DNS records and visits. Every row offers what you can do about it there: open the vendor's page, ask the agent, make a monitor, mute it, accept a change.
- Fleet's Activity and Spend no longer leave out the sessions they could not make sense of. A response's output grows across its records and is now counted at its whole, so tokens read higher and truer. A resumed session's copies of earlier responses count once, a session moving among its repository's folders stays in, and a fork shows under its own id.
- Fleet's Spend and Activity have a time range: an hour to 90 days, with the same length of time before beside it. Spend's figures, sessions, models and tools all follow it, read from whole transcripts rather than the last turns of the newest sessions, and removed worktrees still count. Reading a long range takes a little while, and nothing leaves this computer.
- Everything a chat can do is on one thin rail over its conversation. It folds to a small tab and opens when the pointer reaches it. What the chat embeds is one row that slides where it does not fit; who answers, the mode and what it has used stay put at its end.
- A press on another menu moves there at once, with no press out of the first.
- A chat works in one of five modes: Manual, Accept edits, Auto, Plan and Bypass permissions, for Lattice's own models and for Claude Code and Codex alike. Each is the chat's own, and a new chat starts on the one in use, short of Bypass, which asks first and ends with the app.
- Usage shows how full the chat's context is, its tokens, its cost and your plan's limits, as far as its agent has said.
- Atlas's dock is an array you arrange: drag a tab to any edge of a pane (top and bottom too) for a pane of its own there, or into its middle; drag a pane by its head to move it; drag the border between two panes to resize them. The dock holds sixteen panes, so the Merge train, the Topic map and more can stay on show together, and the arrangement, with the tabs waiting in the bar, comes back when the app restarts.
- The chat is no longer a column on the right: a chat is a tab that sits where you put it, and closing it leaves no chat behind. Up to ten chats can be on show, each a task thread's own, live at once, with its own conversation, box, draft, model and mode. Press + on a chat or in the tab bar for another: the chats in that area even out into a grid, and one you drag to an edge stays where you let it go. A press in a chat gives it the keyboard.
- Drag a task thread from the list into the dock to put its chat there. Pressing a thread already on show takes you to its chat, and a message or topic that belongs to a thread on show goes to that thread's chat, so a thread never has two chats.
- Several of the app's pages can be on show at once, each in its own pane, and an agent that arranges your dock can place a pane at an edge of another.
- A chat's head no longer counts its own conversation as a session: "0 of 1 session done" is gone from a plain chat, and the count shows once a thread has sessions of its own.
- More than three agent turns can now run at once: the fixed limit of three is gone, so ten chats and their tasks can work together. Tasks at once still follow your setting and your plan.
- Agents read what the pages' charts say: a dashboard tile's series says when each value began, the Merge train, Pipelines and Merge requests tiles carry the window on show with each step's time, and Home's read says what waits on you beyond the sessions, in the words Needs you says it. Only your press answers any of it.
- Home, Model use: figures now run over time. Choose a window (an hour, a day, a week, 30 or 90 days, kept for next time) and it shows the answers in each step by how they ended, the tokens their providers reported, and how the window stands against the same length of time before. Under the pointer a chart says that step's figures. When the turns read do not reach all the way back, the stretch they do not reach is shaded and said to have no record, never drawn as none. Agents read the same figures, each step with its time. The chart and the windows are the developer console's own, now shared, so a window reads the same on every page that gains one.
- Home gains Over time: how many sessions were at work and waiting on you, and the graphics card's memory in use, over the window chosen, with the window before dashed beside them. The Merge train adds how many waited in line, and Merge requests how many stood open. These are read once a minute while the app or its host runs and kept on this computer, a minute at a time for 7 days and then hourly for 90; where neither ran, the line breaks.
- Merge train and Pipelines: both gain a window of time, kept for next time. The merge train's figures follow it, and two charts show what the train did in each step (landed, flaked and went on, sent back) with the stretches main stood broken shaded, and how long what landed spent in line. Pipelines shows how many ran in each step by how they ended, how long their checks ran, and how the window stands against the same length of time before, from the relay's receipts or the host's workflow runs.
- Delivery, Merge requests: a merge request a host holds now opens as that host's page for it, with the person's own presses on all of it. It says whether it can merge and what holds it, and offers Merge (squash, merge commit or rebase, at the head that was read), Merge once it can, Bring it up to date, Mark it ready or Make it a draft, and Close or Reopen; a box to comment, approve or ask for changes; what it says of itself; its reviewers, assignees and labels, each added or taken off here; its files and commits, each opening its changes from the host, whether or not its branch is on this computer; and what people said of it. The agent can be asked to review it or to make the changes a reviewer asked for, typed and not sent. Merging and closing are pressed twice, and a repository on the merge train lands through the train alone, so nothing here merges there. The list narrows to words in a title, branch, author or number.
- Home gains Monitors: a figure, a line, and how long it must stay at or over it. Three are on from the start: main failing its checks, the merge train stuck for 30 minutes, and a session waiting on you for 30 minutes. One that fires comes to Needs you with what it is about a press away, as a notice while you are in another window, and to your phone if that is on. Each keeps its history and can be muted. They run only while the app or its host runs.
- The side bar's work is one tree: each project, its task threads and each thread's sessions, in place of three lists that repeated one another. A row is one line; what can be done with it is under its dots, or a right press. What needs you comes first in each project, then what is at work, then the rest by last use, and a thread quiet for a week folds away. One box finds across the whole tree. New chats and threads start from a project's +, and sessions in other apps that wait on you are at the tree's foot, each with one Bring in.
- A quieter rail: Work, Files, Search and Changes, then the places. Lists, Tools, the debugger and the file's structure sit behind a ... button, and show on the rail while one is in use or has something to say.
- A session comes into Alelyon once: pressing Bring into Alelyon again opens the chat it already is, with nothing asked or copied. Its row on the board moves under "In Alelyon" with a press to open that chat, and while it is on its way the row says so. The copy made for a chat is no longer listed as another session waiting on you, on the board or on Home.
- A session continued from an earlier one is titled by what you said in it, not by the summary it began with.
- Delivery, Pipelines: the host's workflow runs are listed beside each pull request's checks, so a push to the main line shows too, and they narrow by how they stand and by words. A run opens with its own jobs. A job the host ran reads what it wrote in the app, whichever way it ended, and from there a person can run a failed job again, run what failed again, run it all again, or stop it. Each job has a history over the pipelines read: a mark for each time, how often it failed, how long it usually takes, and the newest pipeline it failed in, a press away. While something on the host runs and the page shows it, the page reads it again every 30 seconds.
- Projects: Give agents their own folder makes a second checkout beside a project's repository, named <repository>-agents, and new chats in the project open there. Your own folder stays among the project's folders.
- Agents in a checkout they share can land their work: git_land commits an agent's own files on a new local branch off the latest default branch, after you allow it, without moving the checkout. Other agents' files stay behind, nothing runs from the repository, and nothing is pushed until you allow that too.
- Agent runs and traces go deep. A time range with the runs by how they ended, their tokens and how long they took; search and filters by state, agent and model; Run again; and a press on any step of a trace shows what went into it and came out, each a press from the clipboard. Steps fold, and the whole trace copies as JSON. Agents read the same window and the open trace.
- A task thread's chat is now its conversation: your messages and the agent's replies, with what its sessions did among them and what waits for you at its foot. It used to show only the thread's events. Its head says how far the thread has come and names each session under it, a press away from its page.