This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
See what's next for Forge on our platform roadmap.
We're excited to share that Forge, our app development platform for Atlassian cloud apps, is now generally available. You can rely on Forge's hosted infrastructure, storage, and FaaS functions to support apps in production; all of which are backed by Atlassian's operational readiness. Learn more about building the next Marketplace hit with Forge.
Note that some functionality in Forge remains in beta while we're still making changes that may break your apps. Learn more about the current functionality in beta.
You can now build Forge apps that connect to and extend multiple Atlassian apps with a single installation. At launch, you can build apps that connect to Jira, Jira Service Management, Confluence, and Compass. We are looking to add support for other apps and platform surfaces in the future.
This new architecture enables apps to access data from and extend the UI of multiple Atlassian apps, unlocking new use cases and simplifying app management for admins. These apps are available on the Atlassian Marketplace and support unified installation and management.
To learn more and start building, see:
App Installation
App Management
Multiple-app compatibility makes Forge apps a core part of how customers orchestrate work across Atlassian apps.
Partner benefits:
New revenue opportunities: Multiple-app compatibility becomes a new Marketplace value driver.
Broader reach with less overhead: Build and operate one Forge app that connects to multiple Atlassian apps at once.
Extend existing offerings across multiple apps and surfaces without building and maintaining separate apps.
Customer benefits:
Richer, more interconnected experiences: Apps can show up wherever work happens, instead of being tied to a single host Atlassian app.
Less fragmentation: One app can span Jira, Jira Service Management, Confluence, and Compass, reducing duplicate configuration and vendor sprawl.
Better governance: Admins can view and manage these apps centrally (from Connected apps in Atlassian Administration) with clearer install and management flows.
The following models have been removed and are no longer supported by Forge LLMs:
claude-3-5-haiku-20241022
claude-3-7-sonnet-20250219
claude-opus-4-20250514
To check which models are currently supported, use the list function in the @forge/llm SDK. This function lets you filter models by their status.
Forge LLMs remain in Early Access (EAP). Due to high demand, participation is limited. To request access, join the waitlist here.
Support for Node.js 24 is now available in @forge/cli from version 12.14.0.
To upgrade, run: npm install -g @forge/cli@latest
See the Forge documentation for setup instructions.
We've increased the individual resource bundle size limit for Custom UI and UI Kit apps from 50 MB to 100 MB, allowing you to include larger assets and dependencies in each resource bundle.
Additionally, we've introduced cumulative limits that apply across all resources in your app to ensure optimal performance and resource management:
Total files: Maximum of 25,000 files across all resources in your app
Total bundle size: Maximum of 1 GB across all resources in your app
These cumulative limits apply regardless of how many individual resource bundles (up to 50) you use in your app.
For complete details on resource limits, see Resource limits.
We've introduced the useTheme hook for Forge UI Kit apps. This hook retrieves the current theme from the Atlassian app (Jira, Confluence, etc.) and reactively updates your Forge app when the theme changes.
The useTheme hook is now the preferred method for accessing theme information in UI Kit apps, replacing the previous approach of accessing theme.colorMode via useProductContext. Unlike useProductContext, the useTheme hook is reactive and automatically updates when the theme changes in the Atlassian app.
To use this hook, import useTheme from @forge/react and call it in your component. The hook returns a theme object containing the current theme configuration.
For implementation details and examples, see the `useTheme` hook documentation.
The view.onClose bridge method is now available in Confluence and Jira through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
view.onClose allows you to register a callback that runs when the extension point modal closes, such as the macro custom config modal. Upgrade to the latest version of @forge/cli to start building with the view.onClose() method.
For more information, see the updated documentation for the view bridge methods.
The fullscreen viewport size for macro custom config modal, UI Kit Modal and bridge modal is now available in Confluence and Jira, through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
Upgrade to the latest version of @forge/cli to start building with the fullscreen viewport.
For more information, see the updated documentation for the UI Kit Modal, bridge modal and macro.
You can now set custom colors for UI Kit Visualisation charts. You can either set a color theme or assign colors to attributes. This can be done by passing the prop colorPalette into your chart.
For an example of how to implement this, please see the Forge UI Kit example app at https://bitbucket.org/atlassian/ui-kit-charts-example/src/master/.
For more information, see documentation.
Forge customer-managed egress and remotes are now available through Forge’s Early Access Program (EAP). This capability lets admins control which external domains and remotes a Forge app can connect to, and configure those connections per installation. This approach is useful for apps that need to load data from customer-defined URLs, without declaring every possible destination up front in the manifest.
To join the EAP, complete this sign-up form.
We've added new methods to the webTrigger API from @forge/api that allow you to query and delete previously created web trigger URLs.
webTrigger.queryUrls() — Retrieve all web trigger URLs for your app, optionally filtered by module key
webTrigger.deleteUrl() — Delete a specific web trigger URL
For implementation details and examples, see the Web trigger runtime API documentation.
Support for dynamically retrieving the list of supported models is now available in Forge LLMs. The new list function in the @forge/llm SDK lets apps fetch the latest list of models, returning a response like:
1
2
3
4
5
6
7
8
9
10
11
12
{
"models": [
{
"model": "claude-sonnet-4-20250514",
"status": "active"
},
{
"model": "claude-opus-4-20250514",
"status": "deprecated"
}
]
}You can filter on the status field to ensure your app always uses an active model and avoid breaking changes when a model is removed.
Forge LLMs remain in Early Access (EAP). Due to high demand, participation is limited. To request access, join the waitlist here.
For implementation details, refer to the documentation here.
You can now migrate a Connect Jira Issue Field module to Forge's custom field module. The functionality is now available for String, Number and Read-only fields.
See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/ for more details.
Forge app REST APIs let your app expose its own HTTP endpoints so that external systems can call your app code running on Forge.
These Forge app REST APIs are secured with developer-defined scopes and use 3LO (OAuth 2.0) for authentication and authorization. You define the endpoints in your app manifest using the apiRoute module.
This capability is currently in Preview and is available for Jira and Confluence Forge apps. This is currently not available in Isolated Cloud.
To learn how to expose REST APIs in your Forge app, see Expose Forge app REST APIs. For a step-by-step tutorial on configuring a 3LO integration to access exposed REST APIs, see Access REST APIs exposed by a Forge app.
Forge embedded macros are now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
Forge bodied macro apps can now render embedded Forge macro apps through the AdfRenderer component (UI Kit) and the view.createAdfRendererIframeProps method from @forge/bridge (Custom UI).
For more information, see the updated documentation for Forge rich-text bodied macros.
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-125-ui-modification-for-forge-custom-fields/98439
Rate this page: