ferry vs run-gemini-cli
Jira-driven agent workflows compared with Gemini CLI in Actions
ferry and run-gemini-cli both use GitHub Actions to bring AI-assisted work into repository workflows. ferry starts a multi-phase development pipeline from Jira ticket transitions, while run-gemini-cli runs Gemini CLI for event-driven or on-demand coding tasks, reviews, and triage.
ferry: Turn Jira Ticket Moves Into Draft Pull Requests
Ferry uses Jira ticket transitions to start an agent pipeline in GitHub Actions, from refinement through review and merging. It suits teams seeking an automated development workflow, but requires Jira Cloud, GitHub Actions setup, and an LLM provider.
run-gemini-cli: Run Gemini CLI in GitHub Actions
run-gemini-cli brings Gemini CLI into GitHub Actions for automated coding tasks and on-demand help in issues and pull requests. It suits teams that want AI-assisted reviews, triage, or repository changes within their existing workflows.
| ferry | run-gemini-cli | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | Apache-2.0 |
| Stars | 3 | 2.1k |
| Forks | 1 | 288 |
| Last analyzed | Oct 4, 2026 | Oct 3, 2026 |
Key differences
- ferry is organized around Jira ticket transitions and distinct refinement, development, review, iteration, and merge phases; run-gemini-cli responds to repository events, schedules, or issue and pull request comments.
- ferry requires Jira Cloud and Node.js 20 or newer for its documented setup; run-gemini-cli requires GitHub Actions workflows and credentials for Gemini services and GitHub API access.
- ferry documents a local runner with per-ticket worktrees and experimental GitLab CI support; run-gemini-cli is a GitHub Action with configurable workflow examples.
- ferry is licensed under MIT, while run-gemini-cli is licensed under Apache-2.0.
- The supplied project data lists 3 stars and 1 fork for ferry, and 2.1k stars and 288 forks for run-gemini-cli.
Choose ferry if you…
- want Jira status changes to initiate an agent workflow through review and CI.
- need distinct agent phases and options for hosted GitHub Actions or local ticket worktrees.
- are prepared to configure Jira Cloud, an LLM provider, and GitHub Actions.
Choose run-gemini-cli if you…
- want Gemini CLI available in GitHub Actions for reviews, issue triage, or coding tasks.
- need on-demand assistance from issue or pull request comments, or scheduled repository tasks.
- want to configure Gemini authentication, prompts, models, and GitHub access for your workflows.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.