StackMap
Subscribe

contrabass vs pullfrog

Terminal-first orchestrator for issue-driven AI coding-agent runs — polls Linear/GitHub, runs Codex/OpenCode in git worktrees with retries and verification. Go/Charm rebuild of OpenAI's Symphony. — versus — Open-source, model-agnostic GitHub bot: tag @pullfrog on any issue or PR and your own coding agent (BYOK) runs the task inside GitHub Actions, context via an internal MCP server.

The curated verdict

Same job — turn tracker issues into coding-agent runs. Pullfrog executes per @-mention inside GitHub Actions; Contrabass polls continuously and runs agents on your own machine in tmux panes and git worktrees.

contrabasspullfrog
Stars198822
Forks2345
LanguageGoTypeScript
LicenseApache-2.0MIT
Last activity2 months agoyesterday
Topicscoding, orchestrationcoding
Curated connections52

contrabass — the curator's take

Pick it when your work already lives in Linear or GitHub issues and you want local coding agents (Codex, OpenCode, oh-my-*) burning down the backlog unattended — worktree per issue, branch-advance verification so 'success' means commits actually landed, stall detection, deterministic retries, and a Bubble Tea TUI plus embedded web dashboard for visibility. Skip it for single interactive sessions (just run the agent CLI) or if you want cloud-hosted execution — pullfrog is the GitHub-Actions version of this job. Young Symphony reimplementation: the workflow parser accepts more fields than the runtime consumes, and the default team mode needs tmux.

pullfrog — the curator's take

The missing GitHub-native surface for coding agents: instead of copying issues into a terminal session, tag the bot and the work happens where the work lives — Actions runners, your keys, your choice of model, automated triggers for recurring flows. NOT for latency-sensitive interactive coding (Actions cold-starts apply), and 'agent with repo write access via bot' deserves the same permission audit you'd give any CI credential. Young (~800 stars) but moving fast.