Atlassian introduces Jira as the system of record for OpenAI Symphony, an agent orchestration layer for Codex. The integration anchors AI coding agent work to Jira work items, keeping intent, status, progress, code reviews, and follow-up tasks connected in existing team workflows. Symphony watches Jira projects, routes eligible work items to isolated agent sandboxes, and posts updates back to Jira comments. Teams can queue agent tasks, run them in parallel, and maintain human review accountability without monitoring live sessions. Setup involves pulling the public Symphony repo and using Codex to generate a Workflow.md configuration for a Jira space.
Table of contents
Start with the work item, not the sessionHow it worksWhat teams can do with itGet startedQuestions this post answers
How does OpenAI Symphony use Jira to manage AI coding agent work?
Symphony watches a Jira project for eligible work items, routes them to isolated Codex agent sessions, and posts plans, progress updates, and blockers back as Jira comments. Follow-up tasks discovered by agents are created as new Jira work items. Jira workflow statuses control which items are active, blocked, ready for review, or complete, so engineers review the work item rather than monitoring live agent sessions. Teams scaling AI coding agents track orchestration patterns like this on daily.dev.
How do I get started with OpenAI Symphony and Jira integration?
Pull the public Symphony repo from github.com/openai/symphony, then prompt Codex to generate a Workflow.md file for your Jira space. The setup process asks for credentials and pulls your Jira space configuration. Once configured, follow the README in the elixir sub-folder to start Symphony. Start with work items that have clear acceptance criteria and low dependency risk before expanding to larger queues. Developers wiring up AI agent workflows find setup walkthroughs and ecosystem updates on daily.dev.