Operations | Monitoring | ITSM | DevOps | Cloud

Bring your Codex agent into Bitbucket Pipelines. A few weeks ago, we announced support for Claude agents in Bitbucket Pipelines. Today, we’re adding OpenAI Codex as a supported agent. If your team is already using Codex on the desktop, you can now move that same workflow into your pipeline — triggered by a merge, a schedule, a failing build, or a pull request comment.

In November 2025, we introduced new triggers and workflows to Bitbucket Pipelines to help teams manage and scale complex CI/CD workflows. We later extended that foundation with additional event-based triggers for pipeline, deployment, and pull request events. We’re now extending that model with a new package-artifact-created trigger.

When we introduced native Pipelines authentication for Bitbucket Packages, we made it easier to publish artifacts from CI/CD without relying on personal credentials. Now we’re extending that integration further: package artifacts published through the Pipelines integration can display a Source Pipeline, making it easy to trace an artifact back to the pipeline run that created it.

If your team bIf your team builds with Python or.NET, your packages have likely lived separately from your code, stored in a registry with distinct login, permissions, and billing. Starting today, they don’t have to. Bitbucket Packages now supports the Python Package Index (PyPI) and NuGet, integrating Python and.NET package management into the platform where your team writes code, reviews pull requests, and runs pipelines.

You shouldn’t have to leave your PR list to know where your code is deployed. Yet, developers constantly lose time context-switching just to see if a change hit staging or production. To solve this, we are launching the Beta version of Deployment Status Tracking for your PRs. This feature surfaces live deployment statuses directly within your PR list view as code moves through your pipeline.

We’re excited to announce that immutable tags are now available for the Bitbucket Packages container registry. With immutable tags, workspace admins can set container image tags from being overwritten, moved, or modified after they’re first pushed.

In December, we shared our plans to introduce pricing for self-hosted runners. You told us loud and clear that a free option matters. Today, as Premium Runners become generally available, we are happy to share that we will continue to have a free tier, which includes the use of up to 100 self-hosted runners as part of your plan. If your team needs more scale, dedicated support, or advanced management features, you can upgrade to Premium Runners when you’re ready.

Last month, we introduced Agentic Pipelines, a new way to orchestrate AI agents to automatically, and routinely, handle the repetitive engineering chores so you can get back to solving the fun, cool problems. When we launched, Agentic Pipelines supported Atlassian’s developer AI agent, Rovo Dev. Today, we’re opening up Agentic Pipelines to even more teams: You can now run agentic steps in your pipeline with Claude as the provider.

At Atlassian, we use Merge Queues to ship frequent changes with confidence and streamline pull request merges. Across some of our busiest codebases, Merge Queues have sharply reduced incident frequency and turned merging from a stressful bottleneck into a background task. Today, most of our largest repositories rely on Merge Queues—over 70 large repos across products like Jira, Rovo, Trello, and others—having safely landed 30,000 pull requests since adopting Merge Queues Beta last quarter.

Your CI/CD pipeline doesn’t have to live in a YAML file anymore. With on-demand pipelines, you can generate pipeline definitions programmatically, from scripts, services, or automation tools – and execute them instantly via the Pipelines API. No commit. No pull request. No static configuration to modify. Just build the YAML your situation demands and run it.