Atlassian announced new Jira features intended to run AI coding agents for always-on, long-duration software development with governance and validation. The update includes a “Code Context” grounding layer built on its Teamwork Graph, letting agents operate across multi-repository projects so they can be restricted and reviewed. This shifts teams from ad hoc, chatbot-like prompting to automatically generating code merge requests and keeping documentation in sync over hours or days.
Cognition launched Devin Voice, letting users talk to Devin, its AI software engineer, to plan, code, and deliver work. It uses Cognition’s SWE-2 coding model and is powered by GPT-Live for real-time conversation. This adds a voice interface to Devin’s coding workflow so tasks can be requested by speaking instead of typing.
The article argues that AI code generators can create architecturally wrong but functionally correct code, causing a growing gap between what gets written and what humans understand about the system. It highlights a concrete example where a Python AI agent could exceed boundaries like billing importing from shipping, which is blocked by running pytest-archon in CI with rules such as “billing*” should_not_import “shipping*” after installing it via pip. It recommends shifting from documentation to “executable architecture” by adding automated boundary tests (and complexity/interface checks) so CI fails and feeds results back to the AI for fixes without relying on human reviewers.
AI coding agents at frontier labs are producing about three full workdays of research output per workday from human researchers. Token usage per researcher is up 124-fold since December and typical costs now exceed $600 per day to run agents. The shift increases reliance on automated research and heightens safeguards around unreleased models while also fueling broader impacts in medicine, public opinion, and safety incidents involving AI tools.
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.
Reading TLDRocket needs no cookies, and the readership counts we rely on come from
our own cookieless analytics. Google Analytics is the exception: it sets cookies and
reports to Google, so it stays switched off until you allow it. You can change your
mind any time from “Cookie settings” in the footer.
Strictly necessary
Session security and form protection (tldrocket-session,
XSRF-TOKEN, 2 hours). The site cannot work without them,
so they need no consent.
Always on
Google Analytics 4 (_ga,
_ga_<id>, up to 2 years). Measures which
stories and sections readers use. Google acts as a third-party processor and may
store the data outside the EU. No advertising, no profiling, no data sold.
