foreman vs Cognition AI
Side-by-side comparison of features, pricing, and ratings
At a glance
| Dimension | foreman | Cognition AI |
|---|---|---|
| Pricing | Free (MIT), you pay Claude API/CLI usage | Contact sales; enterprise contract |
| Deployment | Local TUI, runs your installed claude CLI; macOS/Windows need WSL2 | Vendor-hosted Devin, Desktop and CLI, Slack/Teams/IDE integrations |
| Model dependency | Claude Code only | Cognition's own models: SWE-2, SWE-1.7, plus Fusion harness for Fable/Astra |
| Process model | Fixed gated pipeline: plan, ADR/PRD, issues, TDD, e2e | Ticket-to-PR autonomous loop with auto-triage and review-comment fixes |
| Cost controls | Per-run turn/cost/time budgets plus daily hard ceiling; demo mode at zero token cost | Not disclosed in provided data |
| Ecosystem hooks | Claude Code, git | GitHub, GitLab, Bitbucket, Jira, Linear, Slack, Teams, PagerDuty, Databricks, MongoDB, Windsurf |

An MIT-licensed orchestrator TUI that supervises headless Claude Code agents through a gated plan → ADR/PRD → issues → TDD → e2e delivery pipeline
Visit WebsiteCognition builds Devin, an autonomous AI software engineer that takes a ticket to a merge-ready pull request.
Visit WebsiteWhat real users say: foreman vs Cognition AI
Not marketing copy and not our opinion — a structured sweep of public discussion (reviews, forums, communities and video comments), showing what people praise and what they complain about for each tool.
foreman
63 mentions across 5 sources · 35% positive — critical (weighted across 5 sources)
Hacker News, YouTube, Product Hunt, GitHub, Lemmy
What users praise
- • Gated plan → ADR/PRD → issues → TDD → e2e pipeline enforces process rather than trusting agent behaviour
- • Hash-sealed approvals auto-revert if a design document changes underneath them — a genuinely novel safeguard
- • Per-run turn, cost, and time budgets plus a daily hard ceiling put hard stops on runaway spend
- • PreToolUse deny hook stops workers from writing their own verification — closes an obvious cheating loophole
What frustrates them
- • Essentially no independent community feedback — one HN post, no reviews, no issue tracker evidence
- • Linux/WSL2-only with Python 3.11+ and authenticated claude CLI — macOS and Windows users excluded
- • Tightly coupled to Claude Code; no support for other agent CLIs or local models
- • The fixed TDD-centric pipeline will clash with teams that don't practice TDD
Researched Oct 16, 2026
Cognition AI
50 mentions across 3 sources · 43% positive — mixed (averaged across 3 sources)
Hacker News, Bluesky, Lemmy
What users praise
- • End-to-end autonomous planning, coding, and PR creation for enterprise teams.
- • FrontierCode evaluation ensures merge-worthy code output.
- • Auto-Triage automates bug monitoring and fix PRs.
- • Native Windows VM and Android emulator support for cross-platform testing.
What frustrates them
- • Community feedback is almost nonexistent — little proof of reliability.
- • Critics question the $10B valuation given unproven adoption.
- • Political ties to Peter Thiel may deter some users.
- • Limited transparency on actual customer success stories.
Researched Jul 16, 2026
Feature-by-feature
Foreman's differentiator is enforcement. Its gates live in the orchestrator, not the model: a PreToolUse deny hook stops workers writing their own verification, a declared touches set plus worktree isolation keeps parallel workers separated, approvals are hash-sealed and auto-revert when a design doc changes, and state lives as readable files committed in the repo with no database. The demo mode replays canned stream-json at zero token cost, and an evals flywheel (retro clustering failures into gated patches, bench replaying the set with success-rate, cost and turn deltas) gives it a measurement loop. The tradeoff is rigidity: ADR/PRD/issue gates assume your team wants that ceremony, and the whole thing is welded to Claude Code, with macOS and Windows users needing WSL2.
Cognition's Devin attacks a different constraint. It ingests Linear or Jira tickets, maps files, writes code, runs tests, opens PRs, then works review comments — with auto-triage on monitored bugs and a vulnerability remediation program wrapped around it. The model line is proprietary and fast-moving: SWE-2 arrived September 10, 2026 with multiple effort levels, SWE-1.7 targets frontier intelligence at lower cost, and Fusion (shipping in Devin Desktop and CLI) carries a vendor claim of up to 39% higher benchmark efficiency. FrontierCode 1.1 scores merge-worthiness rather than test-passing, and native Windows VMs and an Android emulator sit inside the loop. Session persistence and scheduled sessions keep long jobs alive. Foreman lets you audit everything locally; Cognition asks you to trust its benchmarks and contract.
Pricing compared
Foreman is MIT-licensed and free — the real cost is your Claude usage plus the engineering hours to install it, point it at a repo, and accept the .foreman/ scaffold. Critically, it ships its own spend controls: per-run turn, cost and time budgets for every worker, a daily cost ceiling with a hard stop, and a demo mode that exercises the full pipeline on canned stream-json for zero tokens. That makes pilots cheap and predictable, and a team can trial the whole workflow before committing API budget. The hidden line item is labour: WSL2 on macOS/Windows and a team comfortable with ADRs and PRDs.
Cognition does not publish pricing in the provided data — it's a contact-sales enterprise contract, and comparisons should treat it as negotiated. What you're buying is the managed platform: Devin in Desktop and CLI, Slack/Teams/Jira/Linear/PagerDuty integrations, Windows and Android build environments, FedRAMP High In-Process positioning, and a productivity outcome backed by an up-to-$10M guarantee. The $1B annualized run-rate reported September 25, 2026 and the AWS multi-year agreement suggest pricing power and a sales-led motion rather than self-serve checkout. Budget for procurement and review capacity; the product's value scales with backlog volume, so small teams will struggle to justify the spend against Copilot or Cursor.
Who should pick which
- Open-source maintainer running Claude Code dailyPick: foreman
Free MIT orchestrator adds gated plan-to-e2e workflow and an in-repo audit trail without a vendor contract.
- Eng org piloting agentic delivery on a tight budgetPick: foreman
Per-run budgets, a daily hard cost ceiling, and zero-token demo mode let you measure before you spend.
- Enterprise platform team with a multi-thousand-ticket backlogPick: Cognition AI
Devin's ticket-to-PR loop plus auto-triage and vulnerability remediation is built for volume, not single tasks.
- Team needing Windows and Android builds inside the agent loopPick: Cognition AI
Native Windows VMs and an Android emulator are part of Devin's environment; Foreman is repository-and-git only.
- Regulated or government agencyPick: Cognition AI
FedRAMP High In-Process positioning and an outcomes guarantee match procurement requirements a local TUI can't meet.
Frequently Asked Questions
Can I run Foreman without spending anything on tokens?
Yes for evaluation — demo mode replays the full pipeline on canned stream-json at zero token cost. Real runs are billed by your own Claude usage, but the daily ceiling caps the damage.
What happens if someone edits an approved design doc mid-run?
Foreman's approvals are hash-sealed; changing the doc auto-reverts the approval, forcing re-review before build continues.
Does Devin need me to specify which model to use?
The provided data doesn't describe model selection controls. What's documented is that Cognition ships its own SWE-2 and SWE-1.7 models and a Fusion harness for Fable and Astra in Desktop and CLI.
Which one handles bugs discovered in production monitoring?
Cognition's auto-triage monitors bugs and generates fix pull requests automatically; Foreman has no equivalent monitoring hook in the provided data — it starts from a repository and your declared intent.
Is Foreman usable on a Mac?
Only under WSL2, per its own not-for guidance, which also flags that it drives headless Claude Code exclusively — non-Anthropic stacks are out.
How would I measure whether the agent is actually improving?
Foreman ships an evals flywheel: outcome-labelled runs, retro clustering failures into gated patches, and bench replays reporting success-rate, cost and turn deltas. Cognition's comparable signal is FrontierCode 1.1 rubric scoring on merge-worthiness.
More foreman or Cognition AI comparisons
These are not competing purchases: Cognition sells Devin, an enterprise autonomous software engineer with contact pricing, $1B+ annualized revenue, AWS and FedRAMP-track positioning. FanBox is a free,
These do not compete, so a head-to-head decision is the wrong frame. If you code in Claude Code or Opencode and lose your first prompts re-explaining the project, Recall is free and fixes that today w
These two products do not belong in the same evaluation. Cognition's Devin is an enterprise autonomous engineer that lives inside your repo, opens merge-ready PRs, runs in native Windows and Android e
You are almost never choosing between these two. Cognition's Devin is the agent that writes and ships the work — an enterprise contract, native Windows and Android build environments, auto-triage, a v
These are not substitutes, so the honest guidance is: don't pick between them. If you're an individual developer on a Claude Code Pro plan paying per response, Value-for-Fable is free to try and the r
These aren't rivals — they're opposite ends of the same pipeline, and the honest answer is that an AI-native team can run both: Devin writes the PR, TestSprite verifies the merge. If your constraint i
Explore each tool further
Browse these categories
One email a week — new tools, honest comparisons, no spam.
Last reviewed: October 17, 2026