Changelog

Forge LLM is now available through Forge’s Early Access Program. This feature allows Forge apps to integrate with an Atlassian-hosted large language model (LLM) capability, meaning that apps that use the feature will still be eligible for the Runs on Atlassian program.

At launch, only the Claude model family is supported. Support for additional model families will be added soon.

Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

We’re updating Forge’s invocation rate limits to improve our long-term scalability and flexibility. This change will help ensure our platform can adapt and respond to unpredictable high bursts of traffic.

Currently, we limit the number of invocations to 1,200 per one-minute fixed window.

We are changing this limit to a per one-second sliding window instead, scaling the limit appropriately. In addition, invocations from Forge events and user-triggered interactions will have different limits.

The sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.

Along with this, we’re introducing a few improvements to sidebar interactions:

• Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.

• Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.

• Helpful tooltips: Tooltips will appear to guide you through the interaction.

For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:

• Custom logos and titles

• Favicons

• Navigation colors

• Dark and light mode settings

Because of this, the sites with customized look and feel won’t receive the update just yet.

For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.

As announced previously, the ability to use triggers as a dynamic module is now available under Forge’s Early Access Program (EAP).

To start testing, sign up for the EAP here.

As part of our new design language, the refreshed colors and components in the Atlassian Design System (that first launched in products at Team '25) are now officially in GA. Also included is a further tweak to accent token colors in hover/pressed states to improve accessibility.

What you need to do if you are using Forge Custom UI or Atlassian Connect:
Bump @atlaskit/tokens + relevant component packages to the latest version to align your app's look and feel with Atlassian apps.
What you need to do if you are using Forge UI Kit or Forge UI Kit 2:
Nothing! You should have the newest components by default.

The GET methods of the Key-Value Store and Custom Entity Store SDKs can now return optional metadata fields, namely:

• createdAt

• updatedAt

In the previous pricing announcement, the SQL Data stored metric used an average model with billing unit in GB. We are shifting to a sum/counter model. To prevent financial implications from this change, we are adjusting the billing unit, monthly quota, and pricing.

Starting today, the developer console and cost estimator will reflect this change. SQL data stored usage in the developer console will now be displayed in GB-hours.

With immediate effect, the Developer Console will display near real-time usage data for all chargeable capabilities. In rare cases, a delay of a few hours may occur before the latest usage appears.

The following Object Store UI components are now available for through Forge’s Early Access Program (EAP):

• UI Kit components:

  • File picker: allows the user to select files stored locally.

  • File card: displays information about a file (including name, type, and size); this can be used to managed selected files and displaying upload progress.

• Frontend components for integrating with the Forge Object Store via backend resolver:

  • useObjectStore hook method (for apps that use UI Kit)

  • objectStore bridge API (for apps that use Custom UI)

To start testing these capabilities, please go here.

The Batch operations capability is now generally available, allowing you to execute multiple KVS and Custom Entities requests simultaneously. These batched requests are executed in parallel, and each requests will be completed on a “best effort” basis (unlike Transactions, where all requests are completed in an “all or nothing” basis).

This capability was originally launched in EAP as Bulk Set; on Sep 3, 2025 we closed this EAP in preparation for general availability.

Batch operations is included in version 1.2.0 of the @forge/kvs package.

Following its EAP release, Forge Realtime is now available in preview for Jira and Confluence.

Realtime allows Forge apps to subscribe and publish events to users in different browsing contexts, including the ability to publish events from Forge resolvers to the client. During Preview, Realtime can be used in production environments for your app.

Since the EAP release, we’ve implemented the following changes:

• To use global channels, you must now include the Realtime read:app-global-channel:realtime scope in your manifest. Users will then need to upgrade their installation of your app.

• The contextOverrides option now accepts Confluence context properties.

• Event payloads can now be JSON-serializable objects without needing to be stringified first. String payloads are still supported.

Run the following commands on the command line in your app directory to install the latest version of these packages and receive these changes:

• npm install @forge/bridge@latest

• npm install @forge/realtime@latest

For more information, see the Realtime documentation.

The Confluence full page module is now available in Preview. After a successful Early Access Program (EAP), we’re making the module more broadly available for developers to build fully customised app experiences within Confluence.

The EAP URL is now deprecated and will no longer work. Please update your bookmarks and use the new Preview URL format.

More details:

• Old EAP URL (deprecated):
  <https://<tenant-name>/wiki/full-page/<app-id>/<environment-id>>

• New Preview URL (Forge Apps UI Service):
  <https://<tenant-name>/forge-apps/a/<app-id>/e/<environment-id>/r/<route-prefix>/<app-route>>

For more information, see the Confluence full page (Preview)

The ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.

For more information, see App compatibility.

We’ve added new Confluence Forge events for relations:

• avi:confluence:created:relation

• avi:confluence:deleted:relation

You can use these events to invoke your Forge app function when a relationship is created or deleted in Confluence. For more details, see the Confluence events reference documentation.

You can now call Web trigger URLs with additional path suffixes. Previously, requests to a WebTrigger URL with a path suffix (for example, /hello/world) returned a HTTP 404 error. With this update, such requests are now routed to your associatedhttps://developer.atlassian.com/platform/forge/manifest-reference/modules/function/, and the suffix is available in the new userPath property of the request.

This enhancement lets you handle dynamic routes and build more flexible integrations with your Forge app.