Ferry

Agent pipeline for Jira-driven automated development on GitHub Actions, with experimental GitLab CI support.

Jira board  ──▶  repository_dispatch  ──▶  GitHub Actions  ──▶  merged PR
   (you)              (automatic)           (autonomous)        (automatic)

Ferry connects your Jira board to a fully autonomous dev loop — Refiner, Developer, Reviewer, Iterator, and Merger agents run as GitHub Actions workflows, triggered by column transitions on your Jira tickets.

Learn more in the Ferry documentation.

Get started

Requires Node ≥ 20 and a Jira Cloud project. See the install guide for the GitHub Actions path and the experimental GitLab CI path.

npx -p @big-emotion/ferry ferry-init

Then move a Jira ticket into your Refinement column and Ferry takes over.

CLI commands

See docs/CLI.md — ferry-init, ferry-doctor, ferry-update, ferry-uninstall.

Documentation

• Install guide — GitHub Actions setup and the experimental GitLab CI setup
• How Ferry works — what it is and isn't, agent phases, auto-transitions
• Local runner — operator-local execution with per-ticket worktrees
• Configuration reference — includes the Execution paths & accepted divergences reference (script vs. claude-code-action vs. codex-cli, the prompt-enforced trade-off, the required branch-protection setting, ferry-jira-mcp, and ferry-ci-gate)
• MCP servers
• Cost governance
• Runbook

Privacy

Ferry sends Jira and repo content to your configured LLM provider. See docs/PRIVACY.md before pointing it at confidential code.

Reporting bugs

File a GitHub issue.

Contributing

See CONTRIBUTING.md.

Star History

License

MIT