Atlassian Brings Visual AI Creation and Third-Party Agents Into Confluence — Targeting the Gap Between Documentation and Execution
Confluence users can now generate images, diagrams, and visual assets directly within the platform using AI, alongside new agent integrations from Lovable, Replit, and Gamma. The update is Atlassian's most direct move yet to make Confluence a live workspace rather than a documentation repository — and to embed AI execution capability where knowledge work actually happens.

D.O.T.S AI Newsroom
AI News Desk
Atlassian has added visual AI creation tools to Confluence alongside integrations for three third-party AI agents: Lovable, Replit, and Gamma. The update lets Confluence users generate images, flowcharts, and presentation-ready visual assets within the platform without leaving the documentation environment. The agent integrations go further, allowing users to trigger Lovable's UI generation, Replit's code execution, and Gamma's slide creation directly from Confluence pages — turning documentation into a coordination layer for AI-assisted work rather than a static record of completed work.
What Changed
The visual AI tools in Confluence use a combination of Atlassian's own AI infrastructure and third-party image generation to produce graphics inline with documentation. Users describe what they need — a diagram of a system architecture, a mockup of a UI flow, a visual summary of a quarterly plan — and the tool generates it within the page. This addresses a friction point that documentation teams have consistently identified: visual assets require round-trips to external tools like Figma, Lucidchart, or Canva, breaking the documentation workflow and creating version management problems when designs change.
The Agent Integration Model
The third-party agent integrations are more architecturally significant. Rather than just embedding links or previews of external content, Atlassian is allowing agents from Lovable, Replit, and Gamma to act within Confluence pages. A product manager documenting a feature spec can trigger Lovable to generate a working UI prototype from the spec. A developer writing technical documentation can run Replit to execute code examples inline. A team creating a strategy document can have Gamma build a presentation from the document's structure. The integration pattern treats Confluence as an orchestration surface rather than a destination where finished work is recorded.
Atlassian's Broader Bet
This update is part of Atlassian's ongoing effort to position its products as the connective tissue of enterprise AI work rather than as legacy productivity tools at risk of displacement. Jira has added AI issue creation and sprint planning. Confluence is becoming an execution environment as much as a documentation tool. The risk in the strategy is product coherence: Confluence's strength has been its simplicity as a wiki. Adding AI generation, agent execution, and third-party integrations significantly increases the surface area that users need to understand. The question is whether Atlassian can make these capabilities feel like natural extensions of documentation work rather than features that make the tool feel like a different product entirely.