foreman vs Cognition AI

Side-by-side comparison of features, pricing, and ratings

Analysis reviewed Live tool data as of 2026-10-22
Cross-checked through our multi-step verification ·
Saved

At a glance

DimensionforemanCognition AI
PricingFree (MIT), you pay Claude API/CLI usageContact sales; enterprise contract
DeploymentLocal TUI, runs your installed claude CLI; macOS/Windows need WSL2Vendor-hosted Devin, Desktop and CLI, Slack/Teams/IDE integrations
Model dependencyClaude Code onlyCognition's own models: SWE-2, SWE-1.7, plus Fusion harness for Fable/Astra
Process modelFixed gated pipeline: plan, ADR/PRD, issues, TDD, e2eTicket-to-PR autonomous loop with auto-triage and review-comment fixes
Cost controlsPer-run turn/cost/time budgets plus daily hard ceiling; demo mode at zero token costNot disclosed in provided data
Ecosystem hooksClaude Code, gitGitHub, GitLab, Bitbucket, Jira, Linear, Slack, Teams, PagerDuty, Databricks, MongoDB, Windsurf
foreman
foreman

An MIT-licensed orchestrator TUI that supervises headless Claude Code agents through a gated plan → ADR/PRD → issues → TDD → e2e delivery pipeline

Visit Website
Cognition AI
Cognition AI

Cognition builds Devin, an autonomous AI software engineer that takes a ticket to a merge-ready pull request.

Visit Website
Pricing
Free
Contact Sales
Plans
$0
Custom
Popularity
13 views
7.3k views
Skill Level
Intermediate
Advanced
API Available
Platforms
CLI
WebDesktopAPICLI
Categories
🛠️ Autonomous Coding Agents🛡️ AI Governance & Guardrails
🛠️ Autonomous Coding Agents
Features
Supervises headless Claude Code agents from a keyboard-driven Textual TUI
Gated pipeline: plan → ADR/PRD → issues → TDD build → e2e
Human-in-the-loop review gates on every design phase
Hash-sealed approvals that auto-revert if a design doc changes
Per-run turn, cost, and time budgets enforced by the orchestrator
Daily cost ceiling with a hard stop
PreToolUse deny hook blocks workers from writing their own verification
Worktree isolation for parallel workers, gated by a declared touches set
Crash-safe state as human-readable committed files — no database
Demo mode runs the full pipeline on a mocked backend at zero token cost
Evals flywheel: outcome-labelled runs, foreman retro clusters failures into gated patches
foreman bench replays the eval set and reports success-rate, cost, and turn deltas
Vendored foreman-* skills installed into .claude/skills/ by foreman init
YAML configuration via config.sample.yaml
CLI commands: foreman init, build, status, retro, bench
Autonomous planning, coding, testing and pull request creation in your repository
SWE-2 coding model with multiple effort levels (September 10, 2026)
SWE-1.7 coding model positioned for capability at lower inference cost
Fusion model harness in Devin Desktop and CLI, up to 39% efficiency claim
FrontierCode 1.1 benchmark scoring merge-worthiness, not just test-passing
Auto-Triage of monitored bugs with automated fix pull requests
Security Vulnerability Remediation Program for clearing backlog findings
Session persistence so long-running jobs survive restarts
Scheduled Sessions that retain state across recurring runs
Auto-fixes for review comments on open pull requests
Embedded IDE takeover plus an interactive browser the agent drives itself
Devin for Terminal CLI with /handoff into a cloud session
Voice mode for instructing Devin inside a session
Native Windows VMs and an Android emulator for mobile testing
Devin Desktop and mobile apps for monitoring sessions
Integrations
Claude Code
git
Slack
Microsoft Teams
GitHub
GitLab
Bitbucket
Linear
Jira
Databricks
MongoDB
PagerDuty
Pylon

What 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 daily
    Pick: 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 budget
    Pick: 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 backlog
    Pick: 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 loop
    Pick: Cognition AI

    Native Windows VMs and an Android emulator are part of Devin's environment; Foreman is repository-and-git only.

  • Regulated or government agency
    Pick: 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

Explore each tool further

Browse these categories

Still deciding? Get the weekly AI tools brief

One email a week — new tools, honest comparisons, no spam.

Last reviewed: October 17, 2026