sortie-ai/sortie: Turn tracker tickets into autonomous agent sessions

The Problem

Coding agents can fix bugs, update dependencies, add tests, and build features. But running agents you trust across a backlog takes more than launching sessions: isolated workspaces, retries, tracker integration, and cost tracking all need to work together.

Building and maintaining that infrastructure becomes another engineering project.

Sortie is that infrastructure.

Works With

Issue trackers: GitHub Issues, GitLab Issues, Gitea Issues, Linear and Jira.

Coding agents: Claude Code, Copilot, OpenCode, Codex, Kiro and Gemini.

Install

curl -sSL https://get.sortie-ai.com/install.sh | sh

Or via Homebrew: brew install --cask sortie-ai/tap/sortie

Try the local demo with a simulated agent and no external services, or connect your tracker and coding agent.

How It Works

1. Choose which issues to work on, which agent to run, and what instructions to give it in one WORKFLOW.md file.
2. Sortie picks up matching issues and runs agents in parallel, each in its own workspace.
3. Failed runs are retried automatically. Enable CI and review feedback to send failures and comments back to the agent.

Sortie is a single binary, with no separate database or job queue to deploy. Sortie itself sends no telemetry.

Documentation

Full configuration reference, CLI usage, and getting started guide: docs.sortie-ai.com

• Guides
• Architecture
• Roadmap

Prior Art

Sortie's architecture is informed by OpenAI Symphony, a spec-first orchestration framework with an Elixir reference implementation. Sortie diverges in language (Go for deployment simplicity), persistence (SQLite instead of in-memory state), extensibility (pluggable adapters for any tracker or agent, not hardcoded to Linear and Codex), and completion signaling (orchestrator-managed handoff transitions instead of relying solely on agent-initiated tracker writes).

License

Apache License 2.0