Changelog

October 2026September 2026August 2026July 2026June 2026May 2026
UPDATESOverview

July 2026 release notes

July opened support to new channels — tickets arriving over WhatsApp and phone, with numbers provisioned right in the app — and turned the Wiki into a documentation platform with revisions, comments, public links, and exports. Forge gained a pull-request workspace with AI reviews you can publish to GitHub, Muse gained supervised plans and a morning brief, teams took control of AI models with their own provider keys, and remote desktop added multi-monitor support.

July highlights

  • Closure now supports WhatsApp: requesters open and follow tickets by message, with photos and files, and technicians' public replies are delivered back over WhatsApp. Teams connect their own number self-service, with message templates, automatic acknowledgment, a business profile, and transparent pricing.
  • Closure also answers the phone: teams provision a number right in the app, and incoming calls are recorded, transcribed, and summarized into tickets automatically; unknown contacts land in an identification queue.
  • The Wiki became a documentation platform: revision-based publishing with history and visual comparison, comments anchored to the text, public links with optional email verification, Markdown and PDF export, and AI-assisted writing improvement.
  • Every pull request now has its own page in Forge — diff, commits, checks, and conversation — with AI review available on any pull request and one-click publication of the review to GitHub.
  • Muse gained multi-step plans you can edit, schedule, supervise, and undo, plus an optional morning email brief with what needs your attention today.
  • Teams now control their AI models: bring your own provider keys, build a per-team model pool with benchmarks and real prices, and use the newest models, including Claude Opus 5.
  • Support gained smart delegation by category, an active-ticket cap per technician, AI-generated ticket titles, and separate incident vs. request analytics — and MSP teams gained a Customers module with 360° views, SLAs, and per-customer attribution, in early access.
  • Remote desktop added multi-monitor support with live switching, and a Forge issue can be handed to your local coding tool, like Claude Code or Cursor, with full context.
Availability

Availability depends on your plan, your role and permissions, and enabled modules. WhatsApp and phone channels are provisioned per team and carry their own usage costs, shown before activation; the Customers (MSP) module is in early access and enabled per workspace; some AI features depend on plan, usage limits, and — when configured — your team's own provider keys.

July 28-31, 2026

  • WhatsApp setup became fully self-service: teams connect their own number, follow the channel status in real time, enable automatic acknowledgment when tickets open, and manage the business profile shown on WhatsApp — with channel pricing disclosed before signup.
  • The unified inbox arrived: everything that needs your attention in one place, with work separated by stage — like what is in testing and what is ready to deploy.
  • A Forge issue can be handed to your local coding tool, like Claude Code or Cursor, with full context to pick up the work where it left off.

July 20-27, 2026

  • Claude Opus 5 joined the model catalog, and administrators set the team's default models for coding sessions and Muse.
  • AI reviews can be published to GitHub as comments on the exact line of code.
  • External AI assistants connected to Movitera can receive a write authorization granted in the browser — approved once, revocable anytime.

July 14-19, 2026

  • The Forge pull-request workspace arrived: a list, preview, and full page for every pull request, with diff, commits, checks, and viewed-file tracking.
  • Company AI settings: connect your own provider keys, build the team's model pool in a picker with benchmarks and price per million tokens, and configure AI review.
  • Coding sessions and AI reviews gained previews and their own pages, plus a team dashboard to follow every session in one place.
  • Promise Review: a second, independent AI review from a different provider evaluates the change before approval — including externally authored pull requests linked to issues.
  • Forge cycles gained verifiable delivery readiness and delivery briefs.
  • Ticket categories gained assignment policies: a default technician or smart delegation that weighs the team's load and availability.
  • The WhatsApp channel gained message template management, and tickets now show their channel of origin.

July 7-13, 2026

  • The Closure phone channel arrived: teams provision a Brazilian number right in the app, and incoming calls are recorded, transcribed, and summarized into tickets automatically.
  • Unknown contacts — by phone or WhatsApp — land in an identification queue so the team links them to the right person before a ticket is created.
  • Remote desktop added multi-monitor support: view, control, and switch between a device's screens live.
  • Tickets can be opened without a title: AI generates one from the description.
  • The Closure dashboard gained per-kind analytics, separating incidents from service requests.

July 1-6, 2026

  • The Wiki gained revision-based publishing: drafts separated from published content, version history with visual comparison, and restore.
  • Wiki pages accept comments anchored to a passage or block, with replies and resolution, in a side panel.
  • Published pages can be shared by external link — open, or protected by email verification.
  • Pages can be exported to Markdown or PDF, and the editor gained find-in-page and the Improve writing control, which refines text with AI.
  • Muse plans got more powerful: edit steps before approving, chain dependent steps, undo an executed batch, route sensitive plans to supervisors, and schedule recurring routines.
  • The Muse morning brief arrived: an optional daily email with your queue, decisions waiting, expiring contracts, overdue invoices, and today's activities.
  • MSP teams gained the Customers module in early access: customers with 360° views, tickets and assets attributed per customer, SLA plans, and per-customer documents and credentials.
  • Technicians gained an active-ticket cap: above the limit, assigning more tickets requires a supervisor.