What's new

Release highlights for recent Wingman versions — and where the same notes reach you inside the product, from the Changelog dialog in Chat to the update pill in the desktop title bar.

Every change prepared for a Wingman build carries a short, user-facing note written alongside the change itself. The same authored catalog drives this page and the in-app changelog.

These versioned notes can be deployed before their matching immutable release is published. Check Downloads for the currently published Linux release; the About page shows the build you are running.

Version 1.7.69

October 16, 2026.

• See the plan while Build works: Build shows the agent's plan as a live checklist above the composer and names the step it is working on, for Codex, Claude Code and Kimi.
• Longer Build sessions cost less: When a long Build session is compacted, the summary reads the conversation from the prompt cache and stays on the session's model, so it costs less and is never cut short.
• Build commands on every supported Linux: Build runs shell commands in your own login shell, so they work on Ubuntu 20.04, Ubuntu 22.04 and Debian 12 even when the bundled zsh is turned on.
• Knowledge sources refresh in place: Uploaded documents and public repository sources update under their existing identity, keeping their access rules and earlier revisions. The MCP server library also gets a security update.

Version 1.7.68

October 15, 2026.

• Document updates that preserve history: Earlier knowledge document revisions survive server upgrades. Document archives and refresh operations retain their restricted access, and inconsistent storage or permissions stop rollout.
• Stop requests after a disconnect: Chat stops when a client disconnects during knowledge search, avoiding a fallback model request for a client that is no longer waiting.

Version 1.7.67

October 15, 2026.

• Current prices checked against the store: Current-price searches check official product pages before returning prices, keep product variants and markets distinct, and withhold amounts that cannot be verified. Older uploaded price tables cannot supply a current quote.
• Replace supported knowledge documents safely: Administrators can replace supported public text and Markdown documents while preserving their knowledge source. Unchanged content is reused, concurrent changes are detected, and searches check that the document is still current and published.
• Separate checks for stored and retrieved prices: The daily comparison checks stored product information separately from fresh retrieved evidence, so a correct current answer cannot hide an outdated index. Coverage remains eight selected products and their observed market.

Version 1.7.66

October 15, 2026.

• Voyager SDK guidance for your project: Skills recommend Voyager SDK 1.9 for supported older projects, respect explicit version pins, and require release-specific evidence for commands and APIs. Migration guidance separates source conversion from hardware validation.
• Checks for store price drift: Scheduled checks compare eight selected public products with retrieved knowledge, including variants, currency and availability, and detect bounded catalogue-membership changes. Other markets and checkout prices are outside this check.
• More reliable incremental website updates: Official Axelera homepage snapshots wait for initialized content and remove only proven duplicate carousel clones. Successful bounded retries clear their own temporary discovery failures; incomplete crawls still retain the previous published knowledge.

Version 1.7.65

October 15, 2026.

• Prices tied to the requested product: Current-price searches prioritize the official store snapshot, keep memory and cooling variants separate, and disclose missing variant evidence. Price follow-ups request fresh knowledge evidence and retain currency, tax and availability qualifications.
• Visible knowledge maintenance gaps: Repository sync checks processing changes before reusing an unchanged revision. Scheduled checks report missing or stale sources, uploads without a maintenance mapping, and failed retrieval checks. Store indexing preserves structured product offers and reuses unchanged content.
• Faster knowledge searches in Chat: Manual mode runs read-only Wingman knowledge searches and skill loading without approval prompts. Changes, commands and tools from servers you add still ask first.
• Chat ownership protection: Message writes, edits and imports preserve ownership and reject references to another person’s chats, threads, agents, groups or sessions.
• Clearer Build results: Google Gemini Build turns distinguish completion, stopped commands and blocked commands without duplicate interruption errors. Linux install guides again show wingman --version, and document processing retains PDF and Word section headings.

Version 1.7.64

October 15, 2026.

• Complete device target tools: Claude Code, Codex, and Gemini bundles include the device target command package. Bundle checks reject missing, modified, or incorrectly permissioned modules before delivery.
• Preserve source during SDK migrations: Migration guidance keeps unresolved application source intact, reuses complete references for the selected release, and reports missing inputs without inventing compatibility guards or execution commands. Explicit knowledge-search requests remain available as tools activate.
• More reliable knowledge retrieval and updates: Generic knowledge searches reduce repeated identical public website evidence while preserving explicit source and URL requests. Crawl lease renewals stay within their active deadlines, and complete generations receive a bounded publication budget while retaining atomic updates and ownership checks.

Version 1.7.62

October 14, 2026.

• Focused Voyager SDK 1.9 guidance: Migration and SDK help load shorter initial instructions while keeping the full setup and hardware guides available when needed. Guidance requires current knowledge searches, recommends SDK 1.9 for older projects, and respects explicit version pins.
• More complete knowledge updates: Website sync can index text patch attachments and recognize verified tracking, attachment and portal redirects without fetching their external destinations. Recognized SSO login actions are excluded before navigation, while genuine page failures still prevent incomplete updates from being published.
• Hosted knowledge health checks: Source health checks use measured retrieval probes and report their coverage, so a completed sync can also be checked for usable search results.

Version 1.7.61

October 14, 2026.

• Gemini in Build: Build can run on Google Gemini, including Gemini 4 Argon, through the Gemini CLI, the Antigravity CLI or your own API key, with low, medium and high effort.

Version 1.7.60

October 13, 2026.

• Run pipelines on another machine: Build a pipeline in Wingman and run it on an Axelera machine where Wingman is not installed: over your own SSH, through an SSH gate, or with a bundle you carry over. Wingman asks before every step that changes anything.
• Launch checks for Voyager SDK 1.9: Launch checks understand Voyager SDK 1.9 devices, so a good run on a 1.9 board, or one started from a laptop, now passes.
• Your searches stay out of our logs: Wingman no longer writes the text of your search queries to its server logs.
• Terms and privacy at sign-in: The dashboard sign-in page links the Terms and Conditions and the Privacy Policy.

Version 1.7.59

October 12, 2026.

• Follow explicit knowledge-search requests: When you explicitly ask Chat to search the knowledge base, it keeps the search tools available without first injecting automatic excerpts that could discourage the requested search.

Version 1.7.58

October 12, 2026.

• Complete results from parallel knowledge searches: Chat keeps each completed tool result when searches and skill references run together, so the next answer receives the retrieved knowledge instead of an empty placeholder.

Version 1.7.57

October 12, 2026.

• Display guidance follows your SDK version: Voyager guidance distinguishes SDK 1.8 OpenGL and Alpha Vulkan support from the SDK 1.9 Vulkan default and runtime2 rendering requirement. Browser and desktop skills use the same rules.
• More complete website discovery: Website sync follows page entries in sitemaps without counting nested image locations as pages. Failed attempts retain their actual page counts, and progress polling can recover from bounded connection or read timeouts for the same job.
• Keep newer desktop sign-ins: Concurrent refreshes and credential cleanup no longer overwrite a newer desktop sign-in. If cleanup fails, Wingman stops presenting the cached session as signed in.

Version 1.7.56

October 12, 2026.

• Updates from a remote desktop: Linux updates now install from a remote desktop session too. Wingman asks for an administrator password there, as it does at the machine itself.
• A fairer automatic check: When you ask Build for something new in the same chat, the automatic check judges the answer against that request, so Build no longer goes back to redo an earlier question.
• Every instruction reaches Earth: Build conversations on Earth 1.0 keep every instruction after the first, so the knowledge-base guidance and Wingman identity reach the model.
• Knowledge search on every step: Knowledge-base search stays available through a long Build or Chat session, and long sessions reuse their prompt cache instead of paying to write it again.
• SDK migrations retain structured evidence: Chat preserves structured knowledge-search evidence within the agent budget, so Voyager SDK 1.9 migration answers can use the retained results and see when others were omitted.
• Sign in with one click: When Build needs you to sign in, it points you to the button that does it instead of a command to type.

Version 1.7.55

October 11, 2026.

• Read SDK skills in browser conversations: Chat can activate its packaged Voyager SDK skills and read their reviewed reference files during a browser conversation. SDK 1.8 migration guidance uses component-specific SDK 1.9 compatibility requirements, including supported older firmware.
• Keep cloud documents readable: Open cloud documents retain their content when the editor changes their language. Closing a document or signing out still releases its content.
• See campaign landing totals: Admin statistics show lifetime and 28-day anonymous landing totals for campaign links and QR codes.
• Find documented command identifiers: Searches recognize supported escaped Markdown command identifiers while preserving original evidence and private-source protection. Website-reader responses are verified against stored evidence. MCP knowledge and code search preserve exact-identifier coverage verdicts, including when semantic results do not match the requested identifiers.
• Clearer release readiness checks: Release rehearsal follows the active credits billing authority, preserves database access for read-only inspection and reports the actual failing gate. Release checks install the pinned browser prerequisite. Website-reader activation can use an admitted immutable release candidate while retaining source, revocation and publication checks.

Prepared release (v1.7.55)

Version 1.7.54

October 10, 2026.

• Voyager SDK 1.9 guidance in Chat: Built-in Voyager skills cover SDK 1.9 setup, model selection, compilation and runtime commands, with a migration guide for existing SDK 1.8 projects. Guidance checks the selected SDK and hardware before choosing commands. New native kernel and graph compiler references explain optional dependencies and the limits of unverified execution.
• SDK 1.9 source-aware diagnostics: Chat recognizes released SDK 1.9 commands and namespaces. Grounding diagnostics distinguish terms that lack evidence from proven API absence, while retaining older SDK evidence.
• More reliable knowledge refreshes: Knowledge refreshes check complete indexed generations, reuse eligible unchanged content and rebuild changed sections. Code search recovers approved examples for identifier questions even when unrelated results fill the initial selection. Verified public embedded-build references keep usable source labels and code, while private origins remain anonymous. Website crawling requires verified reader readiness before publication.
• Avoid unused compaction cache charges: Build uses normal input billing when compacting a conversation, avoiding the cost of creating a prompt-cache entry that is never reused.
• Security maintenance: The dashboard web server image updates its TIFF library for a high-severity vulnerability. The API image updates Expat to Debian 2.9.0-1. The managed headless crawler removes vulnerable printing dependencies while preserving certificate and internal-network protections.

Prepared release (v1.7.54)

Version 1.7.53

October 9, 2026.

• Wingman tools sign in by themselves: When Build needs the Wingman tools sign-in, it opens it for you, keeps your message and sends it as soon as you approve. A fresh install no longer stops with a setup error.
• One line per stretch of work: Build folds its commands, tools and notices into one line you can open, so the chat reads like a conversation.
• Background commands that finish: A background command in Build no longer reads as running for ever. If Build cannot see its output, it says so and points to the files it writes.
• Helpers for independent jobs: On Earth 1.0, Build can hand independent jobs to Mercury 1.0 helpers and keeps the plan and the final check itself.
• Shell commands from the composer: Start a message with ! to run it as a shell command, and press Ctrl+G to write a long message in a full editor.
• Security updates: Chat runs on updated web and template libraries, and Build in Auto mode asks before it writes or reads outside your project.

Version 1.7.52

October 7, 2026.

• The Linux launcher stops forcing X11: Wingman now runs natively on Wayland when your session is Wayland, including compositors started from a console, and WINGMAN_OZONE_PLATFORM=x11 or wayland pins a platform when you need one.
• No keyring daemon on every launch: The launcher asks your session for its Secret Service, running or startable, and leaves KWallet and KeePassXC desktops alone; it starts gnome-keyring only when there is no provider at all.
• wingman --version and --help work anywhere: Both answer without a display, and a launch with no display exits with a message instead of crashing.
• A smaller package: The .deb ships one Electron binary instead of two identical 191 MB copies, and the public release README now says where to report problems.
• A faster Build composer: Up and Down recall earlier messages, Ctrl+R searches them, Esc twice stops a running turn, Shift+Tab cycles the access mode, a question mark lists every shortcut, and / and @ pick commands and workspace files as you type.
• Auto mode asks before risky terminal commands: In Build's Auto mode, a terminal command that changes to a folder outside your workspace, or hides a key press in a control character, now asks first, so it cannot delete files outside your project without a card.

Version 1.7.51

October 6, 2026.

• Build starts on Earth 1.0: Build now starts on Axelera Earth 1.0 with your old choice one click away, every Build chat runs at once, and a note above the composer says when a chat runs on Mercury 1.0 and lets you request an upgrade.
• A note when your turns run on Mercury: If you use Axelera Earth 1.0 or Venus 1.0, Chat now tells you when new turns run on Mercury 1.0, why, and when your tier comes back, and lets you ask for more from the same note.
• Build shows what is really running: The activity line counts only the current turn and shows the running command's own time, and commands left running when Wingman closed are settled with the reason.
• Retries keep what you attached: A message that waits behind a running reply keeps its files and selected text, a Retry never sends a file twice, and editing a queued message brings everything back to the composer.
• Your own name from the start: New accounts are greeted by the name you type, never a string made from your email address, and a sign-in that cannot be linked tells you which button works.

Version 1.7.50

October 5, 2026.

• Reports from your Build sessions: Type /report or choose Create report to turn a session's work into a PDF with checked figures: a solution study, a technical report or a results brief, with your name on the cover.
• Long Build chats keep every message: A chat past 5,000 messages reopens at its newest messages after a restart, nothing is lost, and Show earlier messages brings older ones back.
• Axelera Earth 1.0 is the Chat default: Chat starts on Earth 1.0 and keeps a model you pick. Requests now run side by side, and a request continues on Mercury 1.0 instead of stopping when your credits are busy.

Version 1.7.49

October 2, 2026.

• A steadier message box: Drafts stay with their own conversation, deleted text stays deleted, a message that fails comes back in the chat you typed it in, and Stop only stops.
• Your Build agent introduces itself as Axelera Wingman: The Build agent on the Axelera AI engine now presents as the Axelera Wingman agent, stays off your own ChatGPT sign-in, and keeps the conversation when you switch providers mid-chat.
• This week's security fixes: The search reranking library, the web framework and the PDF reading library move past the advisories published this week.

Version 1.7.48

October 1, 2026.

• A steadier message box: Drafts stay with their own conversation, deleted text stays deleted, a message that fails comes back in the chat you typed it in, and Stop only stops.
• Your Build agent introduces itself as Axelera Wingman: The Build agent on the Axelera AI engine now presents as the Axelera Wingman agent, stays off your own ChatGPT sign-in, and keeps the conversation when you switch providers mid-chat.
• This week's security fixes: The search reranking library, the web framework and the PDF reading library move past the advisories published this week.

Version 1.7.47

September 30, 2026.

• Paste pictures into Build: A picture pasted into the Build chat is attached once, and a picture or text pasted while the conversation or the side pane has the focus, or through the right-click menu, lands in the message box.
• Names that fit after a save: When the assistant saves a document in a conversation, the conversation is still titled after what it is about, the document keeps the title you asked for, and long titles no longer cover the header buttons.
• This week's security fixes: Next.js, axios, PyJWT, urllib3, gRPC, DOMPurify and several development libraries move past the advisories published this week.

Version 1.7.46

September 29, 2026.

• Search when you ask for it: When you ask the assistant to search the knowledge base or the docs, it now runs the search, including after it asks you a follow-up question, instead of saying search is not available.

Version 1.7.45

September 28, 2026.

• Imports stay on trusted sites: Skills now import only from GitHub and the skill market, and knowledge base crawls reach only approved sites, so a pasted link can no longer make the server contact any other address.
• Fresher system fixes in every release: Every hosted service is now built on a freshly updated base system, so security fixes to the software underneath reach you with each release.

Version 1.7.44

September 27, 2026.

• Install on Linux with one paste: The Downloads page and every release now show one block that installs Axelera Wingman on Ubuntu 20.04, 22.04, 24.04 and 26.04 and on Debian 12 and 13, and every release is installed with it on fresh machines before updates go out.
• Search off means off: When you turn web search off, the assistant, the specialists it calls and the model itself no longer search the web or open pages, including tools the assistant turns on during a reply.
• Credits for every person: Administrators see each person's plan, credits left and credits used this month on the Statistics page, and can grant credits or change a plan from there.

Version 1.7.43

September 26, 2026.

• Your documents beside the chat: Documents the assistant saves in a conversation now appear in My Documents with the rest of your documents, and open in a panel beside the chat, so you no longer need the dashboard to find them.
• Helpers on the Axelera tiers: Build's lead agent can hand work to helpers on Axelera Mercury, Venus or Earth 1.0, never above the chat's own tier, and the Agents tab shows the tier each helper runs on.
• The Wingman look in chat: The chat's sidebar, browser tab, app icons and loading screen now carry the Axelera Wingman wordmark and the round Wingman icon.
• A steadier dashboard: The dashboard stays responsive while a knowledge search waits on a slow database, instead of dropping out for a minute at a time.

Version 1.7.42

September 23, 2026.

• Helper agents in Build: Build can hand parts of a larger task to helper agents that work side by side and report back, and the Agents tab in the side pane lists each one while it runs. Up to three run at once by default, each on the chat's own model, and the Helper agents setting chooses how many a chat may run, from none to six.
• One bar above Build: The Build actions (the side pane, New chat, Tasks, History and Settings) now sit on the pane's own title row beside the Axelera Wingman icon, in every layout, so the chat has one bar above it instead of two.
• One row per chat, a calmer transcript: Opening an older chat from History no longer copies it or moves it to the top, and a chat moved to another provider keeps its row. A slow turn shows one live notice that clears when the answer resumes, and finished commands fold into one row you can open.
• Long answers stay connected: A turn the model spends a long time thinking about stays connected until the answer starts, instead of ending in a timeout page and a run of automatic retries.

Version 1.7.41

September 22, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.40

September 19, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.39

September 19, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.38

September 18, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.37

September 18, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.36

September 18, 2026.

• Attachments in Build: Attach files, folders and screenshots to a Build message and they go with that message: the chips leave the message box when you send, and the sent message shows what it carried. Pictures reach the model as pictures, so you can attach a screenshot of a design or an error and ask about it.
• Paste a screenshot straight into the chat: Paste an image from the clipboard, drop one in from outside the editor, or paste a file you copied in your file manager. A screenshot with nothing typed is a complete message, and pressing Enter right after a paste still sends the picture.

Version 1.7.35

September 18, 2026.

• Background commands and a Tasks pill: Build can start a long command in the background, keep working while it runs and read its output when it matters. A pill above the message box shows how many commands are running and for how long, and the Tasks panel lists each one with Open terminal and Stop, so nothing keeps running unseen.
• Web search in Build: Build can search the web and read a page when the knowledge base does not hold the answer. Each call is charged to your credits only when it runs.
• A clearer Build chat: The Run button now says what it did (Ran, Pasted or Copied), and a one-line plain block is pasted into the terminal for you to review before Enter. Insert puts a reply's code at your cursor, Add Selection to Build sends the editor selection to the chat, a running command block sweeps while it works, and the knowledge base approval is a short link instead of a long address. Kimi chats now appear in Build history.
• Safer commands: Build asks before it runs sudo on another machine over SSH or starts a container with host-level access, and pauses GitHub and Hugging Face reach when a system-wide setting could put a connection token into the commands the agent runs.

Version 1.7.34

September 17, 2026.

• Build runs your commands: Build can now run commands in your integrated terminal and read what it shows, so you no longer paste commands by hand. Code blocks get a Run button, routine commands run without a prompt in Auto mode, and anything that needs administrator rights always asks first.
• GitHub, Hugging Face and your own tools in Build: Connect GitHub and Hugging Face from Home so Build can look up repositories, issues, pull requests, models and datasets. Tokens are checked once, kept in secure storage and never handed to the commands Build runs. Build sessions on the Axelera AI provider can now also use the tools from your own MCP servers.
• Security hardening: Sign-in, the chat assistant, the dashboard and the API close the findings of the latest security review, and hosted Wingman project and task tools now act only with your own sign-in.

Version 1.7.33

September 17, 2026.

• Build runs your commands: Build can now run commands in your integrated terminal and read what it shows, so you no longer paste commands by hand. Code blocks get a Run button, routine commands run without a prompt in Auto mode, and anything that needs administrator rights always asks first.
• GitHub, Hugging Face and your own tools in Build: Connect GitHub and Hugging Face from Home so Build can look up repositories, issues, pull requests, models and datasets. Tokens are checked once, kept in secure storage and never handed to the commands Build runs. Build sessions on the Axelera AI provider can now also use the tools from your own MCP servers.
• Security hardening: Sign-in, the chat assistant, the dashboard and the API close the findings of the latest security review, and hosted Wingman project and task tools now act only with your own sign-in.

Version 1.7.32

September 17, 2026.

• A clearer Build window: Build shows verification results with star icons, folds a run of commands into one block, marks work in progress with the same thinking animation as the web chat, lays out knowledge and web results as cards, and colours code with the ayu-dark theme.
• Sign-in recovers by itself after an outage: When the authentication service has a short outage, knowledge search and dashboard sign-in now recover within seconds of it coming back, without waiting for a restart.
• Tighter tool handling for Build on the Axelera AI provider: The hosted service now runs only knowledge searches for a Build session on the Axelera AI provider. Project and task tools from the Wingman knowledge server are paused there until they move to the desktop app and its approval rules.

Version 1.7.31

September 17, 2026.

• Long Build turns finish on the Axelera AI provider: A Build session on the Axelera AI provider no longer loses a turn that takes more than a minute to answer. The hosted service keeps the connection alive while the model works, so long file writes and multi-step knowledge lookups finish instead of reconnecting until they fail.

Version 1.7.30

September 16, 2026.

• Build mode reaches the knowledge base on the Axelera AI provider: Knowledge searches made from a Build session on the Axelera AI provider are answered again. They had been refused by the hosted service for every account, so answers came only from the pre-attached excerpts; the service now signs those searches with the account behind the Build session.
• The knowledge tools stay connected: A Build session waits the whole browser approval instead of racing it, remembers a good sign-in for a few minutes instead of re-checking every turn, tells you when an approval did not finish without asking you to reconnect, and gives the Claude and Kimi engines the same knowledge instruction as the others.

Version 1.7.29

September 16, 2026.

• Build mode reaches the knowledge base again, and says so when it cannot: A Build session now repairs a lapsed knowledge sign-in once, at the start of the session, instead of quietly answering without the knowledge base. When the knowledge tools really are unavailable the assistant is told so and answers from its own knowledge with that stated, and Kimi sessions receive the same skills as the other engines.
• Answers quote whole documentation sections: Knowledge searches now return the neighbouring passages around each hit, so a flag list or a command reference is no longer cut mid-table, and the tool names the desktop engine uses are recognised, so its evidence is never dropped. File paths in Build replies are clickable, code is highlighted, and every edit shows a summary of the change.

Version 1.7.28

September 15, 2026.

• Earth answers that search the knowledge base finish again: Axelera Earth 1.0 sometimes stopped after announcing a knowledge base search, with no answer and no error. The search now runs and the answer arrives, and if a turn ever does fail, the conversation shows the error instead of a reply that never finishes.

Version 1.7.27

September 15, 2026.

• Visits are counted without identifying anyone: Wingman now counts how often each surface is opened per day: the web chat, the sign-in pages and both dashboards. No account or device is recorded with the count, and the admin statistics page shows the last seven days per surface.

Version 1.7.26

September 15, 2026.

• A tool that stops answering no longer freezes the chat: When a tool the assistant called, such as the knowledge base search, stopped answering, the reply stayed empty for good and nothing told you why. Every tool call now has a ninety second limit; when it runs out, the assistant is told and answers with what it has.
• The pricing page answers at its own address: chat.wingman.axelera.ai/pricing returned a 404 while the same page under a language prefix worked. The address is routed correctly now, and a test keeps every public page on that list.

Version 1.7.25

September 14, 2026.

• Assistants stay signed in to the Wingman MCP server: Connecting an AI assistant to the Wingman MCP server used to ask you to sign in again about an hour after you approved it. The server now requests a refresh token with the authorization, so a session renews itself for as long as the assistant is in use. If a client still shows the old behaviour, remove and add the server once.
• Every authorization screen is Wingman's: The pages an assistant sends you to now name Axelera Wingman as the authority, say which application is asking and what each permission allows, and end with Wingman authenticated, in every language the product ships.
• Agent Dev gets more of the window and a quieter transcript: Agent Dev opens with four fifths of the window and the dashboard beside it, and it keeps working through a long task instead of announcing a handoff and starting over after each context checkpoint. Commands show as one line naming what ran, engine housekeeping notices stay out of the conversation, and a tool server that stops responding while connecting no longer holds a turn open. A command that stays quiet is no longer interrupted after five minutes, Send now on a queued message no longer stops the session, and a forced stop keeps the conversation for the next message.

Version 1.7.24

September 13, 2026.

• Plans and prices, without signing in: A public pricing page at /pricing now states every plan, what a credit buys, the welcome credits and the top-up blocks, and it reads without an account. Each plan opens a short form that reaches Axelera directly, because paid plans are arranged with us rather than bought at a checkout.
• Credits pages that say what actually happened: The Credits card shows the credits used this period and leaves spent welcome credits out of the gauge, so an untouched month reads full. The card, the banner and the documentation now agree about what renews, what never expires, and who sets a seat monthly cap. Concurrent turns and the one-turn overdraft are held inside that cap, a seat removed from a shared pool keeps credits of its own for the rest of the month, and the pool view has its per-tier breakdown back.
• The desktop sign-in page looks like the product: The page the desktop app hands you during sign-in now carries the Axelera Wingman wordmark, colours and typeface, in matching dark and light themes, instead of unstyled browser defaults.

Version 1.7.23

September 13, 2026.

• Keep hardware guidance in context: Chat preserves relevant uploaded knowledge and can continue an authorized search when the first excerpts do not cover the requested model or hardware. Guidance keeps target-specific compatibility evidence separate without exposing internal source locations.

Version 1.7.22

September 11, 2026.

• Continue longer funded conversations: The per-call credits cap limits answer length instead of rejecting a paid turn solely because of that cap when your available credits can fund the request. The Credits button opens current-period usage, remaining credits and reset information.
• Read Voyager skill references in Chat: Chat agents can read bundled Voyager guides for target-specific model qualification, input-media selection and application measurement. Reading a guide does not itself execute a model or helper program.
• Keep large knowledge results useful: Large knowledge-search results retain ranked evidence, useful previews and retrieval status within the model context limit. Long agent sessions also have more request headroom on the hosted compatible endpoint.
• Save downloadable files from Chat: Save generated scripts and other text files in My Documents and sync them to linked projects with the filename and contents you requested, without starting Cloud Sandbox. Running code still requires an execution environment.
• Receive supported Linux updates: Update eligibility follows the supported updater compatibility floor, with clearer manual-install guidance when needed. Waiting offers refresh when automatic checks are enabled; manual and startup-only preferences and paused-channel messages are preserved. Linux release checks validate fresh installation and upgrades on both supported architectures.
• Keep tool-call data intact: Tool calls reject numbers that are too large to represent instead of silently changing those values before a tool runs.

Version 1.7.20

September 10, 2026.

• Tool calls work on every model again: Knowledge-base searches and other tool calls that ended in an error on the deepest tier now complete, whichever model answers.

Version 1.7.19

September 10, 2026.

• Credits are live: Your balance is measured in credits from this release. Every verified account starts with a 5,000-credit welcome gift, Launchpad adds 300 credits a month, and the Credits page shows what each answer used.
• Monthly credits last the whole month: A monthly credit bucket is valid through the end of its calendar month, so the last days of a long month never run empty.

Version 1.7.18

September 10, 2026.

• Sign in on Linux even when no browser opens: The first-run sign-in step opens your browser by itself and offers Cancel while it waits. If no browser window appears, it offers Open browser again and Copy sign-in link, so the same sign-in can be finished in any browser on the machine instead of waiting at step one.
• Your plan's monthly credits, and a gift to start: Every account receives its plan's monthly credits, starting with the free plan. Every new account with a verified email address receives a one-off gift of 5,000 credits, and the same plan names, prices and monthly credit figures now appear on every surface.
• Mercury chat is free of credits: Axelera Mercury chat costs no credits on any plan, under one fair-use ceiling that is the same for everyone: 2,000 questions a day per person, resetting at 00:00 UTC.
• Per-seat caps and alerts for pooled plans: An account administrator on a pooled plan can cap what one seat spends each month and is told once a month when a seat approaches its cap. A run that is one turn from finishing may draw slightly below zero once a day instead of ending on a partial answer, repaid by the next credits.
• Answers that finish, and credits charged right: A long Axelera Earth 1.0 answer stays alive while the model is still thinking, background requests such as conversation titles stay on the cheapest tier, and concurrent turns are charged against the credits an account actually has left.

Version 1.7.17

September 8, 2026.

• A stronger top tier for hard questions: The hardest questions can be answered by a stronger set of reasoning models than before, chosen per question rather than per conversation. Everyday questions keep going to the same fast models, so simple answers stay quick.
• Credits everywhere you see usage: Usage and the message you get when you run out are stated in credits, with no currency anywhere. What a request cost, what you have left, and what a plan includes are now the same unit.
• Your monthly credits, and a gift to start: Every plan now carries its own monthly credit allowance, and existing accounts receive a one-off launch gift on top of it. Both appear on the Usage page the first time you open it after the update.
• Better answers about code you upload: A question about a file you uploaded now retrieves the whole implementation instead of a fragment of it, so answers about your own code follow the real structure.

Version 1.7.16

September 7, 2026.

• Search keeps every ranked result: A knowledge question comes back with the whole ranked set of matching documentation instead of collapsing to a single passage, so answers have more to work from. Search settings saved for a deployment also reach every part of the service within a few minutes, with no restart.
• Steadier crawls, cleaner code samples: A crawler failure no longer interrupts the service around it: the crawler recovers on its own while chat and knowledge answers keep running. Code examples taken from crawled pages also keep their line breaks and exact command syntax, so a command copied out of an answer runs as written.
• Usage charged at published rates: One of the models behind Axelera Auto recorded usage about a quarter above the rates published for it. Its rate card now matches those rates, so the credits a turn spends follow what the model really costs.

Version 1.7.15

September 7, 2026.

• Knowledge answers keep their evidence: A question that names a symbol, file or model the index does not know no longer comes back empty. The best matching documentation stays in the answer, and the answer says which names were found and which were not.
• Search by meaning, ready to switch on: Hosted deployments can search the documentation by meaning again once it is enabled for the deployment, and the reranker that orders the results now ships inside the service, so enabling it no longer stalls the first requests. Until it is enabled, search says plainly that it is matching text only.
• Steadier routing and answers: The routing lane is chosen from your question before retrieved documents are added, so a product question stays on the product lane. Answers on reasoning models no longer fail before the model is reached, newer models keep answering, and a model that reasons and then produces no text never returns a blank answer.

Version 1.7.14

September 5, 2026.

• Mercury is free for everyone: A Mercury answer never uses your credits any more. Every account keeps its monthly credits, and they now go to Venus and Earth only.
• Credits, not dollars: The Usage page now shows what you actually have: credits used today and this month, credits remaining, and a per-request table in credits. No currency anywhere.

Version 1.7.13

September 5, 2026.

• Wingman wears its own mark: The title bar, the update panel and the empty editor now show the Axelera mark. The blue editor icon that showed through in earlier versions is gone, and the build refuses a package that still carries it.

Version 1.7.12

September 5, 2026.

• Continue a project without a popup: Bringing a cloud project onto this device now opens Agent Dev straight away, and so does Fix with Wingman after a failed Voyager SDK update. A Port to Axelera link is confirmed in a compact dialog that always fits the screen, with Show full prompt to read everything first.
• Hardened answers and rendering: Knowledge questions stay responsive to hostile input, internal diagnostics never reach a project or MCP answer, unclosed math markup no longer stalls a conversation, and the obsolete public development proxy is gone.

Version 1.7.11

September 5, 2026.

• Updates wait for you to close the app: An update never changes the installed app while a window is open. Wingman asks you to restart when it is ready, and a session that stays open after an update is told to restart instead of showing a black page.
• Voyager SDK updates that finish the job: The Update button now runs the SDK update itself, tells you why it stopped, and offers to keep your local edits, hand the fix to Wingman, or show the changes.

Version 1.7.9

September 4, 2026.

• Chat commands for long conversations: Type /compact to condense a long conversation, /status to see the model and how much context it has used, /new to start fresh, and /help for the list. Axelera AI conversations also condense themselves before the context window fills.
• Every message speaks as Axelera AI: Mercury, Venus and Earth introduce themselves as Axelera AI models, and the engine notices behind them are gone or reworded as Axelera Wingman.
• Nothing internal reaches an answer: Knowledge answers, support links and error reports no longer carry internal repository names, paths or addresses, and a repository-wide check keeps them out.

Version 1.7.6

September 3, 2026.

• The Axelera AI models answer for every account: Mercury, Venus and Earth answer from the desktop app for every signed-in account. The hosted endpoint no longer refuses the call on a permission no role could hold.
• A first Axelera turn needs nothing from you: The app fetches its Axelera AI endpoint key when you sign in, the Axelera Wingman tools approval no longer blocks a model turn, and the Linux package brings its own engine.
• Every message names Axelera Wingman: Readiness, start failures and update notices speak of Axelera Wingman and Axelera AI, and desktop notifications carry the Axelera Wingman icon.

Version 1.7.5

September 3, 2026.

• A first Axelera turn needs nothing from you: The app fetches its Axelera AI endpoint key when you sign in, the Axelera Wingman tools approval no longer blocks a model turn, and Mercury, Venus and Earth answer on a fresh install without any setup.
• The package brings its own engine: The Linux package bundles the pinned, checksum-verified agent engine, so nothing has to be installed beside Axelera Wingman.
• Every message names Axelera Wingman: Readiness, start failures and update notices speak of Axelera Wingman and Axelera AI, and desktop notifications carry the Axelera Wingman icon.

Version 1.7.4

September 3, 2026.

• The Axelera AI models answer again: Mercury, Venus and Earth start a session, answer, and can be switched between turns. The provider carries the name current Codex tools require, the app talks to a hostname that exists, and the hosted chat serves the endpoint.
• The update unit runs on every kernel: Installing an update no longer fails with a privilege error on the evaluation kit's kernel.
• Failures name the product: A session that cannot start reports as Axelera Wingman, and the update dialogs are titled Axelera Wingman.

Version 1.7.3

September 2, 2026.

• Every surface runs 1.7.3: The hosted chat service, the dashboard and the desktop app report the same version, so the version you see in the app, on the dashboard and in Chat agree.
• One place for your credits: The credits shown in the app are the credits you have. The first-run lineup slide no longer states a sign-up amount, and the message usage card shows dollar rates per million tokens instead of a second meaning of credits.
• In-app updates install on partly upgraded Ubuntu hosts: Carried from 1.7.2: the updater asks apt to change Wingman and its missing dependencies and nothing else, so a pending system upgrade that renames a package no longer fails the install.

Upgrade path (v1.7.3)

Version 1.7.2

September 2, 2026.

• The hosted chat service runs the same version as the desktop app and dashboard: Version 1.7.1 aligned the dashboard with the desktop app. This release brings the hosted chat service to the same number, so every surface you use reports 1.7.2.
• Release notes open inside Wingman: Choosing Release Notes from the update menu now opens the Wingman changelog in Docs, with the same highlights you see here, instead of the list of packages on GitHub.
• In-app updates install on partly upgraded Ubuntu hosts: The updater now asks apt to change Wingman and its missing dependencies and nothing else, so a pending system upgrade that renames a package no longer fails the install with "The package installer did not complete successfully".
• Agent Dev shows your remaining credits: The credits chip beside the model picker in Agent Dev now shows the balance of the account your endpoint key bills, refreshed after every settled turn. Desktops on 1.7.0 or later pick it up within ten minutes or on their next start.

Upgrade path (v1.7.2)

Version 1.7.1

September 2, 2026.

• The hosted dashboard and chat run the same version as the desktop app: Version 1.7.0 shipped the desktop app first. This release brings the hosted dashboard and the chat service to the same version, so every surface you use reports 1.7.1.
• Release notices render completely in Chat and Docs: The notice that closes a release entry in the changelog and on the Docs release page now shows its heading and text in full.

Upgrade path (v1.7.1)

Version 1.7.0

September 2, 2026.

• The Linux app launches on Ubuntu 24.04: Version 1.6.11 does not start on a stock Ubuntu 24.04 install: its package is missing the sandbox permissions and security profile that 24.04 requires. Installing this version fixes it, and upgrading over a much older install now works too, where the installer previously refused.
• Credits are visible in the app: Your remaining credits and usage now appear in settings, with a chart of what you have spent and the tier you use most. Agent Dev shows the same balance inline beside the model picker.
• Voyager SDK questions get answers: Product questions reaching the API on the Venus and Earth tiers were answered without product grounding, so "Voyager SDK" was treated as ambiguous. Those lanes now resolve it to the Axelera Voyager SDK instead of asking you to clarify.
• Seven security advisories resolved: Raises transformers, pypdf, browserslist and query-string past published advisories, covering one arbitrary-file-write finding and six denial-of-service findings.

Upgrade path (v1.7.0)

Version 1.6.12

August 30, 2026.

• Billing checks follow the managed model catalog: Release billing checks validate every enabled managed-model canary target instead of relying on a fixed provider list. Session, deployment, model identity, and billing receipt checks remain mandatory.
• OpenAI requests keep routing metadata internal: OpenAI Responses requests omit the internal provider routing field while preserving model selection, streaming, and input-token conversion.
• Corrective releases preserve the original recovery boundary: A corrected, signed descendant release can recover Chat from a finalized zero-capacity state only when the original immutable recovery boundary remains intact. Changed boundaries or release identities remain blocked.

Prepared notes are not a rollout announcement (v1.6.12)

Version 1.6.11

August 30, 2026.

• Releases keep their progress while development continues: A release keeps its reviewed source, version, and verified artifacts when newer changes land. Normal development no longer restarts an admitted release or discards its successful checks.
• Continuity keeps the safety checks intact: Release checks still stop changed or revoked candidates, rewritten source history, lost deployment ownership, and attempts to replace a newer deployment. Independent sign-in, Chat evaluation, Downloads, and signed updater verification remain required.
• Image conversations use a vision-capable route: Axelera Auto selects a vision-capable route for image conversations and keeps a backup route for every lane.

Prepared notes are not a rollout announcement (v1.6.11)

Version 1.6.10

August 30, 2026.

• Release checks measure visible progress accurately: Chat release verification now times the first rendered assistant activity separately from the first final answer. Status, tool, and approval progress can prove response liveness, while correctness and abstention checks still score only the customer-visible final answer.
• In-flight checks remain stable while messages scroll: The browser evaluator follows stable message identities through virtual-list recycling and verifies rendered visibility in headless Chromium, preventing hidden or recycled interface content from producing a false release result.

Prepared notes are not a rollout announcement (v1.6.10)

Version 1.6.9

August 29, 2026.

• In-domain answers can use one retrieval pass: A default-off release flag can route confident Voyager SDK questions through one source-grounded retrieval pass, providing cited excerpts without requiring a multi-step tool loop while preserving the existing path when evidence is weak.
• Fresh Agent Dev workspaces start on Axelera Earth: When the Axelera provider is available, a fresh Agent Dev workspace now starts with Axelera Earth 1.0. Existing saved configurations are preserved, and environments where the provider is hidden keep their established Claude default.
• Knowledge readiness checks the complete result pool: The production knowledge reader now verifies every retained site result against the real candidate-pool size, so a healthy content-aware index can be promoted without weakening its quality or vector-evidence checks.
• Crawler browsers stay inside the worker: The hosted API no longer starts an unused Chromium process. External-site crawling remains isolated in the dedicated, credential-restricted crawler worker with its existing network and runtime safeguards.

Prepared notes are not a rollout announcement (v1.6.9)

Version 1.6.8

August 29, 2026.

• Knowledge search returns better-matched evidence: Wingman knowledge search now keeps results from different sources distinct, applies reranking confidence correctly, and reports bounded degraded search honestly instead of stalling a response. New and refreshed SDK code in supported languages is indexed by structure for more precise examples.
• Router classification stays bounded: Axelera Auto keeps classification within the same timeout, cancellation, metering, and health lifecycle as the answer it selects, preventing a stalled or ambiguous classifier from causing a second paid dispatch.
• Simple turns answer on a faster lane: Plain greetings, thanks, and acknowledgements now skip tool setup, making trivial turns faster on every tier. Once a conversation uses tools, later turns keep them available so ongoing work remains consistent.
• Agent Dev shows full Axelera model names: The Agent Dev model picker now presents Axelera Mercury 1.0, Axelera Venus 1.0, and Axelera Earth 1.0 by their full product names while preserving existing model selections.
• Final answers are checked on what you see: Release checks now keep the visible final response separate from reasoning, status and error UI, tool cards, and approval controls, preventing a correct evidence-aware abstention from being rejected or a blank response from passing on interface text.

Prepared notes are not a rollout announcement (v1.6.8)

Version 1.6.7

August 29, 2026.

• Tool conversations finish reliably: Axelera Chat now preserves explicit completion proof after GPT usage data, reports incomplete provider responses as errors, and keeps streamed tool arguments correlated through multi-step conversations.
• Background checks stay out of the way: Automated extension tests and authentication-status checks use non-interactive paths, keeping routine verification from opening desktop windows or requesting browser approval. Real sign-in still requires your explicit action.
• Consecutive tool approvals stay ordered: When several Chat tool calls need review, the next approval remains disabled until the current tool resume finishes. Other conversations remain interactive, and duplicate execution stays blocked.
• Downloads and updates gate release completion: A production release must verify both Linux packages, the exact version and download buttons on Chat Downloads, and the signed updater target before it can be marked complete.
• Custom-model workflows stay release-aware: The desktop carries 16 release-aware skills and six reusable helpers for Voyager YAML, model recipes, AxScript, and validation workflows across vision, language, recurrent, audio, speech, diffusion, and time-series models.
• Knowledge updates can ship independently: Approved model-porting guidance can be published through an already-compatible hosted reader without rebuilding the app. Publication checks bind the reviewed content and reader revisions separately and recheck reader readiness after import.
• Corpus handling uses the patched NLTK release: The backend resolves NLTK 3.10.3 to close known arbitrary-code-execution and symlink-based file-read vulnerabilities before production publication.
• Production release checks report the real result: Hosted billing verification now runs its deployment identity recheck with the already-validated modern Bash interpreter, preventing an incompatible macOS system shell from being mistaken for production release drift.
• Failed rollouts retain a durable recovery point: Every hosted Chat candidate records and rereads its exact recovery boundary before the first service mutation, including ordinary upgrades that cross a forward-only boundary later in finalization.
• Temporary metadata faults stay distinguishable: Managed-provider release attestation still fails closed, while timeouts, unavailable metadata, and malformed metadata receive a bounded retry and remain distinct from a proven source, task, or image mismatch.

Prepared notes are not a rollout announcement (v1.6.7)

Version 1.6.6

August 29, 2026.

• Tool conversations finish reliably: Axelera Chat now preserves explicit completion proof after GPT usage data, reports incomplete provider responses as errors, and keeps streamed tool arguments correlated through multi-step conversations.
• Background checks stay out of the way: Automated extension tests and authentication-status checks use non-interactive paths, keeping routine verification from opening desktop windows or requesting browser approval. Real sign-in still requires your explicit action.
• Consecutive tool approvals stay ordered: When several Chat tool calls need review, the next approval remains disabled until the current tool resume finishes. Other conversations remain interactive, and duplicate execution stays blocked.
• Downloads and updates gate release completion: A production release must verify both Linux packages, the exact version and download buttons on Chat Downloads, and the signed updater target before it can be marked complete.
• Custom-model workflows stay release-aware: The desktop carries 16 release-aware skills and six reusable helpers for Voyager YAML, model recipes, AxScript, and validation workflows across vision, language, recurrent, audio, speech, diffusion, and time-series models.
• Knowledge updates can ship independently: Approved model-porting guidance can be published through an already-compatible hosted reader without rebuilding the app. Publication checks bind the reviewed content and reader revisions separately and recheck reader readiness after import.
• Corpus handling uses the patched NLTK release: The backend resolves NLTK 3.10.3 to close known arbitrary-code-execution and symlink-based file-read vulnerabilities before production publication.

Prepared notes are not a rollout announcement (v1.6.6)

Version 1.6.5

August 26, 2026.

• Background checks stay out of the way: Automated extension tests and authentication-status checks use non-interactive paths, keeping routine verification from opening desktop windows or requesting browser approval. Real sign-in still requires your explicit action.
• Consecutive tool approvals stay ordered: When several Chat tool calls need review, the next approval remains disabled until the current tool resume finishes. Other conversations remain interactive, and duplicate execution stays blocked.
• Downloads and updates gate release completion: A production release must verify both Linux packages, the exact version and download buttons on Chat Downloads, and the signed updater target before it can be marked complete.
• Knowledge updates can ship independently: Approved model-porting guidance can be published through an already-compatible hosted reader without rebuilding the app. Publication checks bind the reviewed content and reader revisions separately and recheck reader readiness after import.
• Corpus handling uses the patched NLTK release: The backend resolves NLTK 3.10.3 to close known arbitrary-code-execution and symlink-based file-read vulnerabilities before production publication.

Prepared notes are not a rollout announcement (v1.6.5)

Version 1.6.4

August 26, 2026.

• Release-aware custom-model workflows: Wingman skills distinguish Voyager YAML pipelines, model recipes, and AxScript workflows, with guidance for computer vision, language, recurrent, audio, speech, diffusion, and time-series models.
• Reusable model inspection tools: Reuse local helpers to inspect model artifacts, check AxScript environments and entrypoints, discover model surfaces, and record validation observations instead of recreating those steps for each model.
• Content-aware knowledge refresh: Website refreshes can reuse unchanged indexed pages and replace changed content, with reader-readiness checks before refreshed sources are published.

Model support requires validation (v1.6.4)

Version 1.6.3

August 19, 2026.

• Wingman-only update details: The update status now shows the exact authored Wingman release date and no longer labels the pinned Visual Studio Code engine date or commit as Wingman release metadata.
• Authenticated release timestamps: Linux update manifests bind their publication timestamp to the exact versioned release-catalog entry, and the UI hides any target date that is not authenticated.
• Latest downloads remain canonical: The Chat downloads page continues to resolve the immutable public GitHub Latest release instead of relying on deploy-time version pins.

Version 1.6.2

August 19, 2026.

• Wingman release notes inside Wingman: The desktop update status now renders the matching Axelera Wingman release entry from the signed application package instead of fetching similarly numbered Visual Studio Code notes.
• Downloads follow the public latest release: The Chat downloads page resolves the canonical immutable public GitHub Latest release at runtime, and the production canary verifies every supported GET and HEAD redirect before traffic is promoted.
• Fast signed in-app updates: Version 1.6.2 is the first normal title-bar update on the new signed GitHub channel, with explicit Download and Install actions and an automatic verified reopen.

Version 1.6.1

August 16, 2026.

• Dashboard stays connected: The desktop Dashboard now identifies its health checks correctly, so a healthy hosted service no longer leaves Home stuck on Reconnecting.
• Connection status that stays out of the way: A healthy Agent Dev connection is a compact green dot that stays clear of long drafts. Problems expand into a visible Fix now action, and the exact runtime model is shown separately.
• Signed GitHub-only updates: Linux updates use immutable GitHub release assets, separate reviewed signatures, explicit Download and Install clicks, and a protected automatic reopen after the package is verified.

Manual update required from 1.6.0 (v1.6.1)

Version 1.5.0

August 6, 2026.

• Feedback that reaches the team: Dashboard and desktop feedback flows add screenshot choice, diagnostics, consent, and privacy-aware retention.
• More Agent Dev choices: Kimi joins Agent Dev alongside updated Claude and Codex reasoning controls, with clearer tool approvals and reliable chat links.
• Linux release packaging: Release packaging and verification were strengthened for Linux packages. The public GitHub release remains Linux-only; web apps are deployed separately and other desktop or plugin assets are not published there.

Version 1.4.1

July 17, 2026.

• Onboarding, redesigned: Both onboarding flows now use the Axelera gold and black theme with hardware-focused guidance, and offer a safe path to classic setup when the model is unreachable.
• New chat shell: The chat shell picks up the Axelera Wingman wordmark, a bottom profile block, a Library tab, and an Ask Axelera Wingman composer prompt.
• Knowledge stays fresh: A daily sync re-indexes the public Voyager SDK at its latest published version and re-crawls the full docs.axelera.ai site, so answers stay current without any action from you.
• Desktop sign-in fixed: The desktop login screen now offers one-click customer SSO alongside employee SSO, matching the web dashboard.
• Security hardening: An unauthenticated internal webhook is removed, and three high-severity MCP server advisories are fixed: session requests are verified, task access is isolated per client, and WebSocket origins are validated.

Version 1.4.0

July 15, 2026.

• Chat answers start faster: Simple and tool-using requests start responding in seconds, and the waiting indicator shows rotating progress phrases instead of a frozen label.
• Open in Agent Dev: Port to Axelera project pages gain a one-click Open in Agent Dev launch as the primary action, with Copy prompt as the manual alternative.
• Linux-first packages: The release ships as Linux .deb packages for amd64 and arm64, with verified release metadata for exact-version downloads.
• Docs refresh: In-app documentation gets current screenshots, autoplaying walkthrough clips, and video tutorials covering sign-in, chat, Port to Axelera, and Agent Dev runs.
• Sign-in reliability: One-click customer and employee sign-in, logout, and sign-in method switching work reliably again, and privileged actions stay protected by MFA.

Version 1.3.1

July 14, 2026.

• Skills for Voyager SDK 1.7.0: Wingman skills update for Voyager SDK v1.7.0 with SDK install and board-health repair guidance, and the Axelera Auto chat agent routes work to the skills by default.
• Adaptive thinking budget: Simple questions get faster answers in Axelera Chat with an adaptive thinking budget, and chat stays responsive when tools fail instead of hanging.
• Tools stay connected: Expired tool credentials now refresh and retry transparently, so tool calls stop failing with authorization errors mid-session.
• Agent Dev stability: Full access works reliably by default, stale provider and SSO connections recover on their own, and the workspace returns to a 50/50 split.

Version 1.3.0

April 14, 2026.

• Marketplace routers: New publisher profile and become-publisher flows are live.
• Rate limiting: Per-user API rate limits are enforced server-side.
• Auth hardening: Session handling and the OIDC provider are hardened.

Version 1.2.0

April 7, 2026.

• Erasure cascade: Account deletion cascades to user data in the database.
• SSO improvements: Entra ID SAML SSO supports customer tenants.
• VS Code integration: Axelera Chat is available in the VS Code extension.

Version 1.1.0

March 31, 2026.

• Agent runtime: Multi-agent orchestration supports parallel task dispatch.
• MCP plugin support: Install and manage MCP plugins from the plugin store.
• Mobile layout: The chat experience adapts to mobile browsers.

Version 1.0.0

March 17, 2026.

• Core chat: Chat launches with authentication and agent workflows.
• Agent builder: Create agents and connect skills from the built-in catalog.

Release notes in the product

You do not need this page open to follow releases. The same notes reach you in two places inside the product: a changelog dialog in Chat, and the update pill in the desktop title bar.

1. Open the changelog in Chat

   Click the ? help button at the bottom-left of the chat sidebar and choose Changelog. A dialog lists each release with its version, date, and notes, newest first — scroll back as far as you like. The same menu holds Docs, Feedback, and Community, so everything about the product lives behind one button.

2. Watch the desktop title bar

   The title bar shows a neutral updater dot until the first signed channel check succeeds, then a compact green dot while Wingman is current. When an eligible desktop release is out, it expands to Download update. Click it to fetch and verify the release. Save your work before clicking Install update: Linux asks for administrator authorization, then Wingman closes before application files change and reopens the verified installed version automatically.

3. Review release notes before and after

   Before you download or install, hover the indicator to review the incoming version and its release notes. After Wingman reopens, the title bar shows New in <version> so you can review what changed and open the full release notes.

Title bar update states

One-time channel bootstrap

If something in a release does not behave the way its note promises, send it straight back through Feedback in the same help menu — release notes are only useful when they match what you see.