Skip to content

Project

TrueForge

TrueFoundry's open source agent harness for building, deploying, debugging and governing production agents on any model or MCP server.

Known aliases

  • @truefoundry/trueforge-core

Current stories

buildOne report1 publisher

Ten stalled runs beside ten clean controls is what Verdict accepts as a reproduction

The harness hands the verdict to a pure reducer reading a run ledger, so the model can gather observations but cannot upgrade them. The cost is that your bug has to fit an approved command and a fixed budget.

Publishers:dev.to

Reality

Evidence45
Adoption5
Hype gap+15
Incentives45
Confidence55
buildOne report1 publisher

A missing MCP annotation walks TrueForge's rollback tool past its own approval gate

TrueForge sorts tools by readOnlyHint and destructiveHint, so a tool declaring neither matches no tag in the approval policy and nothing asks before it touches production, which is why the default has to be deny at both enforcement points.

Publishers:dev.to

Reality

Evidence58
Adoption14
Hype gap+12
Incentives62
Confidence60
buildOne report1 publisher

Merging two green branches erased a HIGH-severity fix from package.json

A developer spent a week on an agent that bumps vulnerable dependencies and repairs the breakage, and the repairs were the easy part; his log of how each failure reported success while being wrong is the useful artifact.

Publishers:dev.to

Reality

Evidence48
Adoption10
Hype gap−15
Incentives55
Confidence55
buildOne report1 publisher

Airlock's per-case proxy enforces what a tool's readOnlyHint only claims

An MCP server writes its own danger label, so a harness gating approval on annotations is asking the suspect for its record. Airlock exercises the tools first, then puts the resulting policy in front of every call.

Publishers:dev.to

Reality

Evidence47
Adoption11
Hype gap+12
Incentives76
Confidence41