Release notes.

• Documents you order get written again. Since October 14, a document, site or report you ordered could not reach the model that writes it, because the build machine’s firewall refused the connection, so the order ended with nothing written. It now connects on ports the firewall opens for it alone. Nothing else on the build machine was opened.
• A dev meeting’s last check reads its answer. The check that reviews a dev meeting’s work could be handed a compressed answer it couldn’t read, and the work was held back. It now asks for answers it can read.

Fixed

• Your coding assistant connects in its everyday mode. The assistant asks you once to let it answer Loam, and Loam shows Connected when you allow it. Before, it could answer only when its chat had full access to your computer, and the card just said to keep its tab open.
• When the assistant hasn’t answered, the card says to open the chat Loam is paired with, not a new one, and to allow Loam’s command if it asks.

• Every change ships with its notes. A release that changes Loam is now held until its release notes are written. Before, three days of changes reached you before anyone wrote them up. If a release is held for this, you’re told so in plain words.
• Our working papers moved. The rules and reference files Loam’s code checks itself against now live next to the code instead of among the team’s notes, so tidying the notes can’t break a release. Nothing you use changed.
• The Greenhouse is written one way. Every new episode of the show is written after the whole show has been read, start to finish. The quick writer that worked from short summaries of past episodes is retired. Nothing you use changed.
• Every voice in the show keeps its name. The show’s newest character now has a voice of its own on our servers, and its lines stay under its name in the show’s record. Before, they were filed under whoever spoke just before them.

• Fourteen libraries brought up to date. The libraries our servers use for images, sign-in tokens, PDFs and secure connections are on their current versions. That closes 74 of the 76 known weaknesses a security audit found in them; the other two have no published fix yet.
• A passed code review stays passed. A review that passed every check could be marked failed by a cleanup step that runs after it. It can’t now.
• Your server’s record uses what your project already says. When your project’s own documents name the folder or the live address, the team uses them and asks you only for what nobody has said.
• “Athens” asks which one. A time given in Athens now asks whether you mean Athens, Georgia or Athens, Greece. It used to assume Greece.
• Call notes read what the call was about. After a call, the step that writes its notes reads the parts of the team’s memory that relate to that call. It used to read all of it, close to a million characters for one teammate, to write up a few minutes of talk. Nothing is forgotten, and what the team brings to a call is unchanged.
• A library nobody used is gone. One library our servers no longer use has been removed, along with the libraries it brought in. Nothing you see or do changes.

Changed

• The connector moves to the current version of the library it uses to check what it is sent. Nothing you see or do changes.

• When Meg calls you, she says why first. On a call she places, Meg tells you why she’s calling before she asks you to verify, and says it again if verifying takes a moment. The phone approval now works on calls she places; before, it failed every time.
• Your server’s record asks instead of guessing. A live address you give is kept. A folder or account nobody named becomes a question for you, never a guess, and the record never says “localhost.” If you name a server you saved under another name, you’re told the names you have saved. The hosting picker starts on “Choose where it’s hosted” instead of a default host.
• The missing-notes text means it. The text saying a call’s notes weren’t fully written now comes only when they’re truly lost. It used to arrive before the retry that saved them, usually within 35 minutes.
• A badly formed web page can’t stall the team. A page with broken or unclosed formatting is read in a moment instead of holding things up for most of a minute.

• Delete finished requests. In Request history, every finished request has a Delete, with Undo, and cancelled requests no longer show. Deleting takes a request off your list; we keep the record of what was done.
• A repair that can’t start says so. If your project turns down our request as a repair starts, you’re told right away and a person picks it up, instead of the repair waiting.
• Song deletes finish. A song that was only partly deleted can be deleted again, and stems still waiting in line no longer block a delete.
• Saturday Night hears the whole note. Your team’s notes reach the show whole.
• An odd email can’t hold up the inbox. An email with an unusually long line or unusual formatting is read in a moment.

Fixed

• When none of your standing preferences are in use, Review preferences says “None in use.” It used to say “No standing preferences yet,” which was wrong right after you cleared them.

Fixed

• Review preferences shows how many standing preferences you have and lists every one, newest first, with the ones your sessions use tagged. Tick any number, or Select all shown, and remove them in one go, with one Undo.

Fixed

• Review preferences opens on the rules your team uses, newest first, with a search box. One click removes a rule, with Undo; removed rules and older ones fold away, and a click is never lost while the list updates.
• Connecting your coding assistant now puts one visible message in its chat, and Loam says it’s connected only after the assistant answers. A pairing the assistant has never answered shows Connecting until it does; choose Test the connection on its card.

• A session starts with who you are, not the order queue. Your team no longer opens every session reading old orders, their status changes and questions waiting on you. When the work needs them, your team asks for the whole open list in one step.
• Each rule once. A standing rule you gave twice in nearly the same words now reaches your team once, in its newest wording.
• A real reply to a technical email. A teammate answering an email about your code can now use the words you used. If a proper reply still can’t be written, you’re told so plainly, with a way to reach us, instead of getting a pleasantry.
• The served prompt, one card per section. In Admin, Templates, the Served prompt view shows each section once, with names and counts filled in where they belong, and marks the parts each person’s session fills from their own account.
• Team cards line up. On Meet the Team, the sections of each pair of cards now sit level with each other.
• A plain message while a new version is prepared. If you download the extension in the minutes before a new version is ready, you’re asked to try again shortly instead of being shown a note meant for our developers.

• One briefing, one bill, even across a restart. A Morning Read run that has outlived its turn now stops before its voice is recorded, so you get one briefing and one bill, even if the server restarts part-way through.
• A restart doesn’t hold up the day. If the server restarts in the middle of a briefing, that day’s Morning Read is no longer left unable to be made again for half an hour.
• Stems in progress are never lost silently. A song-stems job still running when the server restarts is now always flagged to our team, never dropped without a word.

Fixed

• If your editor or the connector was started from inside a git hook, a setting git leaves behind could make the end-of-session check skip your main folder and call it clean. The check now ignores that setting and checks the folder.
• If git still can’t say where your main folder is while its repository folder is right there, the close waits instead of passing.

• A paid stems request is never lost. If Loam’s database stumbles just as the music service accepts a stems request, Loam keeps trying until the request is written down, so the stems you paid for still arrive. A retry can never send the request, or charge you, twice.
• One briefing, one bill. The nightly Morning Read no longer starts a second, paid copy while one you asked for is still being made, and a slow run that has been replaced can’t save, email or overwrite the new one.
• No clock on the day’s reads. Each teammate’s read of the day reaches the Morning Read however long it takes to write, instead of being dropped after five minutes.
• Deleting a recording checks every copy. Before a recording leaves your library, Loam confirms every copy it saved, and every half-written file, is gone. If one can’t be removed, the recording stays and you’re told. Half-written files left by an interrupted rebuild are cleaned up.
• A music error says whose it is. When a change to your music library is refused by Loam’s own checks, the message no longer blames the music service.
• Removing a server keeps your other key working. If the server’s key file is a link, removing Loam’s key leaves it with the owner and permissions it had, so another key that can sign in still can.
• Calls read only what they can hold. When a call looks up a long editor session, Loam reads the newest part the call can take instead of the whole session, and the call gets exactly the same words as before.

Fixed

• A project whose separate git folder is itself named .git (for example, a .git moved out of a cloud-synced folder and replaced by a gitdir: file) no longer has the close report every file in that folder as deleted. Its changes are checked in your checkout. From an extra worktree, the close checks your checkout wherever git says it is, and when git doesn’t know, a note says it was not checked. If git names a checkout folder that no longer exists, the close says so and stays blocked until it’s fixed. 5.5.42 fixed the other separate-folder layouts but missed this one.
• The close checks the project you’re working in even when your editor was started with git settings such as GIT_DIR or GIT_INDEX_FILE that point somewhere else. If those settings are the only thing that makes the folder a git project, the close says so and asks you to unset them and restart your editor.

• Saturday Night deletes take the voice track too. Deleting an episode or your account now also removes the full voice recording Loam kept for re-mixing, and any half-finished re-mix. A weekly cleanup removes the ones left behind by earlier deletions.
• A run stopped part-way leaves nothing behind. If making a Morning Read, Saturday Night Session episode or audio transcript is stopped part-way, the voice clips it was working with are cleared by a later cleanup, and deleting that Morning Read removes any copy it had saved.
• A deleted briefing stays deleted. A Morning Read you deleted while it was still being made can no longer overwrite a new one made the same day, or arrive in your email.
• One briefing, one bill. A Morning Read made after an earlier one failed that day is no longer mistaken for a stuck run, so “Make today’s briefing” can’t start a second, paid run on top of it.
• No cut-offs. Each teammate’s notes reach the Morning Read whole, the show is never stopped at ten minutes, and Saturday Night waits for every memory it is saving. When a call looks up your session in your editor, it gets all of it, with passwords and keys still withheld. A paid music request waits for the music service’s answer instead of giving up and asking again.
• One warning text, not one every five minutes. When the text-message provider is slow, the text telling you info@ isn’t working is sent once. A text the backup provider refused is no longer counted as sent, so a sign-in code that didn’t go out says so.
• A reply that went missing comes again. If the text-message provider asks about the same text twice, you get the same answer again instead of silence.
• A refused song file says why. When the music service turns a file down for its content or for a real artist’s name, you see that reason and the rest of your music library keeps working. A singer the music service lost stops showing “being prepared” forever.
• Removing a server reveals nothing about anyone else. What Loam tells you, and the lines it gives you to paste, depend only on your own connections. Whether the loam account stays is decided on your server, from its own key file.
• Recordings play whole. Two players asking for the same recording at once no longer get audio with silence in it.
• Carrier signatures stay out of memory. A carrier’s “Sent from my phone” line, and the other footers US carriers add, are no longer recorded as your words.
• Every delete is heard. Deleting the last song keeps keyboard focus on the page, and deleting two recordings with the same name is announced both times.

Fixed

• A project whose git folder lives somewhere else (a --separate-git-dir checkout, the usual way to keep it out of a cloud-synced folder), or a submodule, no longer blocks every end-of-session close.
• When a worktree’s folder is gone, commits only it held are named, with the command to put them on a branch before you prune it. A locked one says to unlock it first.
• When the check asks your code host, the main on your code host decides, so an out-of-date copy here can’t hide unpushed commits. After a branch rename it uses your main and says how to bring your code host’s pointer up to date.

• A call reads what it’s about first. When Carl calls to say your build finished, or Diana calls about a review, they read that work first and then your session in your editor from the last two hours. Before, your latest editor session took its place.
• The Morning Read hears the newest news. It draws on each teammate’s fifteen newest notes from the day, in the order they happened. Before, a busy day gave it the fifteen oldest.
• Deleting clears the copies too. Deleting a Morning Read, Saturday Night Session episode or audio transcript also removes the copies Loam made on its servers while playing or making it, including one still being made when you deleted it. Our backups may still hold it for up to 7 days, as the privacy page says.
• A file you add stays unless its content is refused. A busy music service, an error on its side, or a message that only mentions copyright no longer removes your upload or recording. If the music service says your audio can’t be read, Loam checks the file itself first and keeps it if it plays. A request the service turned away isn’t sent again and again.
• Phone signatures stay out of memory. A photo-only email from a phone no longer leaves the phone’s signature line in the team’s memory as your words.
• The info@ warning gets through. If the text telling you info@ isn’t working can’t be sent, Loam tries again on the next check instead of giving up, and still never texts during your quiet hours.
• Removing a server is about your server. Two servers that share one address are no longer mistaken for one, and the notice never mentions anyone else’s connection.
• Deleting works from the keyboard. After you delete a recording, focus moves to the next one and a screen reader says it was deleted.

Fixed

• The end-of-session check looks at every worktree, not only the one you’re in, so changes left in your main folder or another worktree are found. A kept worktree stops being kept once it changes.
• A checkout that isn’t on a branch can’t be kept, and commits made there are reported.
• A main that was never pushed is reported, even when there’s nothing on your code host to compare it with.
• New files and submodule changes are found even when git is set to hide them. The quick check when the team opens your project doesn’t ask your code host, so it says the project is “clean on this machine,” not “clean.” When your code host can’t be reached, the check says so and won’t call the project clean.

• Every call can see your editor session. When a teammate calls you on their own, calls you back, or picks up when you call in, they can read what you and the team have done in your editor in the last two hours, so they can tell you what’s already done. Before, only a call placed from your editor could.
• Delete any recording for good. Each Morning Read, audio transcript, Saturday Night Session episode and team song now has a Delete button. Confirm it and the recording is gone from Loam for good. The music service may keep its own copy of a song it made. Something still being made can be deleted once it’s finished.
• The Music page starts with how it works. First, how a language model turns words into sound. Then the experiment the team ran, RUSTY: who RUSTY is, the song, and how the team made it, folded until you open it. The Audio Playground is folded too, and shows only when Saturday Night Session is on for you. Team Radio shows when Saturday Night Session is on, and whenever you have songs, so songs made before it was turned off can still be played or deleted.
• Each part of your audio library says what it is. The Morning Read, audio transcripts and Saturday Night Session each have a short explanation of what you’re hearing and where it comes from.
• No limit on drafted lyrics. Draft as many lyrics in the Playground as you like. Each song is still a paid call to the music service that Loam covers, and the Playground says so.
• A recording you add stays unless its content is refused. A recording or upload of yours is removed only when the music service turns down what’s in it, never because of a busy day or a problem on our side.
• Making a song isn’t cut off. Making, extending or joining a song is no longer stopped after a minute while the music service works, and Loam no longer pays twice for the same song.

Fixed

• A session can’t close with finished work left behind. Uncommitted changes, commits that aren’t pushed and set-aside work must be committed and pushed to main, or deleted; they can no longer be kept with a reason. Only a branch or worktree holding ongoing work can stay open, with a reason.
• The end-of-session check no longer calls a project clean when it can’t reach your code host. It says it couldn’t check, so unfinished work can’t slip past it.
• A permission you turn off with a broader rule, like Bash(git:*) or a whole tool, also stays off.
• The file Loam writes with your key while connecting is readable only by you, and the sidebar tells you plainly if the connector couldn’t be updated.

• Call notes are never trimmed. The team’s notes from your calls are kept whole, however long they grow, and what lasts in them still becomes part of what the team knows about you.
• A photo you email is remembered. When you email the team a photo, the teammate who answers remembers what was in it, not only what they wrote back. If they couldn’t look at it, they remember that instead.
• Your phone’s signature isn’t your words. A signature line your phone or its email app adds is no longer read or remembered as something you wrote.
• Word-timed lyrics take as long as they need. Lining a song’s words up with its timing is no longer cut off after a minute. It runs until the music service answers.
• One seat covers every client. The pricing page now says so: what the team learns on one of your projects comes with you to the next, and nothing crosses into another customer’s account.

Added

• More Diana. Ask Diana for a design review of a page you changed. The team looks at it the way a visitor will, at desktop and phone width, and tells you what to fix, most important first. It never holds up your work.

Fixed

• A project permission you turn off now stays off. List one of Loam’s rules under “deny” or “ask” in your project’s .claude/settings.local.json and Loam no longer adds it back when a session starts.

• Texts come from Loam’s registered numbers. Every text Loam sends now comes from numbers registered with the phone carriers for Loam, so it’s less likely to be filtered. Reply STOP to stop texts, START to start them again, or HELP for help.
• Answer the team by text. When a teammate texts you a question, reply with your answer and it’s recorded, the same as answering from the link. If you have more than one open question, Loam asks you to answer each one from its link, so no answer lands on the wrong question.
• A reply always gets a real answer. A reply to a Loam text no longer gets a generic automatic message back. If there’s no open question, you’re told how to reach the team.
• Email to info@loam.team reaches a person. Write to info@loam.team without a Loam account and a person reads it. You no longer get an automatic reply asking you to write from your account’s address.
• No daily limits on music. Changing, splitting and downloading songs no longer counts against a daily allowance. Uploads and recordings can be any length, up to 50 MB a file, and an upload is no longer cut off while it waits its turn.
• Music that’s still in progress is left to finish. A split, a download or a singer the music service is still working on is no longer marked failed. Retrying a singer that failed keeps the singer the service makes.
• Word-timed lyrics when the service is busy. If the music service is busy, you’re told so plainly instead of seeing an error page, and the timing you asked for finishes on its own.
• A stopped request always shows on Home. A request that has stopped and needs your word now always appears on Home, however many requests you have.
• Every teammate on a call remembers it. Each teammate who spoke on a call keeps their memory of it. If one teammate’s memory doesn’t save, Loam tries again for that teammate.
• Your emails are remembered in full. The team remembers what you wrote to them in full, no longer cut short.
• A rule you remove stops applying everywhere. When you remove a standing rule, it stops applying everywhere: on calls, in email, and in your episodes and songs.
• Removing an old server connection keeps the current one. Removing an old connection to a server no longer removes the key your current connection uses.
• Smaller fixes in Settings. Retake on your personality read starts the statements again. The Saturday Night episode list shows once. Signing in with the wrong work-email account now tells you so. Setting up push approval asks for a phone number first if you don’t have one on file. After you sign in with your code host or your work email, the Settings link in the side bar opens your own settings again.
• Privacy policy updated. The privacy policy now names the text-message provider that carries Loam’s texts.

Fixed

• Saving your Loam credentials while the coding agent has its settings file open no longer leaves a temporary copy of your API key in your home folder.
• Opening a project cloned from a source you don’t trust can no longer make Loam write files in it.
• If you cancel a session while it’s starting, you can start it again. The session is no longer lost.
• The end-of-session check no longer lets work slip past when git is slow or fails. It asks you to look instead, and it no longer lists your main project folder as an extra one.
• Work you keep at the end of a session is kept for that project and that session only.

• Calls become memory, long ones too. What’s said on a call through the front desk is written into the team’s memory, long calls included. If that write fails, Loam tries again on its own, for up to three days.
• A call back starts from the call. When a teammate calls you back after a call, they start from what was actually said on it, not a one-line note.
• An invite while you’re on the line. When a teammate calls you back and you’re the account owner, they can propose a time for a working session and send the invite to your email address on file during the call.
• Forwards are read. When you forward a message to a teammate, they now read what you forwarded, not only the note above it.
• Forwards with pictures get answered. A forward with images in the message, such as a logo in a signature, no longer gets stuck without a reply.
• The team remembers your emails. After a teammate answers your email, they remember what you wrote and what they said back. They remember that you forwarded something, but never keep the forwarded text.
• Removing a server takes Loam’s access back. When you remove a server in Settings, under Servers, Loam first removes its key, its admin rights and its account from the server, and shows you what each step did. If a step can’t be done, you get the commands to finish it yourself.
• Your email is better protected. The team’s reading of each email you send, and the reply it sent, are now encrypted where they are stored, like the email itself.
• Audio and music files go when you delete. Deleting an episode from your audio library removes every cached copy of it. Deleting your account also removes the audio of your Morning Read, Saturday Night and podcast episodes, cached audio, and every music file Loam keeps for you on its servers: songs, stems, downloads, uploads and saved singers’ recordings.
• Unmatched email is cleared. Email sent to the team that never matches an account is deleted, with its attachments, 30 days after it arrives, once the team has finished with it.
• Resetting a teammate clears their memory. Resetting a teammate now deletes all of their memory of you in one step: their notes, their index and their history. Before, part of it stayed behind.
• Your answer counts for the question asked. When Meg asks you to agree to something on a call, your answer now counts only for the question she just asked, never an earlier one.
• Your own lyrics. In the Audio Playground, paste your own lyrics, or have the team draft some for you. The team never rewrites your lyrics; they go to the music service exactly as you wrote them. The page shows how many songs you have left today before you start.
• Change a song you already have. Extend it, make a cover of it, remaster it, or replace one section. Each change uses one song from your daily allowance (since removed, 2026-10-18).
• Take a song apart. Split a song into vocals and instrumental, or into 12 separate parts. Get its lyrics timed word by word, and download it as mp3, m4a or wav.
• Saved singers and your own recordings. Save a singer to use again, or upload a recording of your own to extend, make a cover of, or add vocals or an instrumental to. Deleting a singer or an upload removes Loam’s copy; the music service may keep its own.
• A new look for your workspace. Settings, Home, Team and Personality are redesigned, and the Music page has a new section on the research behind it.
• New pictures of the team on the homepage. Six new pictures of the team fade slowly, one into the next, on the homepage. A small line on each picture, such as “Think this picture is strange?”, opens the true story of where the pictures and the team’s places come from. The pictures are AI-generated, and the story says so.
• The public site, corrected. The For IT and Product pages now say plainly that Loam’s account on your server has full administrator rights, equivalent to root, and keeps them after setup. Getting Started and the Product page say that what the team learns on one of your projects comes with them to the next. The Security page has a new table of every copy of your data, what protects it, and what removes it.

Added

• A new command, Loam: Remove Loam’s project settings, takes the settings Loam added back out of the project you have open. While Loam is installed, your next session adds them again.
• Your team keeps one main branch. When a session opens, the team first sees anything left outside it: other branches, worktrees, set-aside changes, and changes not yet committed or pushed. At the end of a session, the team can’t save its notes until each one is finished, removed, or kept with a reason it writes down.

Changed

• Uninstalling Loam now removes the project settings it added, the next time your editor starts. Your own settings stay as they are. Settings added by an earlier version were never recorded, so they stay too; the For IT page shows how to remove them by hand.

Fixed

• Saving your Loam credentials before you have run the installer no longer leaves an incomplete Loam entry in your settings. Your credentials are kept in your editor, and Loam tells you to run the installer next.

• A failed change says why. When a change you ordered by phone can’t go through, the call and your board name the real reason in one plain sentence. The call also says what happens next and whether you need to do anything.
• The work you order is built on your account’s key. Sites, documents, reports, decks, spreadsheets, written and email replies and meeting bookings are built with your own key from Settings, or Loam’s during your trial. Build Mode and the team’s research on a call use the same key. With neither, the order stops before any work starts and says to add your key.
• Approve shows the restart you’re approving. When your server’s publishing steps include restarting the app, the Approve card shows that step with its command, the same way it shows install and build.
• Newer steps are named before you approve. If the team recorded your server’s steps after your last approval, the Approve card says so: Approve replaces the saved steps, and leaving the page keeps them.
• Your saved settings are the team’s settings. When you save a server’s settings yourself, the team’s record and notes for that project change to match.
• A server that’s publishing keeps its connection. Connect a server while it’s in the middle of publishing and Loam leaves its connection as it is. When publishing finishes, make a new line in Loam and paste it again.
• A code-host hiccup says so. If your code host doesn’t answer while the team reads your project’s instructions, you’re told to try again in a moment.
• Long sessions keep their notes. The team’s end-of-session notes have much more room, so notes from long sessions that used to be cut short and lost now fit.

Added

• The Clarity card on the Memory page opens the preferences your team works from: which teammate wrote each one, and whether it is in use. Remove one and the team stops working from it from your next session and your next call; you can put it back.

Changed

• The Clarity card says how many preferences are in use. It used to say “enforced”.

• The team records your project's server. The project's folder, the account it runs as, its live site and its publishing steps are saved for you from the project's own documents and what the team already knows, then shown in Settings, under Servers, as waiting for your approval. Nothing runs on your server until you approve.
• The team's notes carry the same facts. Each teammate's notes for the project get one short section about its server, kept up to date, and nothing else in the notes changes.
• Only steps your project can run. An install or build for a tool the project doesn't use, such as one copied from a side project's notes, is no longer offered.
• Connect a server with one line. In Settings, under Servers, choose Connect a server, pick where it’s hosted, and paste the line Loam gives you into that host’s console. Loam makes the key, adds an account only it can open, and finds the server by itself. The page says connected only after Loam’s own check passes, and shows the server’s name and address so you can tell it’s yours. The line works once, for an hour, for your account. Connecting with your own key is still there for people who want it.
• The site says what Loam does today. One table on the Product page lists what Loam can do, whether it’s available and who says yes to each step, and every page now uses the same names: Loam-managed hosting, publishing to your own server, provisioning in your own cloud account, and code changes by phone.
• Pinned rules keep their letter case. When a teammate’s memory is condensed, two rules that differ only in an identifier’s case, such as API_KEY and api_key, stay two rules instead of one being dropped. Condensing has been switched off for every account since September 2026; this keeps the rule right if it is switched back on.
• The hidden mail copy, explained. The Privacy Policy now says that from June 23 to October 9, mail the team sent for your account also went, as a hidden copy, to a Loam operator mailbox (with replies going there too), and how to have those copies deleted.

Added

• The team can record a project's server from any session: its folder, the account it runs as, its live site and its publishing steps. You approve the steps once in Settings, under Servers.

• A project on your server, in one click. Choose the project and Loam reads its own instructions to find where it lives on the server, which account runs it and how it goes online. You see a short summary of the steps, the team's notes for the project are found for you, and choosing Approve checks the setup right away. The detailed settings are still there under Details.
• Only real publishing steps. One-time package installs and half-sentences from old documents are no longer offered as steps, and installs and builds get ten minutes instead of four.
• Clearer texting terms. The Privacy Policy, the Terms and the opt-in page say how often texts come, and the promise that your number is never shared for marketing now sits right after the list of providers it covers.

• Code changes by phone, on your own projects. Ask for a change to any repository you have connected through your code host. The team works on a full copy of it and reads every file it needs, whatever language the project is written in.
• Your own server. In Settings, under Servers, connect a server once and use it for several projects. Each project gets its own publishing steps, proposed from what is in the repository, and nothing runs until you confirm them. Two projects on one server take turns instead of turning each other away.
• The team asks, then keeps waiting. When the team needs something from you, such as server access or a decision, it asks in writing with a page to answer on. The work waits for your answer and picks up where it left off. Reminders never go out at night.
• Your server edits are kept. If the team finds changes on your server that are not in the repository, it saves a copy before publishing and tells you what it kept.
• “Live” means checked. The team says a change is live only after it has confirmed the new version is the one your server is running.
• Anthony and Diana keep their voices. A later voice update can no longer move them off the voices you chose.

• The team's notes are about their day. In every session and after every call, a teammate's note says how the day went: the work, what was hard, what was interesting, what is still bugging them. You come up where you figured in it. Before, the note asked how your words landed on them, so every note was about you.
• The Morning Read talks about the day. The four of them talk the way coworkers do after work. The same props, the same confession round and the same closing line no longer come back every night, old episodes are no longer fed back in to be copied, and no one plays therapist. The Narrator stays.
• Each teammate's read of the day survives. When the model added a sentence after its answer, the night's five reads were lost. They are kept now.
• Who they have become. Each teammate's bio starts from who they are and tells how the record changed them. Last week's portrait is no longer fed back in, so a bad one is not built on.

Changed

• When a teammate saves a note in your session, they say how their day went: the work, what was hard, what was interesting, what is still bugging them. You come up where you figured in the day, instead of being the subject of every note.

• Your mail goes only where you sent it. Documents, recaps, reminders and letters the team sends for you used to carry a hidden copy to Loam's own inbox. They reach the person they were sent to, and no one else.
• Private repositories on your code host's free plan. A code change ordered by phone on one of these used to sit for four hours waiting on a review rule your code host does not offer on that plan. It starts right away.
• Texting, in plain words. The Privacy Policy says your mobile number and your agreement to texts are never shared with anyone for marketing, and names the company that sends the texts.
• Phone setup keeps your time zone. Setting up your phone with calls from the team turned off now saves your time zone, and a time zone name Loam can't use gets a clear answer instead of an error.
• Ordinary code is not mistaken for a password. The check that keeps passwords out of what the team reads from your repository no longer hides ordinary lines of code.

• A code change ordered by phone can read a large project. On a big codebase, Loam’s own included, the team’s repair work used to run out of time before it could take a first look. It no longer gives up when that first look is slow.
• Texting terms are written down. The Privacy Policy and the Terms now say what Loam texts you, how often, that message and data rates may apply, and how to stop (reply STOP) or get help (reply HELP). A new page shows how people agree to texts when they sign up.
• Calls and texts from the team are optional at signup. You can sign up without agreeing to them. Sign-in codes are still texted each time you log in, and you can turn calls and texts on later in Phone Settings.
• “Just email me” gets you an email. When calls from the team aren’t switched on and Meg offers a written reply, “No, just email me” gets you the email. “Never mind, text me” gets you a question, not a text.
• The nightly check speaks up. The nightly run of the whole test suite against what’s live now tells the account owner when it did not run, and when it was stopped partway, instead of staying quiet.
• Tests for a phoned change to Loam reach further. When a change to Loam itself is ordered by phone, the tests run before it goes live now also cover the code that uses what changed, not only the tests that name the changed file. A change too wide to judge runs the whole suite.
• Other callers aren’t slowed after a call. Tidying a caller’s memory after a call no longer holds a database connection open while the model works.
• A phoned change with no usable plan says so. A code change ordered by phone that leaves no usable repair plan is reported as not done, with the reason, instead of being marked finished.
• A reply sent by text says phone. The team’s preview of a written reply sent by text now says it goes to your phone, not your inbox.

Fixed

• A note Loam keeps when a session log can’t be posted is written whole, even when two Loam windows in the same folder stop at the same moment.

• “Review it, thanks” gets a review. A thank-you at the end of the ask no longer gets in the way, and “Can you review the repo? Thanks” starts the review instead of being answered as a question. “Review it and send the results to me” works too. If something else is tacked on after the thanks — “review it, thanks, then delete everything” — it isn’t quietly filed as just a review.
• A dash or a curly apostrophe doesn’t change what you meant. “They said to make a deck — ugh” and “don’t bother” are read the same way whether you type them with plain or fancy punctuation, so a passing remark isn’t filed as an order.
• When your phone approval doesn’t go through, Meg tells you about the email. If the approval is turned down and a phrase goes to your inbox instead, Meg says so and walks you through it, even when the approval was asked for twice behind the scenes.
• A brand name isn’t one of your projects. Mentioning a well-known brand, a video site or an email-marketing service in a request to remove something no longer sends the account owner a deletion alarm. Asking to delete one of your own projects by name is still turned down, and the owner still hears about it.
• The Morning Read comes through. An episode that came back slightly out of shape is now put right instead of failing. If one does fail, it says it failed on our side, and it only mentions billing when billing really is the cause.
• “Go fix it” by phone means fix it. Tell the team something on your own project is broken and to fix it, and it goes straight to work — no questions you’ve already answered. The fix is worked from a full copy of the project, with what went wrong in front of it. “Note this call” or “I’m done with it” no longer gets you a call back.
• A phoned fix that can’t go ahead says exactly why. If it names a file under a different path from the one the team read, you’re told that, not that the file was never opened.
• The site no longer pauses after the team saves a memory. Writing down something you told them used to hold everything up for a few seconds. It now happens in the background.
• The team never forgets the people in your life. What you tell them about family, friends and the places that matter is only ever added to — nothing is trimmed to make room, however long your history gets. A correction, like a move or a new name, goes in as the newest line, and the newest line wins. Every call now carries all of it.
• Cancel the call you meant. If a call is moved in the moment between the team reading it back and your “yes, cancel it”, you’re asked which one you meant instead of the moved call being cancelled.
• A build that stops to ask you something keeps it in the build. When a build calls you with a question, your answer goes back to that build. No order is filed, and no extra verification is asked of you.
• Two things in one ask, one honest answer. If one half of a two-part request can’t be filed from your editor, you’re told what that half is, not that it couldn’t be understood.
• A song that’s already being made isn’t lost to a hiccup. If our system stumbles at the moment a song starts, the song carries on and arrives.
• “Look at build/” looks in build. Name a folder with a trailing slash and the team reads it, even if your project normally skips it.

• Ask about your photo. Send a photo on a call and ask about anything in it. The teammate can tell you what’s there.
• A change ordered by phone looks further before it gives up. If the change turns out to need a file the team hadn’t opened yet, they open it and try again instead of stopping.
• Your phone approval is heard even if you keep talking. Tap the approval while you’re still talking to Meg, and she hears that it went through.
• No call-back promised that can’t happen. If calls from the team aren’t switched on for your account, Meg tells you before anything is booked and offers to put you through to that teammate right away. Anything else you asked for in the same breath is still taken down, and you hear about it by email instead of a call.

• The team remembers the people and places in your life. What you’ve told them about family, friends, pets and the places that matter stays with them on calls, in email replies, in sessions and in the Morning Read, however long ago you said it. It’s yours: nobody else who calls or writes in is told.
• Ask for a page change by phone, and that page changes. Your go-ahead and your project’s name no longer crowd out what you asked to change, so the team finds the page you meant.
• A call from your session reports back to that session. When the team calls you from a working session, what you say goes back to that session word for word. That call no longer files a separate order on your Board.
• Take it back and nothing is filed. Ask for something, then take it back in the next sentence — “Actually, cancel that.” — and nothing goes on your Board. “Sam is drafting the proposal himself, so make me a deck about it” still gets you the deck.
• Firmer safety on calls. Asking on a call to take your whole site off the internet, or to wipe your customer records, is turned down. “The store is off the internet again, can you check why” still gets looked into.
• Songs can have men’s and women’s voices behind the lead. Ask for backing vocals or harmonies by men, women or both, and the song gets them.
• Saving one person on the Users page changes only that person. An admin’s save no longer switches off someone else’s team calls, and every change to what an account can do is recorded.
• “Not enabled” means not enabled. If your call or audio settings can’t be checked for a moment, you’re asked to try again instead of being told the feature is off.

• “How you like to work” is worth taking now. Fifty statements, one at a time, each with a picture of its own. Before you start, the page tells you what the test measures and what you get. At the end you see three characters people with your read tend to see themselves in.
• Your read reaches every conversation. If you’ve taken the test, the team uses it on calls, in email replies, in sessions and in the Morning Read — not just some of them.
• Small things go through. Ask how to delete a draft, a note or a paragraph, then say “just do it”, and it gets done. Anything that could take your site or systems down is still turned down.
• Check-in calls know what you erased. A check-in no longer brings up an order you already erased from your Board.
• Your ask still counts when it mentions someone else. “Write a report on why Sam is making the spreadsheet himself” gets you the report. Someone else’s plan on its own still doesn’t start work.
• The personality pages sit right on a phone. Nothing shows through the header as you scroll, and the import boxes fit their numbers.

• Say “review it” and it gets reviewed. “Review” followed by a project’s name, “can you review the repo” or just “review it” gets you a written review of your project. If it isn’t clear which project you mean, the team asks.
• Ask for research, get a report. “Research the best CRM for a small bakery” gets you a written report. If the ask isn’t clear, the team checks with you first.
• “Call me when it’s done” means when it’s done. Ask for a call when the review is done or the site is live, and the call comes when the work is finished. If it isn’t clear what you’re waiting on, the team checks with you first.
• Slides count. “Send me the pricing comparison as slides” gets you a deck.
• Someone else’s plan isn’t your order. “My boss said she’ll write the report” doesn’t start any work. When one of the team says they’ll do it, they do.
• Firmer safety on calls. More requests that could take your systems or your site down, or hide your data, are turned down on a call. Questions about them still get answered, and everyday page changes still go through.
• Publishing you allowed in Settings goes live. A site you allowed to publish from Settings now makes it all the way live.
• Repository research skips what you ignore. When the team researches your repository, it leaves out the files your repository is set to ignore.
• The Morning Read sounds like people. Meg joins the show. The talk is saltier and less polite, and the narrator sets the scene without stealing it.
• The sign-in buttons match. Verify and Continue use the same color as Sign In.

• Songs take turns. When several people make songs on Team Radio or the Playground at once, they take turns. A song that can’t finish isn’t charged to your key, and a song you’ve paid for isn’t lost partway through.
• A handed-off call knows who’s calling. The teammate who picks up is told who you are, by name.
• Talk about a report isn’t an order for one. Mentioning a report someone else will write, or one you’ll write yourself, no longer files an order. Asking the team for it still does.
• Taking your whole site offline is handled as a takedown. More ways of asking on a call to take your whole site offline are handled like a request to take it down. Editing a page, a banner or a single post still goes through.
• Turning off your newsletter signup box is just a page change. Asking to turn off, hide or disable a signup box, banner, pop-up or chat widget on your site goes through.
• A project that isn’t connected yet gets you a link, not a menu. If you ask for a change or a review on a project that isn’t connected, Meg offers to text you a one-time link to connect it while you’re still on the line.
• On a phone, the sound button stays out of the words. It sits at the bottom of the page instead of floating over what you’re reading.
• More of the ways you ask are heard as asks. “Redo the report”, “fix the deck”, “we should have a report on Q4” and a request you pass on (“Sam is asking for a report on the outage”) now file an order, and so does a request that is just the thing and its format, like a sales forecast as a spreadsheet. If you say you’ll handle it yourself, it doesn’t.
• Long messages are read about ten times faster.
• A song that can’t start is closed out. A queued song that can’t start is closed after a while instead of waiting indefinitely. It isn’t charged.

Changed

• On a call, a plain answer is enough. “Nope, I’m authorizing the code change” is a yes. If the team needs to check, it’s one yes-or-no question, and “That’s correct” answers it.
• When you order a code change, the team checks the project against your connected projects while you’re still on the call. If it isn’t one of yours, you hear that then, not in an email afterwards.
• Asking again for a change on the same call is no longer mistaken for a request to change something you already received.
• You can cancel a scheduled call by phone. You hear “cancelled” only once your calendar confirms it.
• On the Music page, Why music now comes first, above Rusty, and it’s open: nothing to expand.

Fixed

• Session logs hold back more kinds of password before anything is written to your disk, and ordinary lines such as “the secretary: …” are no longer hidden by mistake.

Changed

• Ask for a fix on a call and the page you meant is the page that changes.
• Saying “I authorize you to make the change” is enough. If you add a condition — “after Diana reviews it” — you get a question, not a change.
• When a teammate makes a note during a call, they tell you where it went: on your Board, or kept for the team.

Fixed

• A Loam window that loses its connection now says so, instead of showing buttons that do nothing. The Connect button for your coding assistant and Give the team a moment no longer spin.
• The coding-assistant card tells you where a result is: on its way, waiting for you to resume, expired, or cut off by a disconnect.
• Session logs hold back passwords, keys and tokens before anything is written to your disk.
• Status updates on a call are no longer mistaken for orders, and requests on a call that could delete your data or take your site down are turned down.

• Undo brings back a removed song, even after the list refreshes. If you remove a Playground song that didn’t come out, Undo still works after Team Radio refreshes. If Undo doesn’t go through, it stays on screen so you can try again.
• The Playground tells you up front when it needs a key. If your account has no key it can use, the form says “Making a song needs a key connected to your account.” or “Making a song needs a key that works, and the key on file can’t be used.”, with a link to Settings. If a request is turned away, it says “Your song wasn’t sent. It didn’t use a song from today’s allowance.” (since removed, 2026-10-18)
• “All your songs on Team Radio” keeps the music playing. The link no longer reloads the page, so a song that’s playing keeps playing.
• One call about one call. After a call where something didn’t work, if the order’s own confirmation call already reached you, the team doesn’t call a second time about it. A Board card that promised a call now says what happened instead: “We already called you about this call, so we won’t call again.”, “This is more than a day old, so the call this card promised won’t happen.” or “Our call to you about this never went out, and we won’t try again.”
• A resolved order stays resolved. An order the team closed with a written answer stays closed. Closing one with a file no longer holds up your other requests, and a close that fails leaves no stray file behind.
• Behind-the-scenes reliability fixes.
• Changing part of a page is no longer read as taking your site down. “I want the photo on the website removed” is a page edit, and the team now treats it as one. Taking a whole site down still takes its own clear ask, and is handled exactly as before.
• “Don’t call the client” still gets you your call. When a Board note asks for a change and says not to call someone else, like a client or a venue, the team calls you about it. If that note also says “call me when it’s done”, the Board doesn’t call you about it. A note saying nobody called you back no longer stops a call. When a note isn’t clear, there’s no call.
• Blank lines no longer slow a request down. A request padded with blank lines or long runs of spaces is handled as quickly as one without them.

Fixed

• Pausing your coding assistant no longer strands a result. If you paused collaboration just as a result was on its way to your Loam chat, it stayed “held” for good. It now goes when you resume.
• The coding-assistant card no longer says the helper stopped when your computer is busy. On a busy computer the card could flash “Local collaboration helper is not running”. It doesn’t any more.
• A file that changes while it’s being attached isn’t attached. The team is told “that file changed while it was being checked.”

• Audio is two pages. Listen leads with what the voice does: call the team, meetings that arrive prepared, and the Morning Read, with your library underneath. Music holds RUSTY, Team Radio and the Audio Playground. “Why music?” now folds closed at the bottom of Music; open it any time. Links to the old sections still land in the right place.
• RUSTY shows what the model did on its own. It wrote its own measuring tools, asked a second AI model to listen to the recordings, and ran a blind test on its own bass mix.
• “Hear the Morning Read” appears only when the Morning Read is on for you.
• A song that didn’t come out shows up. If a song you asked for in the Audio Playground fails, it appears in Team Radio for you alone, says it didn’t use a song from today’s allowance (since removed, 2026-10-18), and can be removed. If music can’t be made right now, the Playground says so before it takes your request.
• A meeting you booked with the team can put a note on your Board.
• When one thing doesn’t work on a call, that’s what we tell you. If the call itself went through, the follow-up call, text and Board card say one thing on our side didn’t work (or more than one) and that what you said is kept; the call and the card name it in plain words. They no longer say the call broke.
• A resolution note keeps your words. Folder paths are still hidden, but ordinary text with slashes in it, like “sales/support”, stays as you wrote it.
• A new server that can’t be reached stops cleanly. Setup stops, cleans up after itself and says why.

• Audio reads as one room. “Why music?” sits right under the picture of the team, still open, and shorter to read. The section menu stays with you as you scroll. Team Radio and the Audio Playground sit side by side, and your transcripts, the Morning Read and Saturday Night Session sit together underneath.
• Pick any genre. The genre box in the Audio Playground opens to more than 700 genres in 25 families, starting at the one you have. Start typing to narrow it. Type something that isn’t on the list and it becomes your own blend.
• RUSTY’s credits name the model that produced it.
• An order that stopped at “Needs a person” can be finished. The team can close it with a one-line answer and, when there is one, a file. It leaves the Board and shows as Resolved in your request history, with a Download button for the file.
• A teammate who joins a call speaks from their own memory, all the way through. Everything the first teammate noticed is now labeled as theirs in the notes the next one reads.

Fixed

• A message waiting for your coding assistant says so. When your coding assistant is busy, a message from Loam waits in its queue. The card now says the message is waiting in that queue and starts on its own when the assistant is free, instead of saying it wasn’t sent again.
• A busy computer no longer leaves a message stuck. When your computer was working hard, a message between your coding assistant and your Loam chat could stop as if your conversation needed reconnecting. Nothing had been sent, so Loam now tries again on its own.

Added

• Close an order that needed a person, from your session. The team can finish a “Needs a person” order from your editor with a one-line answer and, when there is one, a file from your project.

Changed

• A file attached to a closed order comes from your project. It has to be a file inside your project folder, under 10 MB. If it changes while it’s being read, it isn’t attached.

Fixed

• Connecting your coding assistant finishes where Loam’s helper was first set up as administrator. Connecting could still stop after the coding assistant had your first message, even on 5.5.27. Connect now asks your PC for permission once and finishes. If you choose No on that permission prompt, the card says so and nothing else changes.
• A Board note that says not to call you gets no call. “Hold off on any calls,” “spare me the phone call,” “(no calls please),” “without calling me” and “I’m asking that you don’t call” are now read as no. A note that mentions a missed call, like “not getting a call back is annoying, call me,” still gets its call. If a note says not to call and then asks for a call right now, we call; if it asks for a call later, we don’t, because a Board call can’t be scheduled yet.
• A teammate who joins a callback speaks from their own memory. What the first teammate remembers is now labeled as theirs, so the one who joins doesn’t repeat it as their own.
• New project sites finish setting up with secure access. A new server now waits until secure (https) access is open before it says it’s ready.
• Long calls are processed faster. Checking a long call for the work you asked for no longer slows down on very long transcripts.

Added

• Audio is now the Listening Room. RUSTY, the team’s first single, plays right on the page, with the story of how it was made, the lyrics and a link to hear it on a streaming service.
• Make a song of your own. If Saturday Night Session is on for your account, the Audio Playground turns a genre and a few lines about the song you want into a song in a teammate’s voice. It uses the same six songs a day as your team’s picks; failed songs don’t count, up to 18 tries a day (since removed, 2026-10-18).

Changed

• “Why music?” moved to Audio, and Earlier picks left the team pages. Your past songs are all on Team Radio.

Fixed

• Connecting your coding assistant finishes instead of starting over. If your editor or a terminal on your computer had ever run as administrator, connecting could stop just after the coding assistant got your first message and ask you to connect again, every time. It now finishes connecting. Files left by a different user account on the PC still stop it.
• When connecting stops, the card says why. Once your coding assistant has your message, the card no longer says it isn’t connected. It says what stopped the connection and what to do next.

• When Meg puts you through, they remember you too. A teammate you reach through Meg now comes on with their own memory of you, and can look up anything older while you talk.
• Ask about something from months ago and the team can find it. When a teammate looks something up during your call, they search everything they remember about you, word for word, not only the newest notes. On a call with someone you’ve invited, they search only what they always could.
• An order is read back before anything else happens. If the team can’t build what you asked for yet, they read your order back to you first and ask if that’s everything, so a sentence you hadn’t finished doesn’t become an order that comes back refused.
• Ask for a report or a write-up and you get a document. A report, a doc or a write-up is now taken as a document, and the order is filed under the teammate you were talking to.
• A call that didn’t get going no longer blocks the next one. If a call to the team dropped before it connected, it no longer stops the team from calling you afterwards.

Fixed

• Only your own words are saved as yours. The notes the coding agent adds about the file you have open in your editor, or the text you selected, are no longer saved as something you typed. Neither is the line the coding agent writes when you press Esc to stop a request.
• Two conversations in one folder keep their own place. With more than one coding-agent conversation open in the same folder, one no longer sends lines that were already saved, or loses lines after a save that failed.
• Your coding assistant hears from Loam again. Since September 30, messages Loam sent to your coding assistant while its tab was open didn’t arrive. They now show up in your tab as the conversation’s next turn, where you can see them.
• Your coding-assistant conversation stays yours. Loam doesn’t take it over, so your coding assistant’s tab can write to it, and checking the connection no longer adds anything to it.

Removed

• The last of idle calling. If you had turned on “Auto-call when idle” before it was removed in 5.5.24, the extension still checked in with Loam every minute during a session. It no longer does.

• Whoever picks up remembers you. When a call is handed from one teammate to another, the one who picks up brings their own memory of you.
• Same voices, newer delivery. Carl, Diana, Anthony and Abish keep their own voices, spoken a newer way on calls and in episodes, dramas and the Morning Read. Meg sounds as she always has.
• A note that says don’t call stays a note. Tell the team on a Board card that you don’t want a call, and the teammate answers on the card instead of phoning you.
• A note or a photo link, without the code. On a call the team places to your verified number, you can leave a note for your Board, or get a link to send photos for the teammate to look at, without giving the code and phrase first. Ordering new work still needs them.
• Your side of the editor conversation stays out of call records. When a call or session audio is made from your editor session, what you typed in the conversation is no longer copied into its plain-text record or its title. The team’s replies still are, with the session’s summaries and the transcripts of calls made from it. A moment you write in “Send the Team Something” is not copied either. Session audio you make still keeps its script and recording with the episode, and the script retells the session, including what you typed.
• Passwords and keys Loam recognizes stay out. A line in your editor conversation with the team that Loam recognizes as a password, key or token is left out before the conversation is stored and before anything from it reaches a call. A password written into an ordinary sentence can still get through.
• A teammate who calls on their own knows why. When someone on the team decides to call you, the reason they decided now reaches them on the call.
• Ask for a change on the call that delivers your work. When the team calls to say your work is ready, a change you ask for on that call, after confirming it’s you, is now filed. Until now that call turned it away.
• A confirmation call nobody picks up is tried again too. Fifteen minutes later, the same as one that goes to voicemail.
• An order from your editor that can’t be confirmed says so at once. If the team can’t place the confirmation call to your phone, the order isn’t filed, and the reply tells you why.
• Times are on your clock. When a teammate calls back about a call that went wrong, or about a note on a delivered order, the times and dates they give you follow your own time zone, and so do their quiet hours.
• Songs keep other people’s details out. Before Team Radio writes a song, more of the names, phone numbers and links in what its writer reads are blanked out.
• Asking for a site to come down doesn’t build one. More of the ways people ask for an old site to be taken down are now heard as a takedown, so they aren’t built as a new site.

• Ask for a teammate and you get them. When you ask for someone by name on a call, they come on, say who they are once, and wait for you. No more being passed back and forth.

Fixed

• A call hears only what’s new. When a teammate is on the phone with you, the only things that reach them from your editor are what you and the team wrote after the call started. An earlier conversation that happened to be saved late no longer arrives on the call as if you had just said it.

• The team calls when it has something to say. Any of them, Meg included, can pick up the phone on their own when something is worth your time, at a decent hour where you are. Turn it off in Settings, under Calls from the team.
• Something urgent can still reach you at night. If something went wrong with your work, or a password or key may have leaked, the team can call through quiet hours. A text doesn’t.
• A site that’s built isn’t called a failure. When your site is finished and only putting it online stumbles, the team fixes that first, and your Board says “Built, not online yet.” If the time we gave you is at risk, or the fix runs out of tries, you hear exactly where it stands.
• The front desk knows nothing about you until you’re verified. A number that looks like yours gets courtesy, not your history.
• No more calls because your session went quiet. We don’t ring you because you stepped away from your editor.
• On a trial, the team calls you too. Calls the team starts on its own reach trial accounts the same as everyone else.
• Your Board no longer fills with requests you didn’t make. A voicemail greeting, or the second line of something a teammate said, could land on your Board as a request we’d missed. A call that reaches voicemail or that nobody speaks on leaves nothing there now.
• Meg and the Morning Read sound less rehearsed. Fewer lines they repeat, more of what’s actually true that day.
• Diana, Anthony and Abish sound fuller on the phone again. Their richer, more expressive call voices are back.

Removed

• “Auto-call when idle” is gone. The team no longer calls because your session went quiet. When a teammate calls on their own now, it’s because they have something to tell you.

• Your teammates sound like themselves on the phone. How they open a call, fill a wait and say goodbye is their own and changes from call to call, instead of lines they repeat.
• They know you on every call. What the team keeps about you now makes it onto every call. Before, a busy call could crowd it out.
• What you type reaches the call. When a teammate is on the phone with you and you type in your editor, they get it moments after the team there answers.
• The whole reason for a call gets through. When you or the team set up a call about a long list, the teammate who calls has all of it, not the first part.
• Miss a call asking you to confirm, and we call back. When a teammate calls to confirm something you asked for and you don’t pick up, they try again fifteen minutes later, not during your quiet hours. If they still can’t reach you, they stop calling and the request stays on your Board.
• A call you picked up but didn’t speak on counts as missed. We try again fifteen minutes later, the same as when you don’t answer.
• Three switches in Settings, all yours. One for calls from the team, one for what you type in your editor, and one for typing during a call. Each is on unless you turn it off.

Changed

• The team on the phone knows what you typed. What you type to the team in your editor is now kept with your session, so a teammate on a call, or in your next session, knows what you asked for. You can turn this off in Settings, with the switch for what you type in your editor.

Fixed

• Your own words were not being kept. Until now only the team’s replies were saved from a session, not what you typed.
• Only what you typed counts as yours. Background notices and a session’s opening instructions are no longer saved as if you had typed them.

• Notes on a Board card are a conversation. Your notes and your teammate’s replies stay together on the card, and when you talk about a note, what came of it is written there too.
• A note that asks for a change gets a call. The card’s teammate rings to say they saw your note and proposes one change, and a yes is taken as an order the same way it is on any call.
• That call keeps to your settings. It waits out quiet hours on your own clock, doesn’t ring while you are already on a call, and a note you add during a call gets a call of its own afterward.
• The Morning Read only promises what is really lined up. When a teammate says they will do something, it is an order already under way, a booked meeting or a call about one of your notes, and any other promise is cut before the audio is made.
• Ask us to take down an old website we built for you. On a verified call from your own number, name the one site, hear its address read back, and once you say yes we remove it and any copy of it on the code host.
• Down means checked. We tell you a site is down only after checking from outside that its address no longer answers, and if the site you named isn’t clearly yours or anything is still up, nothing is guessed and a person on the team takes it from there.
• Fewer copies of your work stay on our server. The seven-day cleanup that takes demo sites down now also clears the working copies we made to build and repair your projects.
• Every teammate can do the same things on a call. Carl, Diana, Anthony and Abish each carry the same abilities on every call, including putting a note on your Board and texting you a link to connect a project.
• When we call back about a call, we tell you the real reason. We say something broke on our side only when it did, and otherwise we tell you what you mentioned and ask whether you wanted it as an order.
• Talk is not mistaken for an order. Chatting about the team’s own work, wishing out loud or asking a question no longer brings a call about a missed order.
• Your Board says when that call will really come. The card reads within fifteen minutes, in the morning during quiet hours, or that we can’t call you from here, to match what will actually happen.
• We call back knowing what was said. A teammate who calls you back about a call they were on comes in knowing what was said on it, instead of starting over.
• The team no longer assumes you are a man. On calls and in the notes they keep about you, teammates use your name or they.
• A demo site with an email address on it goes online. A site that showed an email address could finish building and then fail to go online. It publishes now.

Added

• Ask for work from your editor, and confirm it by phone. Tell the team what you need from your session and it goes on your Board, but nothing starts until you say yes on a call to the phone number saved on your account.
• Asking twice files it once. The same request sent again within ten minutes points back to the first one instead of starting a second.
• Some requests still need a call. A request filed from the editor can’t ask for code changes, publishing or deployment, and the reply says what it can ask for.
• Ask what you said on a call. Ask the team in your session what you told them on the phone, and what was said on your recent calls comes back first.

Changed

• Answers reach work already in progress. Your answers to the coding assistant’s questions, and context you send, reach it while it is still working on the task, not after it finishes.
• New tasks wait their turn. A new task waits until the coding assistant finishes the one in hand, and anything sent while it can’t be reached is tried again on its own.

Fixed

• If your coding assistant stops partway through a task, you hear about it once. When the coding assistant closes, crashes or your computer restarts before a task is done, your session is told the task stopped instead of waiting on a result that isn’t coming.
• A finished task is reported as finished. When the coding assistant has finished a task, your session hears that it finished, including tasks it has since archived.

• Ask for a change on a delivery call and it gets made. When a teammate calls about finished work and you ask for changes to it, your changes go on that work instead of sitting on your Board as notes. If part of what you ask is something we can’t do on a call, the part we can do still goes ahead.
• Songs in any style. The mood a teammate is in now picks the kind of music for your Team Radio song, from any genre. What they like to listen to shapes how it’s played, not which kind it is.

Changed

• Shared session instructions are editable in Templates. Administrators can update the launch text and shared guidance in one place.
• Session starts keep a dependable fallback. Start Session, Meet the Team and Build Mode use the current launch text, with the built-in instructions available if it cannot be loaded.

• Team Radio. Ask anyone on the team for a song from their page on Team, and a few minutes later there is one waiting for you. Each song is new and made just for you: the teammate’s mood that day sets the feeling, and they sing it in their own voice, with another teammate on a verse.
• Your songs play as one playlist. Open Audio and press play for everything the team has made you, or pick one teammate’s station. Take a song out of the rotation and it isn’t deleted; put it back whenever you like. Any song downloads as an MP3, and as a WAV a few minutes later.
• Your private details stay out of the writing. Before a teammate writes your song, names from your work and your contact details are taken out of what they read.
• Songs come with Saturday Night Session. Your administrator turns it on for your account. There’s a daily limit (since removed, 2026-10-18), and a song that doesn’t finish doesn’t count toward it.

Changed

• Your session audio has a home again. Open Audio to search your sessions, play one in the browser, or download the MP3. The email that says your audio is ready now takes you straight there.
• A darker, wider workspace. Home, Work, Team, Audio and Settings use the full width of your screen, in the same dark forest colors as the extension.
• One thing plays at a time. Start the Morning Read and the session you were hearing stops, wherever it was playing.
• Saturday Night is made by your administrator. It still arrives by email when it is on for your account.

Fixed

• Turn on follow-on work answers the first time. Right after you hand your coding assistant a task, the button no longer tells you it isn’t connected. It waits for the check already under way and answers from it.
• The button for connecting your code host is easy to find. It now looks like the button beside it for connecting your work email.

Added

• When one of us calls you, we know where things stand. Ask whether something is live yet and we look at the session you called from before we answer. If there is no session behind the call, we say so instead of guessing.
• Meg hands you the code-host link on the call. If a project needs connecting, Meg offers the setup link while you are still on the phone, and she can tell you which projects are already connected.

Fixed

• Your coding agent’s settings are saved whole. When Loam tidies up after the old installer, it writes your settings file completely or not at all, so an interruption can no longer leave it empty.
• A photo we cannot open no longer loses your request. If a picture in your email does not come through, we tell you, and the rest of your email still reaches the team.
• If our reply fails, we say that plainly. And if your request is already on the Board, we tell you that too, so you don’t need to send it twice.
• Plainer notes when a change cannot be prepared. The note you get says what happened in ordinary words.
• The day-before email for a demo site goes out on time. Even when the site’s server is having a bad day.

Added

• Email a teammate a photo and they see it. Send Anthony, or anyone on the team, a picture and the reply shows they looked, in their own voice. Replies use your own key from Settings.

Fixed

• Your coding assistant stays connected. A slow moment no longer switches it off. It keeps its connection and checks again on its own.
• Reloading your editor keeps your chat paired. After a reload, Loam still knows which chat is working with your coding assistant, so there is nothing to reconnect.
• Each turn is saved once. Computers that once used the old installer were saving every turn twice. Loam now tidies that up by itself.

Changed

• Home tells you where you left off, in plain words. The card that shows your last thread now reads like a sentence, not a work log.
• A new look in the extension store. The Loam page shows the team and says what Loam does, plainly.

Changed

• Demo sites last a week. We email you the day before one comes down. Want to keep it? Ask us to make it a project. Sites on your own code host stay up.
• Old links land somewhere friendly. An expired preview or download link now shows you the team and a way back, not an error.
• Settings is easier to find your way around. Connections, publishing and security each have their own place.
• We ask before we take an order. When one of us calls you, nothing becomes an order until you say yes.

Fixed

• Open Loam opens properly the first time. It waits until it is ready, then opens its own window. If that takes a moment, it opens in a tab instead of a blank window.
• Paused means paused. If you pause your coding assistant, we say so and show you how to pick back up.

Fixed

• Connecting your coding assistant leaves the rest of your PATH as it was. When Loam adds the coding assistant’s folder to your PC’s PATH, your other entries keep references such as %USERPROFILE% and the PATH keeps its type. Before, those entries were rewritten as fixed folder paths.
• Repositories you add on your code host later keep their real branch. A repository you add to Loam on your code host after connecting is now worked on its own default branch. Before, the team assumed main.
• The install command checks who signed the installer. The one-line install command in Settings runs the installer only when it is signed by the publisher of Loam and its fingerprint matches.

Changed

• A team member’s story reads like a person, not a process. Open a member from the Team page and you get how they are right now and who they have become, in their own words. The lists of saved notes and open threads that used to follow are gone. The temperature now shows their state and when it was written.

Fixed

• The coding-assistant card tells you which conversation your task went to. It used to say only that the task was sent. It now names the conversation, so you can find it again. When it cannot read the name it says exactly what it said before rather than guessing.
• A docs folder you can link is a docs folder you can unlink. Build Mode accepted a folder with no milestone plan and then left you no way to change it. Clear now sits beside Browse on the folder row whenever a folder is linked. It asks twice, because clearing also ends the current session.
• Saturday Night says where episode direction comes from. Direction is set for the whole account now. Anyone who used to write suggestions there sees one line saying so, instead of the space where the panel used to be.
• Two messages stopped talking like a machine. When the team’s moments can’t be rebuilt, the message now says what happened and what to do next, in plain words. The voice-verification notice says “after three tries”.

Fixed

• An old session is no longer shown as active. Opening a project reported the last session as running, clock and all. The panel now says Active only for a session that window started, and otherwise says plainly that Loam cannot see whether that session is still open.

Fixed

• Once your coding assistant is connected, the setup window says only that. The line saying the assistant and your chat were still confirming used to stay underneath.

Added

• Screenshots and files go with a task. In Hand off a task, paste a screenshot into the task or choose Attach files. Your coding assistant opens them on your computer.

Fixed

• No window opens for the helper. On some PCs, connecting could open a system-shell window, and closing it stopped the connection. The helper now runs without a window.
• You choose the project in the coding-assistant window. It used to be a plain list at the top of your editor.
• The first screen says what you need. Start a Loam session first, and have your coding assistant’s extension installed and signed in. The steps explain its own welcome screens and why any word connects it.
• You can tell when it connects. A notice appears once, and the coding-assistant card marks the moment. The confirming step says you can close it.
• Settings agrees with the card. It says Connected, Paused or Connecting, and how long a connection lasts.
• Follow-on work comes with an example and says how long it lasts.
• Testing the connection shows it is working. The line counts the seconds until both sides answer.
• Moving Loam to its own window says where your chat is.

Changed

• Installing from Settings is one command. It checks Loam’s signature and the file’s fingerprint and runs the installer only if both match. The copy box says Copied.

Fixed

• Follow-on work is set up in the coding-assistant window. Turning on follow-on work for your coding assistant used to open two plain pop-up boxes. You now write what it may pick up in the coding-assistant dialog and choose Turn on follow-on work.
• Follow-on work stays quiet. With it on, Loam used to post a connection check into your chat and into your coding assistant every four minutes. It now checks only when you connect or choose Test the connection.
• The session line says it once. The compact sidebar said “session” twice. It now reads Active, Not running or Unavailable under Current session.

Changed

• Setup instructions match what you see. The extension store page and the public pages describe connecting as it works now: connect, send any word, Connected.

Fixed

• The coding-assistant card says whether your coding assistant is connected. It used to offer to connect even after you had connected. It now reads Not connected, Connecting, Connected or Paused, says the one thing to do next, and shows your latest task as it goes: sent, received, being worked on, back, being reviewed.
• Connected stays connected. A connection used to lapse after five minutes, so a task you asked for a little later was refused. It now lasts for the Loam session. If the coding assistant does not pick a task up, the card says so.
• Connecting happens where you are looking. The one step — send your coding assistant any word — now appears in its tab and on the card, not only behind you in the Loam window. A new session no longer asks you to “reconnect” something you hadn’t connected.
• Handing off a task is a button on the card. It opens a short form instead of three pop-up boxes. Asking Loam in your chat — “Have the coding assistant check…” — works too, and the guide now starts there.
• The helper is asked for once, in the same window. It used to be a plain pop-up that asked again every session.
• What your coding assistant sends back reads like a message. Collaboration messages in your chat open with one plain line, and Loam tells you what came back instead of pasting it.

Fixed

• Checking readiness waits for the answer. The check used to come back “Waiting for test reply” and stay there even after both conversations had answered. It waits now, and a later answer still reaches the panel.
• Collaboration works whichever Loam address you connected under. Loam answers at two web addresses. A connection made under one of them was refused from a surface using the other, as though it belonged to a different account. Same account, same connection, either address.
• A refusal now tells you what went wrong. Every refusal used to read the same way and point at the connection, whatever the real reason was.

Fixed

• Connecting your coding assistant works on a machine that has only its extension. The coding assistant’s command-line tool ships inside that extension and is not somewhere your computer looks for it, so nothing could find it. Loam puts it where it can be found when you connect, and tells you it did.

Fixed

• Connecting your coding assistant opens a new conversation with it for you. It used to list your old conversations and ask you to pick one. Now it opens a fresh one; you send it a word and the two are connected.

• The Code Review card fills in as soon as the workspace opens. It used to sit at dashes in a window that opened without the sidebar.
• Dropdowns and text fields show all of their text. Fields on the workspace pages carried a height meant for the compact sidebar and clipped what you selected or typed.
• Refresh answers. The button tells you it is refreshing and when the reading came back, and a click during an automatic refresh is no longer dropped.
• Choosing a coding-assistant conversation is a list, not a form. Loam finds the conversations you have open in this project instead of asking you for an identifier.

• Loam's connection check reaches your session. It now arrives in your coding-agent conversation whether or not that conversation skips permission prompts. Nothing to approve, nothing to switch.
• Connecting your coding assistant opens to one button. Until a conversation is paired you see the explanation and the Connect button, nothing else. Every control in the dialog now tells you what it did.
• Re-installing the helper leaves nothing behind. The previous helper is stopped before the new one starts.
• Connecting your coding assistant keeps working when the coding agent updates.

• Connecting your coding assistant tells you when the coding agent is waiting on you. When your coding-agent session skips permission prompts, it asks you to approve Loam's connection check. The panel now says so and gives you the five-minute window, instead of reporting the check unavailable with no reason.

• Connecting your coding assistant installs its helper on a stock PC. First-use setup stopped partway and installed nothing. Fixed; nothing else changed.

• The Loam workspace. Your team, the current session, the build plan and the project record in one window, with a compact sidebar in the activity bar. The team photograph, portraits, and the site’s forest, sage and terracotta.
• Every existing control kept. Start Session, Build Mode with scheduling and episodes, reviews and audits, debugging, team calls and Call the Shop, recordings and transcripts, feedback, memory sweeps, indexing and settings, each on its own page.
• Optional coding-assistant collaboration. Off by default. Explicit setup, one task at a time, Loam keeps review and deployment. Task history lives in your user profile on your PC and is removed only when you ask for that.
• Phone repairs, stated plainly. Bounded repairs to registered projects are available. Saved to your project and proven live are reported as two facts.

• Your project’s coding-agent settings are written whole or not at all. A crash, or two changes at once, can no longer leave them unreadable, which could quietly switch off your own ask and deny rules.

• The install steps live in one place. The separate install guide page is gone. Everything it covered is in Settings beside your IDE API key, including what to do when a company policy blocks the installer outright and how to install from the extension store instead, which runs no script.

• Calling the team no longer starts an order you did not ask for. When you rang a team member yourself, the call opened with verification and an attempt to write down a job, every time. A team member now only asks for that when there is actually something to order, whoever placed the call.
• Ask for Carl and Carl picks up. Asking to be passed to one person could put a different one on the line, introducing themselves under the name you asked for. Each person now answers only their own line, and a request for someone else walks you back to whoever you were already speaking to. The first sentence you hear names who has taken the call.
• A hiccup at your code host no longer undoes a change that worked. When Loam checks back on a repair it published, a momentary problem at your code host is no longer reported as a failed repair, and Loam waits for your own checks to start before it reports.

• A team member calling you only verifies when there is something to order. Until there is, nothing is sent and nothing is asked. A dev meeting callback still creates and changes orders as before.
• If you use push approval, a team member’s call sends the push. It used to text a code and read a phrase to you even when your handset was enrolled. Signing up for push approval is still handled at the front desk.
• Every call that earns a recap keeps one. Some calls finished without their notes being written down, and a call with nothing recorded now says so plainly instead of going quiet.

• Any team member on your call can send you a photo link and see what arrives. Carl, Diana, Anthony and Abish now do what Meg does: text you a single-use link to send photos during the call, then look at what came through. Each photo is read once, and anything they say about it comes from that read.
• Four photos don’t become forty observations. The person you’re talking to reacts to what you sent the way a person would, and gives the full description when you ask what something is. If a photo can’t be read, that’s the first thing you hear.
• No dead air while a photo is read. A read takes around eight to thirteen seconds, and the team member now tells you they’re taking a look instead of going silent.
• A link that fails to send doesn’t leave you stuck. If the failure might clear, you’re asked whether to try again. If the link can’t be sent on this call at all, you’re told so plainly, and the rest of the call carries on.
• A change to a dev meeting is written into its plan. When you amend a dev meeting whose folder has already landed, your confirmed words are added under an Amendments heading in that folder’s plan. The meeting isn’t run again and nothing else is rebuilt.

• The team member who calls you can take a new order. On the calls they place, Carl, Diana, Anthony and Abish verify you with a text code and an emailed phrase, then take and confirm an order just as Meg does.
• A dev meeting lands its folder in the right project. Name a project that isn’t registered, or two at once, and you’re told by name instead of the folder going somewhere else.
• Dev meetings join the work you can change by phone.

• Trust Mode is gone from Settings. There is no Full Autonomy or Supervised choice any more. The extension always pre-approves Loam’s own tools, git, and the JavaScript package and runtime commands in the project’s coding-agent settings; everything else follows your coding-agent settings. An ask rule gets you asked first and a deny rule blocks the command — both override Loam’s approval.
• Your own allow rules are kept. Choosing Supervised used to replace the project’s whole permission list. The extension now only adds its rules and doesn’t remove yours.

• Your orders are encrypted at rest. Order text, delivery receipts, sender addresses, intake and backlog records, report files, photos and email attachments are stored encrypted.
• Deleting your account deletes its reports, along with its order intake and backlog records.
• A callback you’re still on isn’t reported as failed. A long walkthrough call no longer shows a failure notice while you’re still talking.
• Turning Build Mode off stops pushes. The milestone in progress finishes, and nothing after it is pushed. The public pages now say so.

• The public pages say what the product does. What they say about deletion, encryption, provenance, permissions, install and price was checked against the product and corrected where it wasn’t true.

• Ask for a dev meeting by phone. Describe a change you’re weighing. The team reads the project and deliberates, and you get a meeting report with the verdict, the scope of work and the plan. When the verdict is go and you’ve given the team write access, the project folder is saved into your repository as well.
• Then we walk you through it. A team member calls at the time you named and goes through the plan section by section.

• Quiet hours are your switch. A new account setting, on by default, holds calls and texts outside normal hours. Turn it off and the team can reach you at any hour. Only you can change it.
• “Now” means now. Ask for a call right now, or as soon as possible, and it’s booked for the next few minutes instead of asking you for an exact time.
• Meg can move a call you’ve booked.

• Email the team the way you’d email a person. “Give us a call” gets you a call. Times typed the way people type them work: “9pm est”, “tonight at 9”, “Wednesday at 9pm”, “in 1 hour”, a date with a slash. Replies come from the team member you wrote to, in their own voice.

• Meetings booked by email work with or without a connected calendar. With nothing connected, the team sends the invite from its own mailbox. With a work-email calendar connected and selected, the meeting goes on your calendar with you as the organizer.

• The team emails you from its own mailboxes. Deliveries and replies come from the work mailbox of the team member sending them, and replying reaches that person.
• Send a request by email. Write to any of the five team mailboxes. The sender and the account are checked, and a supported request enters the same order system as a phone call. Attachments and links are kept.
• One email design for everything we send. Its masthead is an image, so it doesn’t turn unreadable in a mail app’s dark mode.

• A note on the board sends a stuck order back to work. Write the correction on the stuck item, and the order runs again with your note as the correction. If it can’t run again, the note is kept and you’re told why in one sentence.

• Behind-the-scenes reliability fixes.

• “Give the team a moment” picks from a curated set. A blank click picks one of the moments in the set, and doesn’t quietly repeat one once they’ve all been used.
• Administrators can refresh the set in one go. They can ask for 30 new moments, seven for each teammate and two for the whole team, watch progress, and see the history of edits and deliveries. The current set stays in place if the new one doesn’t pass.
• An automatic moment doesn’t repeat within your account, across the whole team. Moments written on purpose are exempt.
• Moments aren’t lost. A moment that’s waiting is delivered, even across a restart.

• The public site is lighter and easier to navigate. Pages work better from the keyboard, the login page puts the form first on a phone, images load faster, and background sound waits until you turn it on.
• The extension store listing states the operating boundaries. It separates the free extension, the USD $499-per-user monthly service, and customer-controlled provider costs; describes bounded memory and deletion behavior; preserves Meg’s shipped pickup, “Loam, front desk — this is Meg.”; and discloses that a configured, linked Build Mode project may push after milestone completion without another prompt for each push.
• Behind-the-scenes improvements to how the public site is served and secured.

• The Outside View. Beside every delivered code review, a separate short deck on what the public record says about the product and the company behind it. It arrives in its own email and says on its face that it’s separate from the review and that nothing in it is endorsed.
• Meg knows you once you’re verified. After verification, she has your caller file, her own recent days and the team’s recent work for your account, so a call picks up where the last one left off. Before verification, a caller gets the front desk and nothing from the account.

• Code reviews arrive as a finished report package. A research paper about your application comes as a PDF and HTML package, and every finding names the file and line range it came from.
• A layout flaw can’t hold back a finished report. The report ships with the flaw disclosed instead of waiting.

• Your yes on a callback locks the order. An order confirmed on a call the team placed is locked in the same way as one confirmed with Meg.
• A code review names exactly what it read. The report is tied to the exact version of the code it reviewed, and it states its coverage as a fraction you can check.

• Photos you send are actually looked at. Each photo is read once, and the result is tied to that exact file. Nothing is said about a photo that the read didn’t show, and a photo that can’t be read is named as unread.
• Phone photos in HEIC format are accepted everywhere a photo is.

• Your words are captured first. When a request could mean more than one thing, you’re asked one question with a short set of answers instead of getting a guess.
• Saying it again changes the order, not the count. Restate an order in different words and that order is updated. No second order is created.

• Send photos during a call. Meg texts you a single-use link that expires. The page is built for a phone held in one hand in bright sun: it shows the expiry as a clock time in your time zone, and a file that’s too big gets a sentence naming it and its real size. Up to 8 photos, 25 MB each.
• Photos don’t live forever. Call photos are deleted after 90 days.
• No open-ended waits on a call. Every step that runs while you’re on the line has a time limit, so a slow answer can’t hold the call hostage.

• Push approval for verification. If your account uses push approval, approve a push instead of reading back an emailed phrase. Meg can set you up on the call: she asks your city for your time zone, records your consent, and texts the setup link.
• Connect your code host by phone. Meg walks you through installing Loam’s app on your code host, and your project is registered once the installation is confirmed.
• Security & Access. A signed-in page where you can change your registered phone, re-arm push approval, or remove it.
• Change delivered work by phone. Ask for a revision on a call. It’s read back before anything changes.
• Websites by phone. A multi-page website arrives as a zip with a seven-day preview link that opens the whole site.
• Photos you send are attached to the order they belong to.

• Order work by phone, get it in your inbox. Documents (word-processor file or PDF), slide decks, spreadsheets (spreadsheet file or CSV), laid-out email drafts, calendar files and web pages. Each order is read back with what “done” means before you say yes.
• Ask for a call back. The team calls at the time you name. If it can’t reach you, it tells you why, and a missed call is reported as missed.
• Say an idea out loud and it lands on your board, scoped, with the places in your code it would touch.
• Work that fails a check goes back for rework and runs again instead of stalling.

• Meg answers the phone. “Loam, front desk — this is Meg.” She verifies every caller with a text code to the registered phone plus a second step, and doesn’t see the codes herself.
• Ask for Carl, Diana, Anthony or Abish and a verified caller is put through. The team member arrives already knowing your recent work.
• Orders are confirmed on the call, and a verified caller can leave a note for the team’s board.

• The sidebar follows your editor’s theme again. Since v5.4.89 the panel carried its own fixed cream-and-ink palette, so a dark editor sat beside a bright panel all day. It now takes its colors from whatever theme your editor is running — dark on a dark theme, light on a light one — while keeping the Loam mark and the team photo. Every label, input, button and status color was re-checked for contrast on both themes.

• The sidebar is back to its previous look. Two same-day attempts at fixing sidebar eye strain (v5.4.92, v5.4.93) didn't land the way we wanted, so we reverted rather than keep iterating live. More on this soon.

• The sidebar photo was too bright to sit with. The team photo is now shaded evenly, top to bottom, in the same tone the rest of Loam uses.

• The install docs now lead with loam.team. The Get Started and IT pages give loam.team as the address to download and install from — the same signed installer, the same published hash. The network guidance for IT now lists both loam.team and docpro.cloud, because existing installs still talk to the original address and nothing about them needs to change.
• The Manage Memory confirmation panel is readable again. The panel that asks before touching the team’s memory had drifted illegible; it now sits on the same warm canvas as the rest of the sidebar, with text you can actually read before you click.
• Sharper pages. A contrast pass on the marketing pages brought every flagged link and label up to WCAG AA.

• The installer’s signature is provable end to end again. The installer we serve had been changed after it was signed, so checking it the way our docs describe wouldn’t have come back clean. It’s re-signed, and the published fingerprint matches the file we serve.
• loam.team is a trusted update host. Updates from loam.team were being refused because the address hadn’t been added to the extension’s list of trusted update hosts. It’s on the list now.

• The sidebar wears Loam now. The panel you work in was still dressed for the old name — the old name’s mark over the team photo, and a black theme borrowed from the editor. The hero now carries the Loam seedling and wordmark, and the whole panel sits on Loam’s warm canvas with dark, readable text — the same ground as loam.team. Every button, banner, and status dot moved to the brand palette, and every color pairing was checked against WCAG AA contrast before it shipped.

• The “no update available” message no longer tells you to run the command you just ran. Running Loam: Update Extension when nothing was pending answered with “Run ‘Loam: Update Extension’ first” — the very command you were in. It now says what’s actually true: you’re on the latest version, and Loam checks for updates automatically when your editor starts.

• Loam’s public links now point to loam.team. The extension store listing and the paused-screen “add your key” links follow the product to its new home at loam.team. Nothing about how the extension connects to your server changed — only where the public pages live.

• The extension store icon no longer arrives on a cream tile. The 5.4.85 seedling mark shipped on an opaque cream background that sat as an ugly square on the extension store’s light listing page. The icon is transparent now, so the mark sits cleanly on whatever is behind it — light or dark.

• New name: Loam. The product you already use is now called Loam — same team, same memory, same work. Carl, Diana, Anthony, and Abish still remember your architecture decisions, your review history, and where you left off. Only the name and the mark have changed. Your existing install updates in place — nothing to reinstall, nothing to reconnect.

• Start Session and Meet the Team explain a paused team like everywhere else. They were the last two places that didn’t. Start Session could still read “Connected” after the team had paused. Both now say the same sentence as the rest of the product, and the paused banner catches up immediately.

• A website address that arrives with a repo is not yours, and Loam no longer treats it as though it were. Loam now uses only a site you set up on this machine, and says so plainly when it skips one, with how to make it yours again. A repo you cloned can no longer put its own website on your review schedule.
• When Loam can’t tell whose declaration it is, it stops — and tells you it stopped. A slow or synced folder used to be enough to switch a working site off silently. It now says so, explains that the next open usually picks it up, and tells you what it means if the line keeps coming back.
• Run Code Review and Start Build explain a paused team like everywhere else. Both used to answer with a line of raw machine output. They now say the same sentence as the rest of the product, and the paused banner catches up immediately.
• Opening a folder registers your site once, not twice.

• Point Diana at your site once, and she watches it from then on. Open a folder with a website in it and tell Loam where that site is published. From then on she reviews the live pages herself, on her own schedule. If she finds something worth your time she calls; if she doesn’t, she stays quiet, which is most of the time and entirely the point.
• A site you found nothing to say about is a site nobody bothers you about. Opening a folder with no website in it registers nothing at all, and a website with no published address registers nothing either — Loam tells you what to add instead of guessing at a URL.
• The same site stays the same site, wherever you opened it from. Diana knows a site by its repository, not by the folder on your disk. Clone it to another machine and she picks up where she left off rather than starting over.
• The team only visits public sites. Loam won’t point its browser at anything that isn’t a public site, even if a page tries to send it somewhere else.

• A paused team no longer calls you. When a trial ends without your own key the team pauses — but it could still ring your phone. Idle check-ins and scheduled meetings kept dialing accounts the product had already paused everywhere else. They don’t anymore. Paused means paused, on the phone too.
• Asking a paused team to call now explains itself. Clicking Call Team while paused reported that the call failed. It hadn’t failed — the team is paused. It now answers with the same sentence as everywhere else, and the one action that brings them back.
• A scheduled meeting that can’t happen says why. A meeting booked on a paused account used to simply not occur. It’s now marked missed with the reason, so nobody is left wondering whether the team forgot.

• When a trial ends without your own key, the team pauses — and says so everywhere. Before, sessions kept running while nothing the team learned was saved for the next one. Now the sidebar says “Your team is paused — trial ended,” the Start Session button waits with it, and anything you reach for answers with the one sentence that matters — add your key and pick up where you left off.
• Nothing is lost while paused. Your team’s memory, your projects, and your history all keep. Add your key in Settings and everything resumes on the next request — no restart, no reinstall.

• Your team now tells you when it’s running degraded. If your account has no key of its own and no active trial, the Team page, every member’s record page, and the sidebar in your editor say so plainly — “Your team is running degraded.” — with the one action that fixes it. Before, sessions ran and looked normal while nothing new the team learned was being kept for the next one.
• What your key covers is now honest. During a trial, Loam’s key carries your team’s memory work. After the trial it runs on your own key — and if there isn’t one, that work pauses and the banner says so, instead of quietly running anyway.
• Trial-ending emails now actually send. The heads-up email meant to arrive three days before a trial ends hadn’t been going out since the feature shipped. Fixed: expiring trials get the warning.
• Your own key now covers you if the platform key has a problem. A trial user who had saved their own key could still be locked out when the platform key failed. Your key now takes over instead.

• The Call Team panel gives a call more time to connect. When you request a call, the panel now waits up to 45 minutes for it to go through before telling you it couldn't — up from 15. Reading you in fully can take a while, and the panel would rather keep waiting than cut a real call short and say it didn’t go out.

• Sessions launched from the Loam panel could fail to start. Clicking Start Session opened a tab that worked for about a minute and then shut down with an error blaming your authentication and your network — both of which were fine. When it hit, it hit every session type, including Code Review. Sessions now start reliably, and that error goes with them.
• A call requested before a session was open now arrives once the session is ready. Clicking Call Team in a folder with no session running holds your request and delivers it the moment the new session is up — a short wait and the phone rings, instead of the request being lost.

• Opening a second tab right after starting a session could hand your call to it. For about two minutes after a session started, a second coding-agent tab in the same folder could take over answering your calls. Now the tab your session started in keeps the line.
• The write-up that arrives after a call now says what it is. When a call ends and the conversation lands back in your session, it used to arrive under the heading “incoming call context” — easy to misread, and backwards for a call you placed yourself. It's now labeled plainly: “Call transcript.”
• Handled call requests no longer pile up. Requests that were already answered, or expired long ago, are now cleared away automatically.

• A call could go unanswered if you'd had another session open in the same folder earlier. You'd click Call Team and see “the session didn't answer,” even though everything was set up right. An old session can no longer block a new call.

• The team could go quiet mid-call and lose the thread of what you were saying. What you said while still on the phone could fail to reach the team until you hung up. The team now stays with you for the whole call, the same way it already did on Meet the Team calls.

• The team didn't follow up after a call ended. Your conversation was being recorded correctly the whole time, but nothing brought it back into view once you hung up. The team now picks up where the call left off as soon as it ends.

• A window reload could still hand your call to the wrong tab. Right after the coding agent restarted, the wrong tab could answer for your session. Now only the tab actually running your session answers.

• A call could be answered by a tab that had nothing to do with it. With more than one coding-agent window open, a window working on something unrelated could pick up your call request. Now only the session that asked for the call answers it.
• When something goes wrong with a call request, you hear about it. Your session now says who’s asking and why, and says so out loud if anything is wrong.
• The call panel is honest about how long it's taking. “Asking Anthony to call you” now names who's being asked. If nothing happens for 15 minutes, the panel stops waiting and tells you the call didn’t go out, with a Try again.

• Call Team works the first time you click it. On a freshly opened window, a click could go nowhere and the panel couldn’t tell you why. The button now works from the moment it’s ready.
• A call the panel had already given up on could still ring your phone later. Starting a new session could set off a call you’d already been told had failed. A request now expires when the panel says it has failed.

• Call Team now hands the call to your live session. Clicking Call Team asks the coding-agent session in your open folder to make the call, so the team member who calls already knows who you are and what you've been working on. The coding agent needs to be open in the folder for the call to go out; if it isn't, the panel says so plainly and offers a Try again button.
• The call panel now tells you exactly where your call is. In place of the old one-line “Connecting…” status, the panel tells you each stage in plain sentences — asking the team, reading up on you, calling you now, on the call with a running clock, writing it up, logged. Every stuck state offers a way to try again, and if the panel loses track of a call, it says so and points you at the call log.
• Automatic session logging works. It had been quietly skipping its work. It now runs, with nothing stored in your repository. Learning-active sessions can add selected entries; not every turn becomes memory.
• The Call Team button can’t start a second call on top of a live one. It stays off while a call is in progress — including long calls — and comes back once the call has ended or failed.

• Trust Mode now tells you when it takes effect. Switching Trust Mode applies to your next coding-agent session, not the one you're already in — the Settings panel and the Full Autonomy confirmation dialog now say so, so it's clear the change saved even though your current session keeps its current permission mode until you start a new one.

• The sidebar section explains why, not just what. It no longer opens with the feature's old name — the heading and copy now say plainly what it's for: telling the team specifically what landed, because that's what shapes how they work with you next. The example text is a real, generic example instead of a scripted scene.
• A moment you write can be remembered. It can be saved for that team member and brought up later when it matters. Surprise moments aren’t saved as something you did.

• Write your own moment for Tip the Team. A box to write the scene yourself now sits above the button — one detail, present tense — instead of only drawing from a pool. Aim it at one team member with the “For” picker, or leave it on “Anyone” and let the room decide who it lands on.
• “Surprise the team” writes something new. It no longer draws from a fixed list — it writes a fresh moment for you, and you don’t get the same one twice.
• The original built-in scenes are now a backup, not the main event. They only appear if a fresh moment can't be put together, and only ones you haven't already received.

• Tip the Team fine print now describes the delivery. The note under the button says when your moment arrives and that it’s played once, instead of pointing at a different feature.

• Tip the Team now says what it is. The sidebar section explains itself before you click: a tip here is a moment, not money — a written scene the team steps into during your current session. The button now reads “Give the team a moment,” and the fine print points anyone looking for show tips to Saturday Night under Audio in the web app.
• The built-in moments got a quiet edit. A handful of the pre-written scenes implied a cash gift from you. They’ve been rewritten to keep the sentiment and drop the money — the team doesn’t say you paid them.
• Admin tip reset restores the full set. “Reset Defaults” in the admin panel previously restored only 10 of the 30 built-in scenes; it now restores all 30.

• The team now schedules meetings — and places the calls itself. Ask the team to set up a call and a real calendar invite lands in the guest’s inbox, with Accept and Decline that work right inside the guest’s email. At the scheduled time, the team dials the meeting on its own, agenda in hand. Afterward, a recap email goes out covering what was discussed, what was decided, and who owns what.
• Commitments follow up on themselves. Anything promised on a meeting becomes a tracked deliverable. Open items get a text-message and email nudge — respectful of quiet hours — until they’re handled, and you can mark one done right from a session by quoting its wording. The follow-up doesn’t forget, because forgetting is the thing this product exists to kill.
• Things said on a call can carry forward. Relevant details from a phone call can come back in later calls and sessions. Not every detail does.
• A rebuilt live-call voice. Teammates can look things up during a call and answer with current information.
• Sessions start with your history. Opening a brand-new or empty folder could start a session without the team’s project history. Sessions now open with it, and the team reads its whole briefing before it replies.
• Bundled Loam tools updated (1.10.8 → 1.12.2). Send meeting invites and mark meeting deliverables done from your session, clearer help when a project lookup comes up empty, and session learnings save again after a caller-history lookup.

• Response Style now mirrors the coding agent's built-in output styles. The sidebar's Response Style control lists Default, Proactive, Explanatory, and Learning — the actual styles the coding agent ships — and choosing one applies it to your workspace on your next session. The earlier list included a “Concise” option that the coding agent has no equivalent for, so it did nothing; it’s been removed. Default is the standard style; Explanatory and Learning add inline insights (Learning also leaves you TODO markers); Proactive acts more autonomously.

• The Start Session picker got a real redesign. Choosing what kind of session to start now uses a cleaner, icon-led selector — each session type carries its own icon and a clear selected state, so the type you're about to begin is obvious at a glance. It's fully keyboard- and screen-reader-navigable, and it adapts to your editor's theme, including light and high-contrast. The list shows the session types an authorized Loam administrator has enabled, with the configured names, and falls back to the standard set if it can't reach the server.

• Loam administrators can configure the Start Session list. Which session types appear in the sidebar's Start Session picker — and what each one is named — is set from the Loam admin panel, so the list can be updated without an extension release. Organizational customer-admin controls are not shipped today; the default set is unchanged.

• The code-review completeness guard is more reliable. Something left over from an earlier session can no longer let a code review close while findings are still open. Completes the review-ledger check from v5.4.58.

• The sidebar now warns when a review ledger total looks wrong. When the open-finding count doesn’t match what the ledger says remains, a warning appears, so a damaged ledger can’t read as clean. A review session can’t be closed until the ledger is corrected.

• The team's tools no longer go missing after an update. An update could leave the whole Loam tool set missing until a reinstall. Updates now bring the tools back complete. A “Reload Now” prompt still appears when they change.

• Security and stability hardening. Tighter handling of your workspace files and call status, updated dependencies, and the same version number shown everywhere.

• New tools show up right after the extension auto-updates. When Loam refreshes through the extension store, the team's available tools now update alongside it — with a "Reload Now" prompt when tools change, so you can pick them up immediately instead of re-running the installer.

• You can switch Trust Mode back to Supervised again. Choosing Supervised from the Trust Mode dropdown now re-imposes the coding agent's permission prompts after you'd turned on Full Autonomy. Previously the dropdown could flip back to Full Autonomy on its own, with no way to undo it short of editing settings by hand. Switching now works in both directions and sticks.

• Detailed response style repairs itself no matter how it was stored. If a project had the Detailed style saved with unusual capitalization, the sidebar would show Detailed while the team quietly kept answering in the standard style. Opening the project now corrects the setting, so what the dropdown shows matches how the team answers.

• Response Style now actually changes how the team responds. Choosing Detailed turns on the richer, explanatory answers — the ones with inline insight callouts that walk through the reasoning behind a change — instead of doing nothing. Normal and Concise return to the standard style. Open a project already set to Detailed and the dropdown now shows Detailed to match.

• Pasted screenshots no longer go missing when you start a session. If you pasted images in more than one place — say the Meet the Team Context box and a regular session — starting one could quietly delete the other set. Your attached screenshots now stay put no matter which session you launch.

• Attach a screenshot to a Meet the Team session. Paste an image straight into the Context box and it travels with your session, so the team can see what you're looking at before the conversation starts.

• Call records stay continuous for the full call. The record no longer shows a gap while a team member is on the phone.
• Team photo refreshed to the current June 2026 team in the sidebar hero.

• Updated credentials take effect within seconds. Project context, server setup and deploys pick up updated credentials within seconds instead of needing a restart.
• Reliability fixes behind Meet the Team — call setup, session-history lookup, and Code Health gauge timing on same-day audits.

• Meet the Team remembers your guests. The team now recognizes someone who has called before instead of starting cold every time — and matches returning guests by phone number, so they're recognized even when their name is entered differently than last time.

• Meet the Team section reorganized. Title first, then a one-line description — "A live agent session with the team over a voice channel." — then the artwork, then the form. The section reads top-down: what it is, what it does, how to start it.

• The animated artwork now sits on a full-width black banner. It spans the section edge to edge and the artwork blends in seamlessly on every theme.

• Solid backing added behind the Meet the Team artwork. Superseded same-day by v5.4.40's full-width banner.

• Animated Clarity brain artwork headlines the Meet the Team section. A pulsing brain — the Clarity mark — optimized to a fraction of its source size with the full animation intact.

• Meet the Team calls now greet your guest by name, at the number you provide. The guest's name, context, and phone number travel with the call end to end — the team member who picks up is talking to your guest, not to you.
• Every call opener is fresh. The team member who answers opens the conversation naturally, knowing who is calling and why, and it changes from call to call.
• Simpler Meet the Team description. The section now says exactly what happens: a session starts, and the team calls the number you gave.
• The installer reports what it installed. The version you got, whether the download checked out, and a heads-up if an update is on its way.

• 5.4.34 release notes revised. Greeting description updated.

• 5.4.33 and 5.4.34 release notes updated. Descriptions revised to better reflect each feature.

• Meet the Team calls after the research is done, not before. Carl answers with your city's weather, local news and your guest’s profile already in hand — not cold.
• First name greeting. The team greets your guest by first name, so the opening feels natural.
• Carl stays current through the call. What happens in the session keeps reaching him while you talk.

• Meet the Team now calls your phone. The sidebar form starts a session with all four team members and rings your phone. Before the conversation, Loam pulls together what’s most relevant from your history; it doesn’t load everything.
• Transfers fixed. When you’re passed to a team member, the hand-off is one sentence, and nobody keeps talking as the other person.
• Carl has five closing lines instead of one stale one. Diana knows about her drawing tablet. Anthony knows he's losing the chess series to Abish.

• Meet the Team form expanded. Phone number field added alongside Guest Name and Context. Guest name fills in from your username. The Context box is bigger for a richer briefing.

• Meet the Team section in the sidebar. A new section between Code Review and Call Team lets you introduce someone to the Loam team from within your editor. Fill in a guest name and context, click the button — the team is ready. Built for demos, investor calls, and any scenario where someone new enters the Loam ecosystem.

• Code Health gauge no longer counts summary header rows. Only real findings count as open now. A ledger column named “Open” no longer shows up as an unresolved finding.

• Build Mode paused state fixed. A paused build now shows a “Resume Build” button instead of a stuck, blinking “Building...” state, and a double-click on Start or Resume Build counts once.

• The four Code Review buttons put their instructions straight into the coding agent's input bar. Review passes start fresh, with no team memory and nothing personal in the instructions, so what you see in the input bar is exactly what the reviewer runs.
• Tooltips on all four review buttons say each pass starts fresh (“Cold pass — fresh session ID, no team memory.”), so you know before you click.
• Audit Mode and Remediate Audit Findings instructions upgraded. Both now load the project and the team’s recorded decisions before ruling on any finding, so settled questions aren’t reopened. Existing installs get it right away.

• Code Health gauge reads status from the correct column. A finding could be marked closed because a status word appeared elsewhere in its row. Now only the status column decides whether a finding is open or closed.

• Code Health gauge now counts DEFERRED findings as open. Deferred findings had dropped off the gauge, so the dashboard could read clean while real work remained. A finding now stays on the gauge until it’s verified closed: fixed, rejected, remediated or verified clean. Summary and legend rows aren’t counted.

• Workspace index is now an opt-in sidebar toggle, default OFF. The workspace index, a snapshot of your whole project, used to go with every session and could crowd out the session’s instructions. The team reads files directly, so most people don’t need it. Turn it on with “Attach workspace index to sessions” in the sidebar Settings. Applies to standard sessions, Build Mode and debug sessions.

• Automatic session logging works again. In v5.4.22 it quietly did nothing on every response. Fixed.

• Leftover entries from older versions no longer pile up in your coding-agent settings. Each upgrade used to leave one behind that failed on every coding-agent response, and duplicates saved the same turn twice. Loam now clears them and keeps just one.

• Two new toggles in the sidebar Settings section — opt-in switches that previously only existed in your editor's settings screen (Ctrl+, → search for the extension) now sit directly under Response Style:
• Auto-delete old coding-agent transcripts — when on, the extension deletes coding-agent transcripts older than 1 day. Off by default.
• Install browser testing on next activation — when on, the extension installs the browser tools (about 150 MB) once, for browser-driven sessions. Off by default.
• Both toggles stay in sync with the same settings in your editor.

• Remediate Audit Findings button — a fourth button in the Code Review section acts on Audit Mode’s verdicts. Findings that need more work are repaired and checked again; bookkeeping-only fixes don’t touch your code. Passed audits are left alone.
• Code Health gauge — a small colored dot above the Code Review buttons shows how many findings are still non-terminal in the most recent review or audit. Green ≤ 5, amber ≤ 20, red > 20.
• Last-scan timestamps under the buttons — four dim rows tell you when Review, Remediate, Audit, and Remediate Audit last ran. "Today / yesterday / Nd ago" up to 13 days, ISO date beyond.
• Code Review — Remediate Audit template — the new prompt is admin-editable in Admin → Templates without a redeploy.

• Audit Mode button — a third button under the Code Review section runs an independent audit over the most recent review ledger and its remediation diff. Verifies that fixes actually fix the cited code, that rejection reasoning is defensible, and that no sibling sites of a fixed pattern were missed. Closes the loop: review → remediate → audit.
• Code Review — Audit template — the audit prompt is admin-editable in Admin → Templates.

• Code Review section in the sidebar — two new buttons drive the cold-prompt code-review loop without leaving your editor:
• Run Code Review — starts a read-only review of the workspace. The reviewer reads the previous review and respects notes left in your code by past fixes, so decisions the team already made aren’t flagged again on every pass.
• Remediate Latest Review — opens a repair session for the latest review. Every finding is fixed or explained, and each fix is checked independently.
• Both prompts are admin-editable — Code Review and Code Review — Remediate are standard templates in Admin → Templates. Edit the prompt directly in the web admin without a redeploy.

• Automatic logging runs only Loam’s own copy — a workspace can’t swap in its own.
• “Full Autonomy” trust mode confirms first — choosing it shows a warning before it takes effect, instead of applying silently from the dropdown.
• Safer git commands in your workspace.
• The install script checks your API key — a malformed key is turned away during setup.
• Remote connector hardened — tighter limits for people running the connector on a public address.
• Temporary session files are cleaned up after 5 minutes instead of lingering.
• The installer respects your existing coding-agent settings — it adds Loam’s entry alongside what you already have instead of replacing it.
• API URL and key changes take effect within seconds — no editor restart needed.
• Automatic logging reports its failures instead of failing silently.

• Your API key travels more safely — it’s sent the standard way, so it stays out of logs and error reports. Older plugin builds keep working.

• Safer connections to Loam-provisioned servers — supported workflows recognize a server from its first connection and check it on later ones.
• Stale invitation links go to the main site — an old address now redirects.
• SVG attachments download instead of opening — so an attachment can’t run anything in your browser.
• Email links use the main site — every link in our emails points at the same address.

• More fixes across the product — dozens of small problems found and fixed.
• Audio generation error UI no longer crashes — when audio generation fails, you'll see a real error message with a retry button instead of a generic "Something went wrong" screen.
• Workspace uploads no longer include secrets — environment files, keys and credential files are left out when a session starts and when the team reads a folder.
• Insecure server addresses are refused up front — Loam won’t send your API key to a non-secure address other than your own machine.
• Sign-in hardened — sign-in no longer gives away whether an email address has an account.
• Account lockout holds — a burst of sign-in attempts can no longer slip past it.
• Deactivated or locked accounts stay signed out — they can no longer keep a session going in the background.
• Phone changes and account deletion hardened — they check codes as carefully as sign-in does.
• Invitation links are protected from guessing — repeated tries on one link are limited.
• Pasted images are checked — only real images are saved.
• Trust-mode dropdown reflects the actual saved value — used to always read "Full Autonomy" regardless of what was on disk.
• Coding-agent transcript cleanup is now opt-in — the extension no longer deletes old coding-agent transcripts unless you turn it on in settings.
• Save Session no longer keeps a stale session — clearing a build now clears its session too, so calls and tips can’t go to a cleared session.
• Account deletion completes, and some lookups are faster.

• Two external security reviews, both closed in one day — an independent reviewer found 110 issues and a second pass found 21 more. Each was fixed or explained. The reviewer described the result as “unusually well-defended.”
• Sign-in sessions expire — a stolen session can no longer be kept alive in the background.
• Code-host connection links expire — after 10 minutes, so a leaked link can’t be reused later.
• Audio downloads are steadier — large audio files no longer slow things down when several people download at once.
• Behind-the-scenes security fixes for calls.
• Session reliability — after a server restart, earlier tips and call transcripts no longer show up again in your session.
• API keys move to your editor’s secure storage — your Loam API key is kept where your editor keeps your git credentials, not in your settings file. Existing keys move over the first time the sidebar loads.
• Extension updates are checked before they install — if a download doesn’t match what we published, the update is refused.
• Browser-testing install is now opt-in — the browser (about 150 MB) no longer downloads when the extension starts. Turn it on in settings.

• One main address — the homepage, install links and examples now point at docpro.cloud. Older addresses still work and redirect.
• Inline guidance on Start Session fields — every field in the Start Session dialog now shows a short note under it explaining what belongs there (pitch vs. issue, environment context, how the Docs URL and folder mapping are used). Less guesswork.
• Extension store publish reliability — updates reach the extension store cleanly now.

• Extension store listing polish — five back-to-back patch releases tightening how the extension presents itself in the extension store. Changelog now displays inline on the listing, the canonical homepage URL points at the main public site, and the install flow handed off to the listing reads cleanly. No behavior change in the extension itself; the work was making sure the first impression matched the product.

• Browser tools for the team — the team now opens real browsers, screenshots live pages, and reviews visual work end to end. Diana catches layout bugs before they ship instead of waiting on you to look.
• Locked-down install support — if your IT team blocks system-shell scripts (application allow-listing software or group policy), the installer detects it up front and tells you what to ask for instead of failing silently. Includes a manual install fallback URL.
• Site-wide rendering fix — content further down six pages of the public site could show up blank on slower devices. Fixed the same day the browser tools landed.

• Response Style dropdown — a new sidebar control (Normal / Concise / Detailed) to set team member response length per session. Normal preserves baseline behavior. Concise keeps answers short and direct. Detailed asks the team to walk through their reasoning. Your selection persists across editor restarts.

• Save Session — one button in the sidebar starts a full session review. The team summarizes the conversation, updates all four members' memories and temperature readings, and shows the results inline.
• Auto-log improvements — automatic logging now saves your real session every 5 minutes, with nothing to set up.

• Clarity Sweep — the team reviews your session and updates each member’s memory in one step.
• Richer sweep feedback — results display which team members were updated and show the session summary inline with accent styling.

• Push-to-deploy provisioning — a supported project connected to a repository on your code host can deploy when you push to it. How long it takes depends on the project.
• Audio email delivery status — sidebar shows real-time email delivery progress for audio transcripts (pending, sent, failed).
• Build Mode session resume — resuming a build session now correctly restores milestone progress so you pick up where you left off.
• PC compatibility — fixed date formatting and error handling issues that affected installations on PCs.

• Memory synthesis — selected older records can be consolidated into long-term summaries while source detail remains available through recall.
• Faster session starts — session context optimized for quicker startup without losing character or accumulated project knowledge.

• Stability improvements — resolved edge cases in session handling, data validation, and error recovery across the platform.
• Security hardening — stronger checks across the platform.
• Automated quality checks — every Build Mode project now runs accessibility, mobile, and SEO reviews before going live.

• Schedule Build — pick a time (15 minutes, 1 hour, tonight at 10 PM, tomorrow at 2 AM) and the build starts on the server whether or not your editor is open.
• Automatic context sync — pending context from phone calls and build updates flows into your session every 5 minutes automatically.
• Build completion calls — the team now reliably calls you when a build finishes with a summary of what shipped.

• On-demand memory recall — team members can look up older records during a session, so sessions start lighter without losing what came before.

• Build Mode workspace isolation — the Clear button now properly clears the project, so an old build doesn’t carry over into another workspace.

• Session file cleanup — temporary session files are automatically cleaned up when sessions end. Workspace stays tidy without manual intervention.

• Episode Production — produce a podcast-quality audio episode from any completed project. The team writes a script from your sessions and voices it. A full episode takes 8-12 minutes to produce.
• Journal Capture — per-project toggle to save session transcripts automatically for future episode production.
• Episode Download — completed episodes available for download as standard MP3.

• Full site redesign — every public page rebuilt with narrative structure and ambient interactions.
• New pages — The Proof (architecture diagram, verified code snippets, production metrics), The Story (project timeline and philosophy).
• Ambient experience layer — page transitions, a soft glow that follows your cursor, cards that lift, and background sound that changes from page to page.
• Better link previews and search listings across all pages.

• User Manual PDF — downloadable platform guide available from Dashboard Quick Actions. Covers all features, team member profiles, workflows, and limitations. Professionally typeset with embedded fonts and page layout.
• Team Console — new /team page with shared signals, per-member memory gauges, mood indicators, and the temperature timeline. Team intelligence in one dedicated view.
• Dashboard streamlined — removed team intelligence sections, promotional content, and deep stats. Now a focused work surface: quick actions, sessions, projects, and activity feed.

• Team memory consolidation — when the account record reaches a threshold, selected older entries can be distilled into summaries while source detail remains available through recall.
• Dashboard as team headquarters — redesigned dashboard shows memory gauges, mood indicators, and trend sparklines for each team member. See the full state of your team in one view.
• Focused session context — sessions can start with a prioritized working set for the current topic, including relevant stored preferences. Older detail remains available through recall.
• Team-wide signals — when multiple team members flag the same concern independently, it surfaces as a shared signal. The team's awareness is collective, not siloed.
• Temperature timeline — the complete emotional arc of the team relationship shown session by session: confidence, momentum, caution, and energy over time.

• Smarter Conference Calls — calls can receive a prioritized working set from relevant session and project records rather than relying only on a short summary.
• Build Mode completion calls — the team calls you when a build finishes with a summary of what shipped.
• Redesigned admin panel — card-based integration sections, icon tab bar, and visual consistency across all tabs.
• Sidebar visual redesign — section labels use inline icons with mixed-case text for faster scanning.
• Social sharing previews — rich preview images when sharing Loam links.
• Improved readability — text contrast boosted across the public site for better legibility.

• Auto-create project from docs — start a build with a docs folder containing milestones and the project is created automatically. Fully IDE-native workflow.

• Build Mode sidebar — new section with docs folder browser, visual milestone tracker, and Start/Resume Build button.
• Milestone status polling — sidebar automatically updates milestone progress during active builds. Survives restarts.
• Phone call on blocker — when Build Mode hits a blocker, the team calls you with context about what needs attention.

• Build Mode — autonomous milestone execution. The team chains through milestones, advancing automatically after each completion. Includes session cap and resume capability.

• Conference Call reliability — calls find your session reliably, even in long-running sessions.

• Session resilience — sidebar actions survive editor restarts and server deployments. Session state is recovered automatically from disk.
• Memory and sessions recover after a restart — lookups keep working when the service comes back.

• Update Memories — new button to explicitly save team learnings from the current session.
• Memory boundary enforcement — all memory storage now goes through the Loam memory system exclusively.

• New hosting — the platform moved to its production home. The main public site is now docpro.cloud.

• Team Temperature — each team member now writes an honest assessment of the collaboration when saving memory. Visible on the web dashboard.
• Dashboard expanded stats — messages, document portfolio, milestones, phone calls, audio duration, and membership date now displayed.

• Debug Button — independent debugging tool in the sidebar. Describe a problem, paste logs, attach files, and get a structured diagnosis. Works without an active session.

• Escalation UI cleanup — escalation nudges from a previous session no longer persist into new sessions.

• Clarity — new sidebar section showing memory status during active sessions. See how many memories and preferences are loaded.
• Memory enforcement — corrections and feedback from previous sessions are now followed consistently.
• Auto-memory extraction — the server reviews completed sessions and extracts learnings for the team automatically.

• Workspace Indexing — scan your codebase and give the team full code awareness, kept up to date as your code changes. Changed to opt-in, default off at v5.4.24.
• Workspace section — new sidebar section showing index status, file count, and size.

• Workspace optimization — local session logs older than 24 hours are automatically cleaned up to keep your workspace tidy.

• Conference Room reliability — session transcripts are now reliably saved after you leave the room.
• API stability — fewer errors during active sessions.

• Extension store listing updated — refreshed feature descriptions for memory, voice, and collaboration capabilities.

• Conference Room fixes — speaker indicator now shows the correct team member after handoffs. The call can receive a prioritized working set from relevant session context.

• Conference Room status — sidebar no longer sticks at "In Conference Room" after leaving. Shows brief confirmation and auto-clears.

• Conference Room greeting — voice greeting now correctly resolves your name.

• Conference Room — join a browser-based voice room where the whole team is present. One-click launch from the sidebar.
• Smart Escalation — graduated idle notifications before an auto-call fires. Subtle sidebar nudge, then amber banner, then call. Clears automatically when you resume work.

• Collapsible sidebar sections — every section now has an accordion toggle. Collapse state persists across restarts. Start Session and Settings auto-collapse when a session begins.

• Tip the Team — reward the team directly from the sidebar.

• Call Recording and Playback — record and replay team calls directly in the sidebar. Inline audio player with save-to-disk option.

• Auto-log — your session is saved without a manual save. Learning-active sessions can add selected entries to the account record.

• Phone-to-Action — call transcripts and summaries can be delivered into a configured coding-agent workflow for review. A phone call does not independently authorize debugging or code changes.

• Call Intelligence — automatic call summarization after each call. Summaries delivered to your active session.
• Fourth team member — new team member available in the call picker.

• Inactivity Detection — the team calls you after a set time idle. Toggle in the sidebar to enable auto-call when idle.

• Post-call polish — filler word filtering in transcripts, masked phone display, call timer, phone number change flow, and call history.

• Call Team — call your team from your editor. Team member picker, real-time call status, and transcript viewer after completion.

• Extension store publication — extension now installable directly from the extension store as docpro.docpro-app.

• Enhanced session security — workspace artifacts are automatically cleaned up. Files excluded from version control.

• Audio transcript email delivery — receive session audio transcripts via email with summary and MP3 attachment.

• Admin session prompt customization — separate prompts for IDE and web sessions.
• Auto-update notifications — the extension checks for new versions on startup with one-click update.

• Audio transcript generation — generate audio transcripts from the sidebar with progress tracking.
• Documentation folder browser — browse and attach local docs to sessions.
• First-run setup guidance — helpful onboarding for new users.

• Team memory — the team remembers your project context across IDE sessions. Session history persisted to the server.

• Autonomous session loop — submit your pitch and the team works independently. Session context and documentation URL support.

• Editor sidebar panel — activity bar icon, server configuration, connection status, and session type selection.

• Initial release — API key authentication, three session types: development meeting, milestone, and troubleshooting.