TLDRocket
Sign in

Atlassian upgrades AI coding agents for always-on software development

SiliconANGLE Kyt Dotson

Atlassian is adding new Jira tools for always-on AI coding agents. They’re built to let teams run agents longer, with more control and audit trails.

Based on reporting by SiliconANGLE, Kyt Dotson — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Atlassian is pushing Jira toward a more ambitious kind of automation: AI coding agents that can keep working in the background instead of waiting for each prompt. The company says the next phase of software development is “always-on” agentic AI, and its new features are meant to let engineering teams run those agents at scale without losing control over what they do.

The problem Atlassian is trying to solve is pretty familiar. More teams are using agents, but they’re also asking them to work longer, across more parts of the development cycle, and with less hand-holding. That creates obvious trust issues. Agents need context, shared memory, validation and a way to understand project standards if they’re going to do useful work instead of producing confident nonsense.

At the center of the update is Code Context, which uses Atlassian’s Teamwork Graph to give coding agents secure intelligence across complex, multi-repository codebases. The company is pairing that with Agent Space Settings and Agent Context Controls, so teams can decide where agents operate, what they can see and what they can do. In plain terms: management gets to treat them a bit more like employees with permissions than like loose chat windows.

There’s also AutoDev, which scans backlogs and turns work into code merge requests inside Jira. A standards system then checks the code, and a separate agent reviews merge requests against those standards to flag problems. On the documentation side, DevDocs can automatically create or update technical docs in Confluence straight from code repositories, so the docs don’t lag behind the code.

But Atlassian is not pretending this is magic. Every agent run generates an audit log with diagnostics, and the system can measure impact across throughput, quality, adoption and cost. There’s also an AI agent usage dashboard that shows who is using the tools, how they’re being used and what the outcomes look like at a team level. The pitch is simple: move from foreground coding tools to background agents that quietly chew through engineering tedium, while still leaving a trail you can inspect.

My take — AI-written commentary, not fact-checked reporting

This is the part of AI that actually matters: permissioning, logs and boring control panels, not another shiny chatbot demo. Atlassian is basically admitting agents are useful only when they stop freelancing like interns on espresso. That’s the right instinct, and it’s a reminder that enterprise AI wins by being governed, not by being clever for five minutes.

Read more about this at: SiliconANGLE

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.