Alelyon app 0.10.0, the patch notes.

Alelyon app 0.10.0 31 October 2026

• Developer console: a chart of latency now draws its axis lines on figures it can write exactly, so with very fast calls a line at 2.5 ms no longer reads 3 ms.
• Developer console: a chart of calls now draws its axis lines on whole numbers and writes each as it stands, so with few calls a line at 0.5 or 2.5 no longer reads 1 or 3.
• A part of the service that is off or full now says so in its own words, instead of saying Alelyon is down for maintenance: a CRM that is not switched on, or photos that cannot be uploaded right now.
• Ask the agent takes what you are looking at into the chat of the project you are in. It arrives typed in the chat's box and is not sent, so you add what you want done first. Back returns you to where you were. It is on:
• Your agents can arrange the dock beside the chat in Atlas as you would: they see its panes and tabs, open a page or a task thread in the pane they name or side by side in a pane of its own, and close a pane (its tab stays open). An agent outside the app asks you first each time.
• Your agents (the one in Atlas's chat, and one outside the app through the agent bridge) can see your task threads and their sessions, which work and what each waits on you for, and open a thread beside the chat. Asking you first each time, they can stop a session or answer what it asks: they quote what they answer word for word, and act only on your own sessions and threads.
• Drag a tab from the tab bar to the dock: let go on a pane's left or right edge and it opens there in a pane of its own, or in a pane's middle to open it in that pane. The places it can go light up as you drag, and Esc leaves it where it was.
• In Atlas's topic map, a topic you pick can be stopped while it works, an approval it waits on approved or refused, and its task thread opened beside the chat, from its details. Another person's topic offers none of these.
• In Atlas's task threads a session at work can be stopped from its row, and an approval it waits on is approved or refused there, without opening it. These actions, and opening a thread beside the chat, are done the same way as Home's answers, and only on your own sessions and task threads.
• In Atlas, Side by side at the head of the task threads opens every thread at work or waiting on you in one press, each in a pane of its own beside the chat (up to four, those waiting first).
• Fleet's Waiting on you brings a Claude Code session into Alelyon's chat from its row. Bring into Alelyon forks it, leaving the session as it was in Claude Code: its messages become a chat of its own, in a task thread of its own and in the project whose folder it worked in, and the agent goes on from where it stopped. A session at rest can be moved in instead, once you confirm: the session itself then goes on in Alelyon. Its folder is attached first, through Lattice's own confirmation, and the chat says where the session came from.
• A change's card on the Merge train page now holds the rest of what can be done with it:
• In the train's line, a branch opens its card, a session its chat or Fleet's inspector, and a pull request its page. The line in the task threads' panel opens the card too.
• On a merge request, its branch, the session that opened it and its relay rank are links.
• A conflict's current side now says when it is main with the changes ahead of it in its batch merged, whose lines may not be on main yet. A conflict whose change went back to its session says its session holds it; picks still work.
• A change in the merge train's line has one place on the Merge train page. Pick it on the railway, or open it from Fleet, Home or a chat, and its card shows:
• A chat's stage line acts. The stages the chat has passed, the one it is at, and its next step can be pressed:
• Chat: answers are easier to take in at a glance. A section is coloured by what it is: the outcome in the theme's main colour, evidence and checks in green, risks and gaps in amber, failures in red, next steps and decisions in the colour the theme gives the model, with a bar down its left side. GitHub call-outs (`> [!NOTE]`, `[!TIP]`, `[!IMPORTANT]`, `[!WARNING]`, `[!CAUTION]`) show as coloured cards. Code is coloured as the editor colours it, and a diff shows what it adds and removes. Verdict words in bold or code (passed, failed, UNMEASURED), and table cells holding only one, take their colour, and task lists show ticks.
• alelyon-cli mcp --http <port>: the MCP server over Streamable HTTP on this computer only, for programs written with any lab's agent SDK; each request needs the key written to a file at start.
• alelyon-cli mcp install, check and rules: register the MCP server with every AI tool on the computer, whichever lab's models it runs (Claude Code, Codex, Gemini CLI, VS Code, Cursor, Windsurf, Claude Desktop), check each lists it, and give a project's agents the working-together rule. Nothing changes without --yes.
• Opening a module from the Topic map's Code view now keeps your place, so Back returns you to the map.
• On the Merge train's conflicts, a side cut at 4 KB opens whole at a press: main's file as main had it, or the change's as its head has it, read-only in the editor at the hunk's line. The note under it no longer names a command that printed the same cut text.
• Developer console: Kept copies of your setup: keep your boards, objectives, dashboards, monitors and endpoint checks as they stand until you delete them, and roll back to a copy, with what stood then saved first so that you can undo it. Shown once the service offers them, in your own console.
• Console: a Service health part, for the people who run Alelyon's service and nobody else: its newest backups, its disk and memory, its slowest routes, and what wants a look first.
• On the Data page, a row opened whole opens what it records: a relay proposal its change on the Merge train and its receipt, a receipt its checks, and a bus post its session (and the session it was for) on Fleet's Session inspector, found by its whole id or the start of one.
• The chat's box takes dictation. While the speech engine is connected, Dictate sits beside Send. It puts what you say at the end of the box, for you to read and send yourself; nothing is sent for you. Press it again to stop.
• Dictation goes to one place at a time. Starting it in the chat moves it there from Sinai's box or the Words page.
• A draft comes back to its Marketing piece with one press. After you ask Lattice for drafts and send the request, the chat's newest finished answer offers "Put this in" with the piece's name, for example "the LinkedIn post for Fernhill". Pressing it puts the answer in the piece and shows it on the Marketing page, with Back to the chat.
• Ask for something shorter and the shorter answer is the one offered: the press follows the newest finished answer in that chat.
• Merge train, Flaky tests: a test's link now opens its file at the test, not at the top of the file. Where the file no longer has that test, it opens at the top.
• Fleet's Waiting on you now lists first the sessions this app runs that wait on you, answered there as on Home: Approve or Refuse, a choice or your own words, and each title opens its chat.
• A waiting session can be stopped, on Home and on Fleet's Waiting on you, while its turn runs.
• The rail shows a count on every place that holds something for you: Pages, Marketing and Fleet now too, and Atlas counts the changes that wait for your Approve beside the sessions.
• Fleet's Waiting on you answers a session from its row: type an answer and, once you confirm the post, it goes to #fleet addressed to that session, which finds it on the bus when it next runs. Each session's row also opens its chat as its coding agent wrote it to disk, read-only in the editor.
• On Fleet, a branch's name opens what it changed since main, read-only in the editor, and a worktree's folder opens in the editor to work in; Back returns to Fleet. Plug-in pages can ask the app for both.
• Fleet's Activity, Spend, Flow, Session inspector and Contested Areas read every coding agent's sessions this computer keeps, Codex's beside Claude Code's, and each session says whose it is. Codex's sessions are read without their words, and their rows say so. Waiting on you still reads Claude Code's sessions alone, since only their turns say who is waiting.
• On Fleet's Landing tab, a change's rank opens it on the Merge train with it picked, its branch opens what it changed since main, and its session opens in the Session inspector. A receipt's id opens its checks among the receipts. Plug-in pages can ask the app for a change and a receipt too.
• Across Fleet's tabs a session's id opens it on the Session inspector, a branch its changes, and a worktree or a session's folder opens to work in; a file path, on the plan and the guard's row, opens the file. A name someone declared on the bus stays plain text.
• Fleet's page scrolls again and keeps its margins: what ran past the bottom of the window could not be reached.
• A group project a friend made, which you are in, can now be worked on here: Choose its folder on its card in Group projects. The project of yours on that folder becomes your copy of it, or the folder is brought in as a project named as the group project is, and opened. Once it has a copy here, its card opens it in Lattice. Your account keeps nothing of the copy: the group project stays the one your friend made. If the folder was a project of yours on your account, that record is taken off, since the folder is now the group project's copy. A project of yours that others are in, or the copy of another group project, is not taken.
• In a group project, Atlas's list of task threads shows yours and, under Recently active, the ones the others in it had active in the last week: whose each one is, how many sessions it holds, when it changed and whether it is at work or waiting on them. Your Alelyon shares only your threads' names and states with the others in the project, never what they say.
• Home's Needs you lists what waits on you in your CRM: your tasks overdue or due today, done there or moved on to tomorrow or a week from today, and the deals and leads that want looking at, each opening its record. The rail counts it, and each new one is told as the other things that wait on you are.
• Home's Together part is now called Group projects, and so are the projects you work on with friends wherever the app names them.
• Home's Needs you lists the Claude Code sessions outside Alelyon that wait on you, as Fleet's Waiting on you reads them: whose session it is, the folder it works in, how long it has waited and its last words. Each is brought into Alelyon's chat from there to go on in it, or moved in once it is at rest; inside a project, those working in its folders. Coming back to Home reads them again, at most every 30 seconds.
• A session a program runs through Claude Code's SDK, as Alelyon's own chat runs its sessions, is not one of them: Fleet's Waiting on you says it is run by a program and offers no way to bring it in, and Home does not list it.
• Home's Needs you lists what asks for your answer on Pages: each reply to you, mention of you and quote of your post you have not read, with who wrote it and what, and a reply box to answer it there. Its words open the post on Pages. The rail counts it, and a new one is told as the other things that wait on you are. Reading them for Home marks nothing read.
• Inlay hints: the language server's types and parameter names, drawn faint after the end of the line they belong to (the text never moves, so a click lands where it looks), read when a file opens and again once typing pauses. Ctrl+Alt+I, or the tab bar's button, turns them off and on.
• Nothing changes in the app: the terminal's idle-shell test now waits for the shell's prompt instead of a fixed two seconds, so it holds up when the machine is busy.
• The last names that were only words now open what they name: a pipeline's branch, the sessions and files in Atlas's System tab, a train's riders and a log entry's branch while the change stands in line, a conflict's file, an incoming change's rank, the organization on a service account, and Sinai's grants file.
• Ask the agent now also comes from a post's menu on Pages, a row opened whole on the Data page, a receipt checked on Trust, a failed call in the console and a flaky test on the Merge train.
• The Topic map in a narrow pane, such as a quarter of the dock: a picked topic's or folder's details sit under the map instead of beside it, and the line under the map gives its keys a line of their own under its figures, where before they were squeezed to a word a line.
• CRM: Ask the agent on a lead or a deal types its facts into Atlas's chat for your own ask; nothing is sent until you send it. A person's card can show their lead or contact in your CRM, found by the Pages page it was made from, or add them.
• The CRM has Automation: rules that add a task or a tag when a lead or a deal is added or reaches a stage, each read as a sentence, switched on or off in place, and written as a sentence of choices, with five to start with.
• The CRM has a Calendar: a month of your tasks, calls and meetings (or everyone's) by the day they are due; press one to open its record, or drag it to another day to move it.
• CRM Calendar: the line under the month says how many of its tasks, calls and meetings are left to do and how many are done, by the month's name.
• CRM Fields: add fields of your own to leads, contacts, companies and deals (a line of text, a number, a date, a choice, a yes or no, or a web address), and rename, reorder or take them away on the new Fields page. A record shows them under About, each changed where it is shown; the form, the list's columns, and CSV import and export have them too. A list sorts by any of them (press a column's name) and narrows to one value of a choice or a yes or no; a report groups by one, and its rows open the deals they count.
• The CRM is laid out as a workspace: a side bar of its places, your saved views and the records you opened lately, and a record that opens beside its list, with its details changed where they are shown. A delete can be undone, Esc closes what is open, and the keyboard walks a list.
• Home charts the months around this one (what was won, and what open deals are forecast to bring, weighed and at best) and lists a month's deals at a press. It also shows your day's tasks and the records that want looking at: a deal past its close date or untouched for two weeks, one with nothing planned, and a new lead nobody has contacted.
• On the deal board, drag a card to another stage, or onto Won or Lost; the move can be undone.
• CRM: Leads from Pages can switch on a form on your products' pages. Anyone may write to the makers from a product's page on the website, and each message comes in as a lead with a task to answer it. Automation offers a sixth rule to start with: tag a lead from a web form.
• CRM Home shows this month's goals and how far each got: what is won, how many deals, or how many activities are logged, for everyone or one person. Set them from Home.
• CRM: Kept copies, for a CRM's person or an organization's owners and admins: keep the whole CRM as it stands until you delete it, and roll back to it, with what stood then saved first so that you can undo it. Shown once the service offers it.
• CRM leads have a board of their statuses: drag a lead on as you work it, or onto Unqualified, with an undo; a lead opened beside the board converts from there.
• A CRM list's columns are yours to choose, and a row changes where it is shown: a lead's status or a deal's stage (at once, with an undo), the owner, and a deal's amount and close date.
• CRM: Products. A price book on its own page (code, price, the Pages product it is, whether it is offered), and on a deal's page the products it sells: added from the price book in one press or written in, each quantity, price and discount changed in place, the deal's amount their total.
• CRM: Email the quote, on a deal with products: an email to its contact with each product and the total, for Draft with Sinai to word if you like, logged on the contact and the deal once sent. A deal made from a lead that wrote with the form on a product's page starts with that product.
• CRM Home: What sells, the products on deals won in the last 90 days.
• CRM: Draft with Sinai, in the email composer: the model you chose on Sinai's page writes the email from the record, its newest activities and what you ask for, word by word into the subject and the message. Stop it, or undo it to get your own words back. A model that runs off your PC is asked about first. Nothing goes to Alelyon.
• CRM: a record links to where it came from: a lead from Pages to the person's page, a lead that wrote with a product's form to that product's page, and a product in the price book to its page on Pages.
• CRM: the email composer's template menu says "Start from a template" until one is picked.
• The CRM can log the email people in it send you. Switch it on under Your mailbox on CRM Home (iCloud Mail and Gmail): the app reads your inbox on this PC, read-only, as Home opens and at most every 15 minutes, or when you press Look now, and each message from one of your leads or contacts lands on their timeline once, with who sent it, when, its subject and its first words. Nothing in your inbox is marked, moved or deleted. Not yet for Outlook.
• The CRM has Reports: the pipeline by stage, the forecast and wins by month, deals by company, leads by source and by month, contacts by company and activity by person, or any grouping of your own. Each is a chart and a table with its totals, exported to CSV; a bar, a row or a cell opens what it counts.
• CRM Reports: save the report on show as your own, under a name, and find it again under Yours beside the standard reports. A saved report whose choices you change offers to save the changes, or to keep them as another under a new name.
• CRM Home: show up to 4 of your saved reports on Home, each as a small chart with its total; a press opens it on the Reports page.
• CRM Reports: group deals by product, with a new standard report, Deals by product. A deal counts under each of its products with those lines' total, and once in the totals. A product's row lists the deals that carry it.
• CRM What sells: a product's name lists its deals, and a link opens every deal by product, at each stage.
• CRM Reports: a chart of how many puts its middle line on a whole number, and every line on a chart says where it stands (a line at 2.5 no longer reads 2).
• alelyon-cli: `mcp --http` refuses a Host or Origin that does not name its port and keeps its key file owner-only on Unix; `mcp check` and `mcp install` say when Gemini CLI keeps the server off in a folder it does not trust.
• A person's name opens their card in more places: who replied to you or mentioned you on Home, who invites you into a group project, whose a group project is, the people you can take out of yours, whose a thread under Atlas's Recently active is, and a CRM record's owner.
• A person's or an organization's page on Pages offers their card from its menu, with what else the app knows of them and what you can do from there.
• Features that are here no longer wear a badge saying so. The Account page's roadmap is now Still to come: only what the app does not do yet, each saying what is missing, with no "Here now", "Step", "Later" or "No screen today" chips. Home's More sections no longer counts how many of each section's features have arrived.
• Pages, sign-in and Friends are listed as here, which they are; the developer console's keys and Billing say what is still to come of them.
• A note that says where to go now goes there: Sign in, on the CRM, the Marketing products, Group projects and the console; Make one on the website, under Monitors; Open Pages, Products, when you have no product to choose; and Open Settings, Account, on the board's paid-plan note.
• A person or an organization found in the command palette opens their card, which goes on to their page.
• An organization has one card, as a person does. Press its name on a person's card (the organization their title names) or in the console's Service accounts, and it opens over what you are on. Esc or a press outside closes it, and what was open is back. It shows, each only where it exists:
• Records are joined only where they carry the same ticker. A team plan names no organization, so it does not show here.
• A CRM record made from an organization's Pages page now links to that page, as one made from a person's does.
• Editing a record that came from Pages no longer leaves a note on the Pages screen saying it is a lead.
• Make your own API keys in the app. The console has an API keys part beside Service accounts. It lists your keys with what each may do, when it was last used and when it expires. It makes a key with a name, permissions and an expiry, and shows the secret once for you to copy. It revokes a key after asking, and a press shows a key's calls. Rolling a key, or limiting it to some networks, stays on the website, one press away.
• Typing "key" in the command palette finds every place you keep one: your API keys, your models' keys, the OpenAlex key, and the keys pinned for checking receipts.
• Nothing changes in the app: its owner build's tests now remove their temporary folders however they end.
• A person's card now shows what your CRM holds on them. The leads, contacts and deals made from their Pages page are listed, and pressing one opens it in the CRM, where Back returns to the page you opened the card on.
• With none, the card offers Add to the CRM. The new lead then appears in its place, or the card says why it could not be added.
• The card asks your CRM each time it opens, so a record deleted, converted or changed by a teammate shows as it is now. It works even if you have not opened Marketing yet.
• A person has one card. Press their name and it opens over what you are on: in a group project's people, a friend request on Home, your friends panel (a request either way, or the name above a chat) and Settings' Team part (a teammate, who invited you, whose team you are on). Esc or a press outside closes it, and what was open is back. It shows, each only where it exists:
• Its actions: message them (a friend), accept or decline their request, ask them to be friends, invite a friend to one of your group projects, add them to your CRM, and open their page.
• Records are joined only where they carry the same Pages username. Someone on a list without one is never taken for anyone.
• A plug-in's page can ask the app to open a link: a file at its line opens in the editor, a web page in the browser, and Back returns to the page. On Fleet's branches view, each file that several branches change opens in the editor at a press.
• Nothing changes in the app: its tests no longer read or write the preferences kept in your home folder.
• A reply you stopped is not offered to go back where its ask came from: only a finished answer is, the newest since the ask.
• Nothing changes in the app: its tests now remove their temporary folders however they end, so test runs stop filling the disk.
• The app no longer names one vendor where any agent will do. Lattice's Tools page calls them coding agents and says, for each, where your messages go; Settings shows how to connect any MCP client (Cursor, Gemini CLI and others) beside Claude Code and Codex; Research offers its archive to any coding agent; and the Cloud model choice no longer names a lab.
• A coding agent that cannot install because Node.js is missing now says so, for Codex as for Claude Code.
• Lattice reads a trusted folder's skills from `.agents/skills` too, where most coding agents look, beside Claude Code's own skills folder; a skill kept in both is read once.
• Versions pushes a version for you. Push it… shows what runs (git's push of the version's branch and tag to origin, with your own git and its sign-in), and a second press sends it, then marks the version pushed. When git cannot push, what it said is shown. I pushed it stays for a push made by hand.
• Each note waiting for the next version opens the change it came from: its session's chat, or what its commit changed, read-only in the editor.
• Groundwork for bringing outside sessions into Alelyon, part two: Lattice can bring a session another app saved in as a new conversation. The agent forks the saved session, which stays as it was; or, for a session at rest, it can be moved in whole instead. Its messages become the conversation's turns, in the folder the session worked in and in a task thread of its own or the one you name. The conversation then goes on in that session, so the agent keeps its whole history, after a restart too. Nothing in the window offers it yet.
• Lattice reads a trusted folder's `GEMINI.md` as rules for its chats, after `AGENTS.md` and beside `CLAUDE.md`, so a folder set up for Gemini CLI works the same in Lattice. Like them, it is named when you are asked to trust the folder, and an agent's change to it is kept apart for you to confirm.
• `/init` reads a `GEMINI.md` already there before it writes the folder's `AGENTS.md`.
• Groundwork for bringing outside sessions into Alelyon: Lattice's agent client reads what an agent can do with the sessions it saved, lists them, and opens one as a fork (the saved one left as it was) or loads it, each only where the agent says it can. Nothing in the window uses it yet.