September 2026 release notes
September introduced Status — uptime monitors, incidents, and a public status page — plus a workspace audit log, Closure ticket approvals and recurring tickets from Tasks, simpler Movitera Link enrollment with codes, richer remote sessions, inline password generation in Vault and the Vault Extension, a unified Settings layout, Forge AI titles and repository tracking, Work with an agent, a Closure Services catalog, Muse wiki move and archive, Vault password import from a CSV export, Closure archive reasons with optional requester notice, simpler image upload in editors, advanced filters on Forge and Closure, filters drafted from a sentence, and an issue writing helper in the create dialog, plus Closure Changes and AI triage helpers, Forge Designs, richer board filters, Muse diagram support and MCP for designs, problems, and changes, Vault Extension authenticator codes, create-and-link from a design, clearer onboarding exits, group types with leaders for Closure, Muse images in chat with a Status skill, Forge grouping by initiative and cycle delivery meters, Vault password health, Link health alerts into Closure, workspace-required two-factor authentication, and clearer approval and share details.
September highlights
- Status arrived: HTTP uptime monitors, incidents with updates and postmortems, a private overview, and an optional public status page teams can share.
- Closure gained sequential ticket approvals (approval holds and an approver page) and recurring tickets opened from Tasks activity templates.
- The workspace audit log lets administrators review security-relevant activity and export it.
- Movitera Link enrollment codes connect computers without a Movitera login on the device; remote sessions gained clipboard and file transfer, plus automatic administrator input on Windows and full control on Wayland Linux.
- Inventory can attach acquisition documents to assets and keep searchable observations on devices and assets; Muse admins can choose which pool models the team may use.
- Vault lets you generate a password while creating a credential, with the same options as the standalone generator.
- Vault Extension generates and fills passwords on the site you are using, without leaving the page.
- Settings pages share one layout: grouped sections, search, an unsaved-changes bar, nested AI pages, and theme and language on Profile.
- Forge can auto-generate issue and initiative titles when your team turns that on in Settings › AI.
- Issues can track repositories: assign repos, filter the board, register repos by hand, and set a preferred base for coding work; Forge navigation groups Work, Code, Planning, and Integrations.
- Work with an agent prepares a coding handoff from an issue, with team preferences for language, pull requests, comments, and QA.
- Closure Services lets people browse a catalog and open public requests that land in quarantine for review.
- Muse can propose moving or archiving Wiki pages, and editors can move whole Wiki folders.
- Vault imports private login credentials from a password-manager CSV: preview rows, skip duplicates, then import.
- When archiving a Closure ticket, technicians can leave an optional reason and choose whether to notify the requester; the reason appears on the ticket timeline.
- Editors that support image upload open the system file picker and accept drag-and-drop on the issue page, instead of asking only for a URL.
- Forge and Closure gain advanced filters: AND/OR groups, saved views, shareable filter links, and follow on Forge issues. Closure can also filter by solution rating.
- On Forge and Closure, you can describe a filter in one sentence and apply it to the board (available even when the AI assistant is off; rolling out where enabled).
- The Forge create-issue dialog can structure or improve the description in one prompt panel, with a preview you insert or replace; teams can set writing instructions under Settings › AI › Forge.
- Closure Changes gives teams a dedicated workspace for change records alongside tickets and problems.
- Closure AI triage helps classify tickets, surface documentation gaps, suggest related problems, and guide closing notes.
- Forge Designs adds a design board with file links and a message timeline; you can create and link an issue from the design picker.
- Board filters gain Me/None shortcuts, initiative number search, and people photos in pickers; Profile can lock display name where your workspace requires it.
- Muse renders Mermaid diagrams in Wiki and related surfaces, accepts images in chat, can use a Status skill when enabled, and Muse MCP can work with designs, problems, and changes.
- Vault Extension supports authenticator (TOTP) codes and split OTP fields on sites that ask for them separately.
- Onboarding lets people exit or skip every step instead of getting stuck mid-tour.
- Group types let admins structure groups (for example Company, Branch, Department), assign leaders, filter Closure by type, and backfill older tickets.
- Vault password health checks credentials for leaks and weak passwords when your company turns it on in Settings › Vault.
- Link health alerts can open Closure tickets when a device disk is nearly full or a drive is failing.
- Required two-factor authentication lets a workspace require 2FA on every action, with enrollment and verify gates on web and mobile.
- Forge cycle delivery shows throughput and per-developer completion on the cycle Analysis cards, and you can group issue and design boards by initiative.
Availability
Availability depends on your plan, your role and permissions, and enabled modules. Status, the audit log, Link enrollment, and Muse model controls need the matching module and admin permissions. Public status pages are optional and configured per team. Inline password generation needs Vault. Extension generation needs the Vault Extension installed in the browser. Settings changes apply to everyone with access to Settings. Forge AI titles need Forge and a team manager to enable the flags under Settings › AI › Forge. Repository fields, the Repositories page, promotion stages, and deployment previews need Forge (and a connected GitHub integration where those actions apply). Work with an agent, agent prompt settings, and the issue writing helper need Forge. The classic create-issue form is a per-user Profile opt-in. Advanced filters and saved views need Forge or Closure. Sentence filter draft may be off for some workspaces until rollout completes. Closure Services, public requests, and archive reasons need Closure. Muse wiki move, archive, and folder moves need Muse and Wiki. Vault CSV import needs Vault and a signed-in user with second-factor auth; imports create private credentials. Image file picker and drop need a surface that already supports image upload. Closure Changes, AI triage helpers, documentation-gap panels, and closing-note guidance need Closure (and AI features where those helpers are enabled). Forge Designs, design-file links, design timelines, create-and-link from a design, group-by-initiative, and cycle delivery meters need Forge. Me/None filter shortcuts, initiative number search, and people photos need Forge or Closure as shown in each board. Profile name lock follows workspace policy. Mermaid diagrams need Muse/Wiki surfaces that render markdown. Muse chat images, Status skill, clearer module availability messages, and model-usage labels need Muse and matching Settings › AI / Muse controls. Muse MCP for designs, problems, and changes needs Muse and an MCP client with access. Vault Extension TOTP/split OTP needs the Vault Extension installed. Onboarding exits apply to the product onboarding flow. Group types, leaders, per-type Closure filters, My team tickets, and apply-to-past-tickets need admin or manager access to Settings › Groups and Closure where tickets carry those groups. Vault password health needs Vault plus a company opt-in under Settings › Vault (off by default). Link health alerts need Link and an admin or inventory manager who can edit Settings › Link (off by default). Workspace-required 2FA needs an organization admin, and members must enroll or verify before continuing. Per-stage tested-issue gates need Forge repository promotion stages. Live codes on one-time Vault shares need Vault sharing. Approval timeline detail needs Closure approvals.
September 24-29, 2026
- Closure adds a Changes workspace so teams can track change records next to tickets and problems.
- Closure AI helpers can triage tickets, call out documentation gaps, suggest related problems, and guide closing notes with a checklist where enabled.
- Approval messages on a Closure ticket timeline now show what was approved, not only who decided.
- Forge Designs: a design board, links to design files, and a message timeline on each design. From the design picker you can create an issue and link it in one step.
- Forge and Closure filters add Me and None shortcuts; initiative search matches initiative numbers; people pickers show photos. Profile can lock the display name when the workspace requires it. Shortcuts such as View in Issues from cycles, initiatives, and repositories seed the advanced filter when that mode is on.
- Forge Issues and Designs boards and lists can group by initiative (off by default, remembered per team and page).
- Cycle Analysis cards for Development and Delivery show throughput and per-developer completion as a flow meter, including how this cycle compares with usual pace.
- Repository promotion stages can each require a tested issue before promoting, instead of one team-wide toggle covering every stage.
- Muse Wiki and related markdown surfaces render Mermaid diagrams. Muse MCP can list and work with designs, problems, and changes for connected agents.
- Muse chat accepts images (attach, paste, or drag-and-drop). Settings › Muse adds a Status skill, more approval actions by module, and Activate all / Deactivate all for skills. AI settings show where each pool model is used and what blocks it; Muse explains when a module is unavailable and who can turn it on.
- Vault Extension can fill authenticator (TOTP) codes and handle split one-time-password fields on sites that separate them from the password.
- One-time Vault share pages show a live authenticator code for shared credentials that include TOTP, matching the credential view.
- Product onboarding offers exit and skip on every step so people can leave the tour without finishing it.
- Settings › Groups supports group types (with Company / Branch / Department presets): one-per-person and required rules, module gates for Closure, Wiki, and Vault sharing, and group leaders. Closure ticket pickers and filters follow Closure-typed groups (including none of this type). Group leaders get a My team tab in My tickets. Admins can apply a type's current membership to past tickets (fill or replace, open or all, with preview and confirmation).
- Vault password health (opt-in per company under Settings › Vault): a Password health page lists leaked and weak passwords, with search, attention views, and recheck; credential detail shows the same findings.
- Link health alerts (opt-in under Settings › Link): a nearly full disk or a failing drive on a Link device can open a Closure ticket, with thresholds, categories, default requester, and a confirm preview before enabling.
- A workspace can require two-factor authentication on every action. Admins turn it on under Settings › Workspace; members who need to enroll or verify are gated on web and mobile until they complete 2FA.
September 20-23, 2026
- Issue and peek editors that support image upload open the system file picker from the picture control and slash image action, and accept drag-and-drop onto the editor card, instead of prompting only for a URL.
- Forge and Closure boards and lists support advanced filters: nested AND/OR conditions, type-aware value pickers, saved filters you can rename and reuse, and shareable filter links. Quick filters seed the advanced tree when you switch modes. Forge issues can be followed from the peek and detail headers. Closure advanced filters include solution rating. People who prefer the older list toolbar can keep it in Profile preferences.
- On Forge and Closure, describe a filter in one sentence and apply it to the active board or list. The control stays available even when the AI assistant is off. Fields the draft could not bind are called out so you can finish them by hand. Rolling out where enabled.
- New Forge create-issue dialog: one prompt panel to structure or improve the description (including structure-without-rewriting and keeping a single language), preview the result, then insert below or replace. Teams can set writing instructions under Settings › AI › Forge.
- When attaching a pull request to an issue, the picker lists pull requests from that issue’s repositories first, newest first.
September 17-19, 2026
- Forge roles include Designer and Project manager on issues and related flows.
- Settings › AI › Forge: team-wide agent prompt language, pull-request and QA instructions, and comment style.
- Linked pull requests on an issue can open a GitHub deployment preview when one is available.
- Repository promotion stages show where a pull request has landed, with landing markers and a development detail view.
- After you create an issue, ticket, or similar record, the success toast shows the code with copy and open actions.
- Wiki editors can move a whole folder (including across spaces) without breaking uniqueness rules.
- Repository detail page rebuilt with richer profile fields (defaults and related settings in one place).
- Forge board and issue links can deep-link an open issue peek.
- After onboarding, new sessions land on an enabled module instead of the profile page.
- Vault: Import on the credentials toolbar opens a three-step flow for a password-manager CSV (pick file, preview rows without showing passwords, import selected). New rows import as private logins; duplicates are flagged and off by default.
- Closure archive: optional Reason and a Notify the requester toggle (enabled only when a reason is present; defaults on). Blank reason archives silently. The reason shows on the ticket timeline. Muse archive proposals offer the same fields. Self-archive does not notify.
September 14-16, 2026
- Forge: leave the title blank when creating an issue or initiative and Movitera generates it in the background. Settings › AI › Forge controls the flags and optional instructions.
- Forge issues carry repositories: set them on create and detail, filter the board (including issues with no repository), open a Repositories registry to add repos manually, and choose a preferred base for coding work. GitHub sync merges matching rows.
- Forge navigation regroups into Work (Issues, Cycles), Code (Repositories, Pull requests, Coding sessions), Planning, and Integrations.
- Work with an agent: prepare a coding handoff from an issue (one-click open), including repository defaults and coding-agent preferences.
- Closure Services catalog and public help surfaces: browse services, open public requests, and review quarantined submissions.
- Profile opt-in restores the classic Forge create-issue form for people who prefer it.
- Muse: approve proposals to move or archive Wiki pages; list folders when choosing a destination.
- Closure ticket create: Create more keeps the modal open, clears title, description, and attachments, and keeps category, requester, customer, priority, and kind.
September 12-13, 2026
- When creating a Vault credential, generate a password in place — length, charset, presets, and patterns stay on the form.
- Vault Extension: generate a password on the current tab, copy it, or fill the password field; advanced options persist; an in-page control appears on focused password fields during signup.
- Settings pages share one layout: groups with headers, sidebar search (also in the command palette), and a sticky bar when you have unsaved changes.
- AI, Closure, and Muse model settings live under Settings › AI as nested pages; WhatsApp Closure auto-confirmation lives under Settings › WhatsApp.
- Profile settings include theme and language choice cards.
- Link duration settings use readable time presets instead of raw seconds.
September 10-11, 2026
- Inventory managers generate Link enrollment codes; computers connect with a code and keep company credentials without a Movitera login on that machine. Link configuration moved into Settings so the Link page focuses on setup and enrollment.
- Full-control remote sessions gained a clipboard and files panel: send or receive text, upload a local file, download a remote file by path.
- Assets accept acquisition documents (invoice, PO, receipt); device and asset observations can be edited and searched from the lists.
- Attachment previews follow the app theme and open PDF and text files in place (Word, Excel, and TIFF still download).
- Moving a Closure ticket to In progress self-assigns it to you on the board and ticket page.
- Ticket headers and cards distinguish the requester from who opened the ticket.
- Closure dashboard group filters support Any (OR) or All (AND) across selected groups.
- Ticket conversation loads the latest events first and can page into older history.
- Settings › Members opens each person in a detail preview so admins can review and change groups without leaving the list.
- Settings › AI lets admins choose which shared-pool models Muse may use for the team.
September 8-9, 2026
- Workspace audit log: browse recent security-relevant events, open related records, and export CSV.
- Tasks activities can open recurring Closure tickets from a ticket template, with occurrence tracking on the dashboard.
- Forge issue filters match Closure: multi-select type, assignee, and initiative, with assignee avatars and a collapsible Filters bar.
- Approved Windows remote sessions can reach elevated apps with automatic administrator input (no extra UAC loop for that session).
- Linux remote sessions can use hardware H.264 encoding when the machine supports it.
September 5-7, 2026
- Status: create HTTP monitors (method, interval, thresholds, test-before-save), pause or hide them, open and update incidents, and publish an optional public page.
- Monitor detail shows latency history and an event timeline; incident cards spell out how long each incident lasted on private and public views.
- Creating or editing a monitor uses a short multi-step form with an unsaved-change guard.
- On Wayland Linux, Movitera Link full control works through the desktop remote-desktop portal; the console shows when control cannot reach the device.
- Closure categories can require approval before completion: technicians open an approval hold, and approvers decide on a dedicated page.