Release Notes & Changelog — What the Team Has Shipped

v5.4.91 July 31, 2026

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.
A quieter codebase and sharper pages. A cluster of dead dashboard code — thirty-three files no page ever loaded — is gone, and a contrast pass on the marketing pages brought every flagged link and label up to WCAG AA.

v5.4.90 July 31, 2026

The installer’s signature is provable end to end again. The PowerShell installer we serve had been edited after it was signed, so the verification steps our own docs walk you through — check the Authenticode signature, compare the SHA-256 — would not have come back clean. The installer is re-signed, the published hash matches the bytes we serve, and re-signing is now a written step in the release procedure so an edit can never quietly outlive its signature again.
loam.team is a trusted update host. The extension keeps a deliberate short list of hosts it will accept an update from. loam.team was never added when the product took its new name, so entering the address the product itself advertises got every update refused. The list now includes loam.team — the guard itself is unchanged.

v5.4.89 July 31, 2026

The sidebar wears Loam now. The panel you work in was still dressed for the old name — a DocPro 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.

v5.4.88 July 30, 2026

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 VS Code starts.

v5.4.87 July 30, 2026

Loam’s public links now point to loam.team. The Marketplace 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.

v5.4.86 July 30, 2026

The Marketplace 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 Marketplace’s light listing page. The icon is transparent now, so the mark sits cleanly on whatever is behind it — light or dark.

v5.4.85 July 30, 2026

New name: Loam. DocPro is now 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.

v5.4.84 July 28, 2026

Start Session and Meet the Team explain a paused team like everywhere else. They were the last two places that didn’t. Meet the Team said nothing of its own and sent your key across the wire for an answer Loam already had; Start Session could leave the header reading “Connected” after the team had already paused, until the next check caught up. Both now say the same sentence as the rest of the product, and the paused banner catches up immediately. Every way into a session now tells you the same thing in the same words.

v5.4.83 July 26, 2026

A website address that arrives with a repo is not yours, and Loam no longer treats it as though it were. Opening a folder registers the site named in .docpro/surface.json — and if that file was committed into the repository, the address in it came from the repository rather than from you. Loam now uses only a declaration you wrote on this machine, and says so plainly when it skips one, with the two commands that 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, the paused banner catches up immediately instead of waiting for the next check, and neither sends your key across the wire for an answer Loam already has.
Opening a folder registers your site once, not twice. Two things could ask at the same moment and both would ask the server.

v5.4.82 July 26, 2026

Point Diana at your site once, and she watches it from then on. Open a folder with a website in it and add a small .docpro/surface.json naming 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 never fetches an address it shouldn’t. Loam now refuses to point its browser at anything that isn’t a public site — before it goes, and again if the page it asked for redirects somewhere else on the way.

v5.4.81 July 26, 2026

A paused team no longer calls you. When a trial ends without an Anthropic 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.

v5.4.80 July 26, 2026

When a trial ends without an Anthropic key, the team pauses — and says so everywhere. Before, sessions kept running while nothing the team learned was saved for the next one — the ride ran with the screens off. Now the pause is honest on every surface: the sidebar says “Your team is paused — trial ended,” the Start Session button waits with it, and any tool you reach for answers with the one sentence that matters — add your Anthropic 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.

v5.4.79 July 18, 2026

Your team now tells you when it’s running degraded. If your account has no Anthropic key and no active trial, the Team page, every member’s record page, and the VS Code sidebar 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 Anthropic 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 had never gone out — a fault present 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 Anthropic key could still be locked out when the platform key failed. Your key now takes over instead.

v5.4.78 July 11, 2026

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 claim it never went out.

v5.4.77 July 10, 2026

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 with a session that never managed to start.

v5.4.76 July 10, 2026

Opening a second tab right after starting a session could hand your call to it. For about two minutes after a session starts, a second Claude Code tab opened in the same folder could win the right to answer your calls — the last one to arrive took the line. Claims are now first-come and final: once your session's tab holds the line, another tab can never take it over.
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 past the point anything could act on them — are now cleaned up automatically instead of accumulating forever.

v5.4.75 July 10, 2026

A call could go unanswered if you'd had another session open in the same folder earlier. A leftover session still running in the background could hold the line and quietly swallow new call requests — you'd click Call Team and see “the session didn't answer,” even though everything was set up right. Each session now keeps its own line, so an old one can't block a new call.

v5.4.74 July 10, 2026

The team could go quiet mid-call and lose the thread of what you were saying. Once a call connected, nothing kept your conversation current while you were still on the phone — only what happened after you hung up was guaranteed to land. The team now stays with you for the whole call, the same way it already has on Meet the Team calls, so what you say while you're still talking gets through too.

v5.4.73 July 10, 2026

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.

v5.4.72 July 10, 2026

A window reload could still hand your call to the wrong tab. Right after Claude Code restarts, every tab you have open can start up at once, and one of them used to simply be first. A tab now has to prove it's the one actually running your session before it can answer for it.

v5.4.71 July 10, 2026

A call could be answered by a tab that had nothing to do with it. With more than one Claude Code window open, the request to call you could reach whichever one happened to finish first — including one working on something completely unrelated. It's now addressed to the specific session that asked for the call, and nothing else can pick it up.
The request handed to your session now explains itself. It used to ask the session to act without saying anything back to you. Now it names who's asking and why, and tells the session plainly: if anything's wrong, say so out loud instead of failing silently.
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 never went out, with a Try again.

v5.4.70 July 10, 2026

Call Team could be clicked before anything was listening. On a freshly opened window, the button worked immediately — but the piece that answers a call request hadn't started yet, so the click went nowhere and the panel never learned why. The button and the mechanism that answers it now come up together.
A call the panel had already given up on could still ring your phone later. A request that timed out used to stay valid indefinitely; starting a new session afterward could fire a call you'd already been told had failed. Requests now expire on the same clock the panel uses to declare them dead.

v5.4.69 July 10, 2026

Call Team now hands the call to your live session. Clicking Call Team no longer places the call from the sidebar — it asks the Claude Code session in your open folder to make the call itself. Before dialing, the session reads up on you — who you are, your history with the team, what you've been working on — so the team member who calls already knows why. Claude Code 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 reports each real 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 nothing spins forever: if the panel loses track of a call, it says that too and points you at the call log.
Automatic session logging works now — it never had. The piece that records your conversation into the team's history after every response shipped without a way to read its credentials, so it had been silently skipping every log since it was introduced. The extension now delivers those credentials where the logging can read them — in your user-level settings, never inside a repository — and re-checks them at every session start, so your sessions genuinely reach the team's record.
The Call Team button can no longer fire a second call underneath a live one. The button stays disabled for as long as a call is genuinely in progress — including long calls — and re-enables only once the call has ended or failed.

v5.4.68 July 9, 2026

Trust Mode now tells you when it takes effect. Switching Trust Mode applies to your next Claude Code 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.

v5.4.67 July 6, 2026

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.
What you write sticks. When you write your own moment, it's now saved into that team member's lasting memory, not just reacted to once and forgotten — the same kind of memory that carries across every session. Moments the team writes for you as a surprise are not saved this way, since those are invented for the occasion, not something that happened.

v5.4.66 July 6, 2026

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 every time. It no longer draws from a fixed list — it composes a fresh moment for you, and the same one will never be delivered to you 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.

v5.4.65 July 6, 2026

Tip the Team fine print now describes the delivery. The note under the button says when and how your moment arrives — delivered on the team’s next log turn, performed once — instead of pointing at a different feature.

v5.4.64 July 6, 2026

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 — nothing the team performs will ever claim 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.

v5.4.63 July 2, 2026

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 Gmail and Outlook. 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.
Dynamic Souls: the team remembers every caller. Each team member now carries durable memory across phone calls — what a caller shares on one call, the team knows on the next, and what the team learns on a call flows back into its written memory the moment the call ends.
A rebuilt live-call voice pipeline. Calls now run over Loam’s own real-time bridge, with live context streaming to the team mid-conversation — including the ability to look things up during the call and answer with current information.
Session-start hardening. Opening a brand-new or empty folder could previously start a session without the team’s project history loaded. Sessions now open with the full list of projects the team knows, load the matching history first, and the team reads its entire briefing before responding.
Bundled Loam tools updated (1.10.8 → 1.12.2). Adds scheduling meeting invites and marking meeting deliverables done from your session, richer guidance when a project lookup comes up empty, and a fix for session learnings failing to save after a caller-history lookup.

v5.4.62 June 30, 2026

Response Style now mirrors Claude Code's built-in output styles. The sidebar's Response Style control lists Default, Proactive, Explanatory, and Learning — the actual styles Claude Code ships — and choosing one applies it to your workspace on your next session. The earlier list included a “Concise” option that Claude Code 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.

v5.4.61 June 27, 2026

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 VS Code theme, including light and high-contrast. The list still shows exactly the session types your administrator has turned on, with the names they chose, and falls back to the standard set if it can't reach the server.

v5.4.60 June 27, 2026

Your administrator now curates the Start Session list. Which session types appear in the sidebar's Start Session picker — and what each one is named — is now set from the Loam admin panel, so the list can be updated without an extension release. The default set is unchanged.

v5.4.59 June 26, 2026

The code-review completeness guard is more reliable. The stop hook that keeps you from closing a code review while findings remain now confirms the current session before trusting it — so a leftover marker from an earlier session (a call, or a session you just launched) can no longer make the check skip and let a review close while findings are still open. Completes the malformed-ledger guard from v5.4.58.

v5.4.58 June 25, 2026

The sidebar now warns when a review ledger total looks wrong. When the sidebar's open-finding count doesn't match the number the ledger itself declares as remaining, a warning appears — so a corrupted or partially written ledger can't silently read as clean. An auto-installed stop hook also prevents closing a review session while the mismatch persists, and clears itself once the ledger is corrected.

v5.4.57 June 25, 2026

The team's tools no longer go missing after an update. A recent change refreshed the tool server when the extension auto-updates, but only refreshed part of it — so an update could leave the server unable to start and the whole Loam tool set would quietly disappear until a reinstall. Updates now deliver the complete, matched tool server as a single unit, so the tools always come back. A "Reload Now" prompt still appears when they change.

v5.4.56 June 25, 2026

Security and stability hardening. Tightened how the team reads files from your workspace, added stricter validation on call-status requests, and updated the MCP server's dependencies to their latest patched releases. Version reporting across the app and the MCP server is now consistent everywhere.

v5.4.55 June 24, 2026

New tools show up right after the extension auto-updates. When Loam refreshes through the Marketplace, 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.

v5.4.51 June 21, 2026

You can switch Trust Mode back to Supervised again. Choosing Supervised from the Trust Mode dropdown now re-imposes Claude Code'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.

v5.4.50 June 20, 2026

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 automatically, so what the dropdown shows always matches how the team answers.

v5.4.49 June 20, 2026

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.

v5.4.48 June 20, 2026

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.

v5.4.47 June 20, 2026

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.

v5.4.46 June 14, 2026

Call records stay continuous for the full call. The session now logs activity every 30 seconds while a team member is on the phone, so the record no longer shows a gap for the duration of the call.
Team photo refreshed to the current June 2026 team in the sidebar hero.

v5.4.43 – v5.4.45 June 13 – 14, 2026

Rotated credentials take effect within seconds. The shared server tools — project context, server provisioning, deploys — now pick up updated credentials within five 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.

v5.4.42 June 12, 2026

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.

v5.4.41 June 12, 2026

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.

v5.4.40 June 12, 2026

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.

v5.4.39 June 12, 2026

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

v5.4.38 June 12, 2026

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.

v5.4.37 June 12, 2026

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 generated fresh for that call. The team member who answers opens the conversation naturally — informed by who is calling and why — and it is never the same line twice.
Simpler Meet the Team description. The section now says exactly what happens: a session spawns, and the team calls the provided number.
The installer reports what it installed. Server version, integrity verification of the download, and the version that actually landed — with a heads-up if a deploy is mid-flight.

v5.4.36 June 12, 2026

5.4.34 release notes revised. Greeting description updated.

v5.4.35 June 12, 2026

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

v5.4.34 June 12, 2026

Meet the Team call fires after research loads, not before. The session opens, runs all 8 parallel searches, commits a full context brief, then places the call. Carl answers with your city's weather, local news, and guest profile already in hand — not cold.
First name greeting. The guest name field parses to first name before it reaches the phone agent — so the opening feels natural.
Session heartbeat every 60 seconds. The session logs turns continuously after the call fires, keeping Carl's live context current throughout the call.

v5.4.33 June 12, 2026

Meet the Team now calls your phone. The sidebar form opens a full team session and rings your phone simultaneously. Carl picks up with the team's complete memory already loaded — every team member's cross-session history in context before the first word.
Transfer mechanics fixed. When the orchestrator routes a call to a team member, he says one sentence and transfers immediately. He does not continue talking as the other person.
Carl has five closing lines instead of one stale one. Diana knows about her Wacom tablet. Anthony knows he's losing the chess series to Abish.

v5.4.32 June 12, 2026

Meet the Team form expanded. Phone number field added alongside Guest Name and Context. Guest name pre-fills from your authenticated username. Context textarea expanded for richer briefing.

v5.4.30 June 12, 2026

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 VS Code. 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.

v5.4.29 June 11, 2026

Code Health gauge no longer counts summary header rows. The parser now requires a finding-ID-shaped first cell (starts with a letter, contains at least one digit) before a row counts as open. A ledger column literally named "Open" no longer registers as an unresolved finding.

v5.4.28 June 11, 2026

Build Mode paused state fixed. A paused build now reliably shows a "Resume Build" button instead of staying stuck on a blinking "Building..." state. The connection-check on sidebar reload no longer re-sends the build-started signal. Double-click protection added to Start/Resume Build.

v5.4.27 June 11, 2026

The four Code Review buttons place their instructions directly into the Claude Code input bar. Review passes are cold by design — each click starts a fresh session with no team memory, and the instructions contain nothing personal — so the encrypted file handoff used by team sessions is no longer involved. What you see in the input bar is exactly what the reviewer runs. Unusually large instructions (over 32KB) fall back to a private temporary file that is read once and cleaned up automatically.
Tooltips on all four review buttons disclose the cold-pass behavior ("Cold pass — fresh session ID, no team memory.") so the session model is visible before you click.
Audit Mode and Remediate Audit Findings instructions upgraded to their canonical cold-start editions. Both now stand up their own session, load project context, and recall the team's recorded decisions before ruling on any finding, so settled questions are not re-litigated. Delivered from the server — the update reaches existing installs immediately.

v5.4.26 June 3, 2026

Code Health gauge reads status from the correct column. The previous parser read the entire pipe-delimited row as a single string, so a finding with a matching status keyword anywhere in the row — including the ID or description column — was incorrectly marked terminal. The parser now extracts the status cell by column index, so only the actual status column determines whether a finding is open or closed.

v5.4.25 June 1, 2026

Code Health gauge now counts DEFERRED findings as open. A deferred finding was in neither the open set nor the terminal set, so it silently dropped from the gauge — making the dashboard read clean while real work remained. The gauge now uses a closed-by-exception model: a row is open unless it carries a verified-terminal status (FIXED-VERIFIED, REJECTED-VERIFIED, REMEDIATED, or VERIFIED-CLEAN). Deferred, blocked, mistyped, and blank statuses all stay on the gauge. Summary and legend table rows are excluded from the count.

v5.4.24 May 31, 2026

Workspace index is now an opt-in sidebar toggle, default OFF. The cached workspace index — a full snapshot of your project's file tree and contents — was previously attached to every session automatically, consuming up to ~400 KB of prompt space and pushing session instructions out of the agent's read window. The team reads files directly with its tools; the snapshot was redundant for most workflows. A new "Attach workspace index to sessions" toggle in the sidebar Settings section controls it. Applies to standard sessions, Build Mode, and debug sessions.

v5.4.23 May 31, 2026

Auto-log hook is now bundled correctly inside the VSIX. v5.4.22 shipped without the hook file it referenced: the Stop hook registered an absolute path inside the extension bundle that resolved to a missing file, so session turn auto-logging silently no-opped on every response. The build process now copies the hook before packaging and verifies its presence — a future version cannot be published without it.

v5.4.22 May 27, 2026

Stale Claude Code Stop hook entries no longer pile up after extension upgrades. Each time the extension started a session, it added a Stop hook entry to .claude/settings.json pointing at its own copy of the auto-log script — and never removed the entries that prior versions had added at paths that no longer exist on disk. Those orphaned entries failed with Cannot find module on every Claude Code response, and surviving duplicates caused the same conversation turn to be saved to the server twice. The extension now prunes any stale or legacy auto-log entry before adding its own, so the list stays at one current entry no matter how many times the extension is upgraded.

v5.4.21 May 25, 2026

Two new toggles in the sidebar Settings section — opt-in switches that previously only existed in VS Code's Settings UI (Ctrl+, → search "docpro") now sit directly under Response Style:
Auto-delete old Claude Code transcripts — when on, the extension deletes ~/.claude/projects/**/*.jsonl files older than 1 day on activation. Off by default. Backed by docpro.cleanupClaudeTranscripts.
Install Playwright MCP on next activation — when on, the extension performs a one-time install (~150 MB) of the Playwright MCP server and Chromium browser for browser-driven sessions. Off by default. Backed by docpro.installPlaywrightMcp.
Both toggles read and write the same VS Code configuration keys, so flipping either in either place keeps the other in sync. State refreshes every time the sidebar becomes visible.

v5.4.20 May 25, 2026

Remediate Audit Findings button — a fourth button in the Code Review section closes the loop on Audit Mode's verdicts. Verdicts marked as needing reopen or completion go through the full repair-agent + verifier gauntlet; drift verdicts go through a bookkeeping-only path that cannot touch code. Passed audits are excluded.
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.

v5.4.19 May 25, 2026

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.

v5.4.18 May 25, 2026

Code Review section in the sidebar — two new buttons drive the cold-prompt code-review loop without leaving VS Code:
Run Code Review — kicks off a read-only review against the workspace. The reviewer reads the prior ledger and honors in-code anchor comments left by past remediation passes, so design decisions the team has already evaluated and rejected are no longer re-flagged on every pass.
Remediate Latest Review — opens a team-docpro remediation session against the latest ledger. Five parallel repair agents and five independent verifier agents drive every row to a terminal state with anchor comments planted on every rejection so the next reviewer pass can honor them.
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.

v5.4.17 May 24, 2026

Auto-log hook is locked to the extension bundle — the Stop-hook that records IDE turns now resolves to an absolute path inside the installed extension. A workspace cannot ship its own auto-log.mjs and have the extension execute it.
"Full Autonomy" trust mode confirms before bypassing permissions — selecting full-autonomy triggers a warning dialog before bypassPermissions is written, instead of taking effect silently from the dropdown.
Workspace git commands no longer shell out — internal git invocations use execFile with an argv array instead of child_process.exec, removing the shell-injection surface.
Install script validates your API key shape — install-docpro.ps1 checks API keys against dp_[A-Za-z0-9_-]+ before passing them through PowerShell strings, blocking quote-injection during setup.
Remote MCP server hardened — for users running the MCP plugin behind a public endpoint: origin allowlist via REMOTE_MCP_ALLOWED_ORIGINS, per-token rate limit (60 requests / 60 seconds), and a 5 MB request-body cap.
Decrypted session-prompt temp files clean up after 5 minutes — the file the extension writes for Claude Code to read is unlinked on a 5-minute timer instead of lingering.
Installer respects your existing Stop hooks — the previous installer overwrote any Stop hooks already in your ~/.claude/settings.json. It's now additive: it appends Loam's hook entry to whatever you already have.
Live API URL and key changes take effect within 5 seconds — the MCP plugin used to read credentials once at module load and never re-check. Updates now propagate on a 5-second TTL cache instead of requiring a VS Code restart.
Auto-log failures surface to stderr — 401 responses log once, 429 responses are retried once after a 1-second delay then surfaced, instead of disappearing silently.

v5.4.16 May 24, 2026

API keys move from request body to Authorization header — every call the MCP plugin makes now sends your API key in the standard Authorization: Bearer … header instead of (just) the request body. Header values are excluded from generic request-body logging, error-tracker payloads, and HTTP proxy debug captures by convention, so credentials no longer ride along in places they shouldn't be. Older plugin builds remain compatible — the backend still accepts body-field keys during the rollout window.

v5.4.15 May 24, 2026

SSH host-key pinning on every server you connect to — when Loam provisions a server for you, the host key is captured on first connect and verified on every subsequent connect. A man-in-the-middle attacker on the network path can no longer intercept deploy traffic without triggering a hard refusal.
Stale invitation links no longer route through legacy subdomains — anthropic.docpro.cloud redirects to the canonical apex; it's no longer in the invitation-origin allowlist.
SVG attachments downgraded — uploaded SVGs now download as application/octet-stream instead of image/svg+xml so the browser never executes script inside an attachment named like an image.
Email links use the canonical site — outbound emails now build URLs from a single PUBLIC_URL environment variable; hardcoded subdomain fallbacks removed.

v5.4.14 May 23, 2026

Fourth code-review pass of the day, closed clean — a six-agent whole-repo audit landed after the third-pass shipped, surfacing ~99 additional findings across backend, frontend, and extension. Every one either shipped a fix or is anchored in the code with the reasoning preserved for future passes. Zero deferrals.
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 ship secrets — .env, *.pem, id_rsa*, *.key, and files containing credentials are now excluded from the session-start workspace bundle and from "Read this folder."
API URL validation up front — pointing docpro.apiUrl at a plaintext http:// host (other than localhost) is now rejected before any request fires, instead of silently sending API keys in the clear.
Login timing oracle closed — login now runs a constant-cost password check even when the email doesn't exist, so an attacker can't distinguish "wrong email" from "wrong password" by response time.
Account-lockout race closed — concurrent login bursts can no longer all slip past the lockout threshold in the same race window; the check is now serialized at the database lock level.
Heartbeat reissue revalidates user state — token refresh now rechecks active / setup-complete / lockout state, so a deactivated or locked-out account stops being able to extend its session via background polling.
Phone-rotation and account-delete MFA hardening — these now use constant-time code comparison and reset the lockout counter on success, matching the login flow.
Invitation links get a brute-force gate — a per-token rate limit caps how many times a single invitation link can be inspected within a short window.
Image bytes are sanity-checked — pasted screenshots are verified against PNG/JPEG/GIF/WebP/BMP magic headers before being saved.
Trust-mode dropdown reflects the actual saved value — used to always read "Full Autonomy" regardless of what was on disk.
Claude Code transcript cleanup is now opt-in — the extension no longer prunes ~/.claude/projects/**/*.jsonl files older than a day on activation. Set docpro.cleanupClaudeTranscripts to true to enable.
Save Session no longer keeps a stale session ID — clearing a build now also wipes the session-id file, so call routing and tip pushes can't target a session that's been cleared.
Database hygiene — user-FK cascades cleaned up so account deletion actually completes; missing indexes added to usage-records lookups; outdated passlib dependency dropped from the lockfile.

v5.4.10 – v5.4.12 May 23, 2026

Two external security reviews, both closed in one day — an independent reviewer audited the full repo and surfaced 110 findings; a second-pass audit on the just-shipped result added another 21. Every finding either shipped a fix or is anchored in the code with the reasoning preserved for future review passes. The reviewer described the post-closeout codebase as "unusually well-defended."
Session-keepalive token lifetimes are now bounded — the heartbeat endpoint reissues a new session token only when the current one is close to expiring, instead of every 60 seconds. An exfiltrated token can no longer be kept alive indefinitely by background polling.
OAuth state values now expire — the signed state token used in the GitHub connection flow now carries a timestamp and is rejected after 10 minutes. A leaked URL from a browser history or referer log is no longer a forever-valid grant.
Audio downloads stream from the database — cold-cache audio rebuilds now stream large MP3 files through the worker in 1 MB chunks instead of materializing the whole blob in memory. Concurrent first-readers no longer cause a memory spike on deploys.
Webhook replay protection — the last remaining call-pipeline webhook strategy now requires a timestamp envelope. Captured webhook bodies can't be replayed.
Session reliability — when an IDE session is rebuilt from the database after a server restart or a worker eviction, prior tips and call transcripts are no longer re-injected into the next response. One-time delivery is now permanent.
API keys move to VS Code SecretStorage — your Loam API key lives in the same secure store VS Code uses for git credentials, not in settings.json. Existing keys are migrated on the first sidebar load.
Extension update integrity check — the extension verifies the SHA-256 of any downloaded update against what the server published before installing. If they don't match, the update is refused.
Playwright browser install is now opt-in — the Chromium binary (~150 MB) no longer downloads as a side effect of activating the extension. Set docpro.installPlaywrightMcp to true in settings to enable it.

v5.4.6 – v5.4.9 May 15 – May 22, 2026

Canonical host migration — the homepage, install guide links, and default server URL examples now consistently point at docpro.cloud. Older host names continue to 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.
Marketplace publish reliability — fixed a sequence of publish failures caused by publisher casing and PAT handling. Updates flow cleanly to the Marketplace now.

v5.4.1 – v5.4.5 May 2026

Marketplace listing polish — five back-to-back patch releases tightening how the extension presents itself in the VS Code Marketplace. Changelog now displays inline on the listing, the canonical homepage URL points at docpro.cloud, 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.

v5.4.0 April 28, 2026

Browser tools for the team — the team now opens real browsers, screenshots live URLs, and reviews visual work end-to-end. Diana catches CSS bugs before they ship instead of waiting on you to look. Powered by Microsoft's official Playwright MCP, pinned to a known-good version.
Locked-down install support — if your IT team blocks PowerShell scripts (ThreatLocker, AppLocker, GPO), 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 — caught and shipped in the same session the browser tools landed: a CSS opacity trap that was rendering below-fold content invisible on six pages of docpro.cloud for headless tools and slow devices. The Playwright workflow paid for itself before we even productized it.

v5.3.17 April 16, 2026

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 VS Code restarts.

v5.3 April 10, 2026

Save Session — one button in the sidebar triggers a full session review. The team summarizes the conversation, updates all four members' memories and temperature readings, and displays the results inline.
Auto-log improvements — the automatic turn logger now sends real session data to the logging endpoint instead of a status ping. Runs every 5 minutes with no configuration required.

v5.1 April 10, 2026

Clarity Sweep — server-side session analysis that reads logged turns and produces per-member memory updates in a single API call. No MCP dependency required.
Richer sweep feedback — results display which team members were updated and show the session summary inline with accent styling.

v5.0 April 9, 2026

Push-to-deploy provisioning — provision a server with a GitHub repo and changes go live automatically. Push your code, the site updates in under a minute.
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.
Windows compatibility — fixed date formatting and error handling issues that affected Windows installations.

v1.7.96 April 7, 2026

Memory synthesis — accumulated knowledge is automatically distilled into long-term summaries. Older sessions are compressed while preferences, decisions, and lessons are preserved.
Faster session starts — session context optimized for quicker startup without losing character or accumulated project knowledge.

v1.7.78–v1.7.86 April 5–6, 2026

Stability improvements — resolved edge cases in session handling, data validation, and error recovery across the platform.
Security hardening — timing-safe token comparison, path traversal prevention, input validation enforcement, and session ownership checks added to all sensitive endpoints.
Automated quality checks — every Build Mode project now runs accessibility, mobile, and SEO reviews before going live.

v1.7.73 April 3, 2026

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 VS Code 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.

v1.7.71 April 1, 2026

On-demand memory recall — team members can search and retrieve specific memories during a session. Reduces prompt size while keeping the full knowledge base accessible when needed.

v1.7.70 March 31, 2026

Build Mode workspace isolation — the Clear button now properly deactivates the project on the server, preventing stale build state from leaking across workspaces.

v1.7.68 March 29, 2026

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

v1.7.67 March 29, 2026

Episode Production Pipeline — produce a podcast-quality audio episode from any completed project. The system synthesizes a screenplay from session transcripts, then voices each line individually. 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.

Site Redesign March 29, 2026

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, cursor-following glow, card-lift interactions, and per-page audio energy scaling. Compositor-safe, 60fps.
SEO & validation — Open Graph tags, Twitter cards, canonical URLs, and structured data across all pages.

v1.7.63 March 28, 2026

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.

v1.7.62 March 27, 2026

Team memory self-optimization — when accumulated knowledge reaches a threshold, the team distills it automatically. Older sessions compressed while every preference, architectural decision, and lesson learned is preserved. Memory grows smarter, not just larger.
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 now start with memory focused on what's relevant to your topic, plus all standing preferences. Faster starts, less noise.
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.

v1.7.59 March 26, 2026

Smarter Conference Calls — the team now hears full session context on the phone, not just summaries.
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.

v1.7.58 March 25, 2026

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

v1.7.57 March 25, 2026

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.

v1.7.56 March 25, 2026

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

v1.7.55 March 24, 2026

Conference Call reliability — improved session handling ensures calls always find the session context, preventing errors in long-running sessions.

v1.7.54 March 23, 2026

Session resilience — sidebar actions survive VS Code restarts and server deployments. Session state is recovered automatically from disk.
Server-side fallback — memory and session lookups now recover gracefully after service restarts.

v1.7.49 March 23, 2026

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.

v1.7.48 March 22, 2026

AWS migration — platform hosting moved onto the production Loam infrastructure. The canonical public site is now docpro.cloud.

v1.7.47 March 22, 2026

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.

v1.7.44 March 21, 2026

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.

v1.7.42 March 20, 2026

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

v1.7.40 March 20, 2026

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.

v1.7.35 March 20, 2026

Workspace Indexing — scan your codebase and give the team full code awareness. Smart file prioritization with git-aware incremental updates. Changed to opt-in, default off at v5.4.24.
Workspace section — new sidebar section showing index status, file count, and size.

v1.7.33 March 19, 2026

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

v1.7.31 March 19, 2026

Conference Room reliability — session transcripts now reliably captured after leaving the room.
API stability — added request pacing to prevent errors during active sessions.

v1.7.30 March 18, 2026

Marketplace listing updated — refreshed feature descriptions for memory, voice, and collaboration capabilities.

v1.7.29 March 18, 2026

Conference Room fixes — speaker indicator now shows the correct team member after handoffs. Team has full session context when you join.

v1.7.28 March 18, 2026

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

v1.7.27 March 18, 2026

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

v1.7.25 March 17, 2026

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.

v1.7.23 March 17, 2026

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.

v1.7.22 March 17, 2026

Tip the Team — reward the team directly from the sidebar. Tips reinforce memory retention, relationship value, and behavioral continuity through the compression algorithm. The team remembers who invests in them.

v1.7.16 March 16, 2026

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

v1.7.15 March 16, 2026

Auto-log — every assistant turn is logged automatically without manual intervention. Consistent team behavior improvements.

v1.7.14 March 16, 2026

Phone-to-Action — call transcripts and summaries are delivered directly into Claude Code. The team acknowledges calls and acts on them immediately.

v1.7.13 March 16, 2026

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.

v1.7.12 March 15, 2026

Inactivity Detection — configurable idle timeout triggers a team callback. Toggle in the sidebar to enable auto-call when idle.

v1.7.11 March 15, 2026

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

v1.7.10 March 15, 2026

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

v1.7.8 March 16, 2026

VS Code Marketplace publication — extension now installable directly from the Marketplace as docpro.docpro-app.

v1.7.0 March 15, 2026

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

v1.6.0 March 15, 2026

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

v1.5.0 March 15, 2026

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.

v1.4.0 March 15, 2026

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.

v1.3.0 March 15, 2026

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

v1.2.0 March 14, 2026

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

v1.1.0 March 13, 2026

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

v1.0.0 March 13, 2026

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

What the team
has shipped.

Latest Major Release.

Version History.

What the teamhas shipped.

Latest Major Release.

Version History.

What the team
has shipped.