Skip to content
leera
Get started

Changelog

Always movingforward.

The latest from Leera. Follow product improvements, new capabilities, and changes for self-hosted deployments.

Latest releasev1.10.0Explore what’s new ↓
Release notesBuilt, shipped, improved.
v1.10.0Latest release
AIIntegrationsSelf-hosted

Ping retired and simpler Slack account linking

Ping and personal connected accounts are retired, and Slack accounts link with a single-use code from /leera link.

  • Ping, the AI teammate, is no longer part of Leera: its page, Slack direct messages and channel mentions, check-ins, questions to teammates, goals, memories, briefs, meetings and analytics are gone. When your deployment updates, Ping’s stored data is deleted, including Ping conversations. Comments Ping posted on issues stay as ordinary AI comments, and messages it already delivered by Slack or email stay where they were delivered.
  • Personal connections to Gmail, Google Calendar, a Microsoft 365 calendar or another product’s MCP server are retired. Their stored sign-in tokens are deleted on update but not withdrawn at the provider; remove the app in your Google or Microsoft account’s security settings if you want that access gone.
  • The read-only Ping tools for MCP clients and the Ping: read permission are removed. Existing tokens keep their other permissions; a client that asks for ping:read by name is refused and must stop asking for it.
  • Existing Slack account links stay. To link one now, type /leera link in Slack and paste the single-use code it sends you, valid for 10 minutes, under Settings → Slack → Your Slack account. Accounts are no longer linked automatically by matching email, and unfinished link requests are canceled.
  • Leera AI chat, AI agents, Leera’s MCP server for AI clients, the Slack integration (channel rules, issues from Slack, personal notifications, QA report sharing) and the GitHub, GitLab and Figma integrations keep working. Plan details no longer list a Ping allowance; existing licenses stay valid.
  • Self-hosted: take a database backup before updating, because deleted Ping and connected-account data can only be recovered from it. To withdraw Google access at Google itself, run ./install.sh --revoke-connected-accounts on your current version before updating; the command is removed in this release. Connected-account app credentials are deleted, and the LEERA_TYPESAFE_*, CONNECTORS_GOOGLE_* and CONNECTORS_MICROSOFT_* settings are obsolete. Leera Cloud was updated on October 24, 2026.
v1.9.0
AIPlannerAuthenticationSelf-hosted

Scoped Ping goals and clearer planning

Give Ping scoped work to follow up, plan across accessible projects, and navigate boards, email codes and workspace reminders more easily.

  • Ping brings private chat, goals and checkpoints, explicitly authorized work on selected issues, and optional watches for overdue, blocked or waiting work. Review progress, pause work and control what the separate work brief may share.
  • Review, correct or forget Ping’s saved work facts and conversation context. Work tools use your existing access; shared tool changes require an exact preview and approval. Teammate contact still requires participation and current permissions.
  • Use configured Slack, email and calendar connections with their individual permissions. Where Gmail is enabled, new users’ first Allow discloses automatic five-minute Inbox checks and suggested replies; existing users’ choices are preserved and sending still needs approval of the exact email. Gmail is not generally available on Leera Cloud, and integration-specific previews and setup limits remain.
  • Figma and FigJam web Preview adds document links, cards and click-to-load embeds. Connect your own account for private previews of files you can access. Operators must configure their own app and complete live acceptance before rollout; source permissions remain in force.
  • Plan standalone issues and parent-child work on a project roadmap, or choose All projects to compare the projects you can access. Open an issue in its own project and keep saved dates consistent between views.
  • See project tags and active linked-test-case counts on board cards and list rows. Navigate wide boards with Board overview and long lists with Jump to group. Backlog search, inline issue creation and keyboard focus are clearer.
  • Enter or paste email verification codes into six slots with autofill support, clearer resend feedback and recovery guidance. Completing a sign-in code submits it once.
  • Use compact trial and payment-grace notices with appropriate next steps for your role. Cloud low-token notices distinguish a low balance from a suspended workspace. Resize navigation with the mouse, touch or keyboard while keeping saved widths.
  • Open What’s new for release history. Only Got it acknowledges a release; closing the dialog leaves its prompt available. Acknowledgment stays separate for each release, server, workspace and user; vendor prompts remain hidden on white-labeled instances.
  • Ping starts automatically with nonarchived projects initially in workspace scope; people still consent before participating. Administrators can use Pause Ping in Workspace Settings → Ping. AI chat needs a configured provider plus AI and Planner access; templated check-ins work without a model.
  • Before upgrading, retain a backup of any generic AI Reports and Coordination records you need: those features, report-only chat cards, and Coordination tasks, schedules and responses are removed. QA test reports and ordinary chat history remain.
  • Managed Slack connections are deactivated, with pending deliveries and channel approvals canceled. Reconnect using the instance’s own Slack app. Self-hosted installations must upgrade API, web and database together; desktop apps retain their separate release cycle.
v1.8.0
AIIntegrationsQASelf-hosted

Reviewed follow-ups and clearer QA evidence

Ping (introduced as Organization Agent) and expanded Slack workflows arrive as opt-in previews, alongside integration APIs, clearer QA evidence review and analytics consent controls.

Illustrated feature preview · Ping Preview: review project scope, owner and manager routing, and the fixed question template before enabling monitoring.
  • Ping (introduced as Organization Agent) Preview monitors recorded overdue and blocked issues in explicitly selected projects, with reviewed owner and reporting-manager follow-ups, business-hour response windows and retained case evidence. It is off by default.
  • Expanded Slack Preview supports explicit account linking even when email addresses differ, issue intake and optional AI assistance.
  • The REST API and signed outbound webhooks are in Preview, with scoped Planner and QA access, signature verification and delivery recovery.
  • Sentry Cloud alert intake and GitLab.com merge request linking are in Preview. Customer credentials, matching deployment and representative live verification remain required.
  • QA run recordings play continuously through available clips in case order. Create a linked defect from an existing failed result while preserving its verdict, evidence and issued report snapshots.
  • Configured website and Leera Cloud analytics require explicit consent with decline and withdrawal controls. Self-hosted application activity is excluded; consented website license checkout is separate. Live provider ingestion remains a rollout check.
  • Preview features retain their setup, access and delivery limits. A release does not establish live provider verification or Slack Marketplace approval.
v0.2.5
MCPSelf-hosted

MCP permissions grow up

Connected AI clients can now be granted access beyond read-only Planner, and the OAuth consent flow got friendlier.

Illustrated feature preview · Choose read or write access for connected AI clients across modules.
  • MCP connections can be granted read/write access across modules — not just read-only Planner.
  • The OAuth consent page scrolls properly, so "Allow access" is always reachable.
  • Self-hosted updater: bundle refresh works mid-update and reports clearly when it cannot.
v0.2.2
MCPAI

Claude.ai can now connect to your workspace

The MCP endpoint speaks OAuth, so claude.ai (and any OAuth-capable MCP client) connects with a consent screen instead of pasted tokens.

Illustrated feature preview · Review requested workspace access before connecting an OAuth-capable MCP client.
  • OAuth 2.0 served on the MCP endpoint with standards-based discovery — claude.ai connects directly.
  • Projects and the entire QA module (cases, plans, runs) exposed through MCP tools.
  • MCP coverage extended to project settings, team, and roles.
  • Initialize-based MCP protocol support, so current-generation clients connect cleanly (0.2.1).
v0.2.0
MCPBillingSelf-hosted

The MCP server arrives

Every workspace now ships a Model Context Protocol server with access tokens and a growing tool catalog. Billing moved to Polar.sh.

Illustrated feature preview · Manage scoped access tokens for the built-in ticket and project tools.
  • Built-in MCP server with scoped access tokens — connect external AI clients to your workspace.
  • First tool wave: ticket and project operations, read through delete.
  • MCP connections manageable from workspace settings, self-hosted included.
  • Polar.sh replaces Razorpay for self-hosted licenses and SaaS billing.
  • Branded MCP auth challenge for white-labeled instances.
v0.1.15
EmailSelf-hosted

Project email management, polished

Inbound project email addresses are easier to see, manage, and remove.

Illustrated feature preview · Review inbound project addresses, remove an address, and check email activity.
  • Project email settings list existing addresses and support deletion.
  • Working email activity log on project settings.
  • Self-hosted operators can run upgrades from their own install directory.
v0.1.11
Self-hostedLicensing

Self-hosted edition, production-grade

One backend image now serves both cloud and self-hosted editions, with real license lifecycle management built in.

Illustrated feature preview · Review the installed license and its status from Instance Settings.
  • Single backend image for both editions — same product everywhere.
  • Licenses bind to an install, expire, refresh in the background, and can be revoked.
  • Operators can purchase upgrades directly from Instance Settings.
  • License states surfaced on the license page.
  • Setup wizard writes operator-readable configuration files.
v0.1.6
Platform

Cloud deployment foundations

Release infrastructure hardened: signed releases, cloud deploy pipeline, and unified frontend configuration.

  • Signed release keys introduced for the update pipeline (0.1.9).
  • Streamlined cloud deployment for the web app.
  • Frontend API configuration collapsed into a single server URL variable.