Why Cuelight

Several apps can already start an AI coding agent from a Jira ticket, and most teams can start a GitHub Actions workflow from Jira somehow. What usually goes missing is everything after: how the run went, what should happen next, and who is allowed to do it.

Cuelight closes that loop on the ticket:

  1. Run. Someone presses a button, like Send to agent or Deploy to staging. Cuelight checks their Jira groups and starts the workflow. They don't need GitHub access.
  2. Report. The run posts its result to the same ticket, with a link to the pull request or the logs.
  3. Next step. The run hands over the next buttons, like Deploy preview, Promote to production, Roll back or Run agent again, and only the people allowed to press them see them enabled.

Cuelight isn't an AI agent and uses no AI itself. If you use one, it runs in your own GitHub Actions with your own API key.

Compared with AI agent apps

AppStarts the agentThe agentAfter the pull request
GitHub Copilot for JiraAssign the work item to Copilot, or @mention itGitHub's Copilot coding agentA draft pull request. Review and approval follow your rules in GitHub
Claude Agent for JiraAssign the work item to the agent, or @mention itClaude, in Anthropic's infrastructure with your Claude API keyA draft pull request for your team to review
Rovo Dev in JiraGenerate code from the work item, or assign it to the agentRovo Dev, in Atlassian's cloud sandbox, using Rovo creditsA pull request for your team to review and merge
Agent Dispatch for JiraA Send to agent buttonClaude Code or Codex, in your own GitHub Actions or GitLab CIThe run's status and the pull request link on the ticket
CuelightA Send to agent button you define, for the Jira groups you pickAny agent that runs in your own GitHub Actions, with your API keyDeploy preview, Promote to production, Roll back and Run agent again, each for the Jira groups you pick

From each app's own documentation, checked in October 2026. None of the four describes a preview, approval or deploy step on the ticket after the pull request. See Run Claude Code or Codex from Jira for the whole loop. If another agent already opens your pull requests, Approve after an agent's pull request offers Deploy preview for any pull request whose branch name has the work item key.

Compared with what teams use today

What you use todayWhat's missingWhat Cuelight adds
A label like ready-to-deploy and an Automation ruleAnyone who can edit the ticket can add the label. Nothing comes back to the ticketA button only the right Jira groups can press, a comment for every press, and the result. Keep the rule and put a button in front of it
Jira Automation manual trigger with Send web request to GitHubJira Automation has no built-in action that starts a workflow, so you call the GitHub API yourself. The result stays in GitHub unless the workflow writes back, and nothing offers the next step. Each run counts toward your Automation usage. How to set it upA workflow action with a form, a report step that writes back, and next steps the run chooses
GitHub for JiraIt shows branches, pull requests, builds and deployments. It doesn't start anythingThe buttons that start the workflow, next to the information you already see
The Run workflow button in GitHubIt needs write access to the repository, and the ticket never hears about the runJira groups decide who can run it. The run and its result are recorded on the ticket
"Can someone deploy SHOP-142?" in chatA developer has to see it, do it and reply. The ticket has no recordThe person who needs the deploy presses the button and sees the result

Works with what you have

  • Jira Automation keeps doing what it's good at. A Cuelight button can add a label or set a field, and the rules that listen for it still fire.
  • GitHub environments still apply. If a job needs a required reviewer, it waits for one in GitHub as usual.
  • Any tool that can make an HTTPS request, like n8n, a script or an agent, can offer a next step on a ticket.

When you don't need Cuelight

  • You only want an agent to open pull requests, and review and deploy already happen in GitHub. An agent app on its own may be enough.
  • Only developers run the workflows, and they're happy doing it in GitHub.
  • You only change Jira fields and never start a workflow. Jira Automation already does that well.
  • Your pipelines run somewhere other than GitHub Actions. Cuelight starts GitHub Actions workflows only, though Jira updates and offers from other tools still work.

Try it

Build an action and try its button in the action builder, send a ticket to an agent and promote the result in the demo, or install it. It's free for up to 10 users and free for 30 days for larger teams.