Article —
Sortie turns tickets into pull requests
Sortie is an open-source orchestrator that hands issue-tracker tickets to coding agents and follows the work through CI and review. What it is, what it is not, and where it fits.
Sortie describes itself as “Tickets in. Pull requests out.” It watches your issue tracker, gives each ticket its own workspace, starts a coding agent on it and follows the result through CI, review and merge.
What it is
An open-source (Apache-2.0), self-hosted orchestrator for coding agents. It works with trackers such as Jira, GitHub, GitLab, Linear and Gitea, and with agents such as Claude Code, Codex, Copilot CLI, OpenCode, Gemini and Kiro. One WORKFLOW.md file holds both the settings and the agent prompt. Failed CI goes back to the agent, reviewer comments reach the same session, and you cap tokens, turns and concurrent agents.
What it is not
- Not a coding agent. It does not write the code; it runs the agent that does.
- Not a hosted service. You run it yourself, on a laptop, a VM, a container or Kubernetes.
- Not a substitute for review. A person still decides what gets merged.
What it is good for
Teams that already keep work in a tracker and already use a coding agent, and want the step in between automated. Well-scoped tickets, such as small features, fixes and chores, are the natural fit. Vague tickets still need a human to sharpen them first.