What’s new in fak

In one breath: This page groups recent witnessed fak changes into human-readable themes. Each item names its shipped or planned scope and links to proof. It is current through commit 9a0fb818e on 2026-09-01.

Every entry below is one commit that carries a per-leaf ship stamp, so each line is traceable to repository evidence rather than to a hand-written claim. The page is refreshed by one committed command, and it summarizes — it is not a complete changelog and it promises no release cadence.

What does this page cover?

It covers the 7 days of repository history ending 2026-09-01: 1424 stamped changes across 1470 non-merge commits, grouped into the themes below. The repository release marker at that commit is 0.45.0.

A stamped change is a commit whose subject carries a (fak <leaf>) trailer — the same witness the commit-message gate and the marketing feeds bind to. Every entry carries the scope it may be claimed at:

Scope What it means How it is decided
shipped The change landed on trunk and its subsystem is claimed as shipped. Stamped commit whose leaf and issue pass the CLAIMS.md honesty ledger.
research/plan A plan, note, or experiment — not a capability you can use. Every path the commit touched is a research, planning, or notes surface.
landed, not claimed shipped Real work landed, but the capability is still [SIMULATED]/[STUB]. CLAIMS.md still tags the commit’s leaf or issue as unshipped.

How fresh is this page, and how is it refreshed?

The freshness boundary is explicit and machine-checkable — the page carries the commit it was folded from, so staleness is a computation rather than a judgement call.

Field Value
Current through 9a0fb818ed8880e1b010b6d76e0d0bf49ff50024
Commit date 2026-09-01
Range folded 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024
Counted 1424 stamped changes / 1470 non-merge commits
Generator module internal/marketing@r28+g3be545f40
Source of truth git log + linked GitHub issues + CLAIMS.md, folded by the derived generator module above
Refresh fak marketing whats-new --write
Staleness check fak marketing whats-new --check --json (default ceiling: 7 commit-date days or 250 non-merge commits behind)

fak marketing whats-new --check reads that anchor, measures how far HEAD has moved past it, and regenerates the page over the recorded range. It exits non-zero when the page is older than the allowed window or no longer matches what the repository says, so a hand edit or a rotted snapshot is reported instead of trusted. Nothing on this page is maintained by hand: the only curated content in the generator is the theme titles and their “why it matters” lines, which describe subsystems rather than individual changes.

What changed recently?

Each theme names why its subsystems matter, then lists its most user-facing changes newest-first. Features and fixes are listed before supporting work, and every theme states how many changes it counted so the summary never hides its own truncation.

Micro-agents and micro-context

Why it matters: These subsystems decide what a model actually sees: which context is resident, what is paged out, and how a small agent is handed only the slice it needs. Work here changes token cost and answer quality on the same hardware.

In this window: 33 stamped changes across ctxplan, headroom, trajectory — 13 feature(s), 14 fix(es), 6 supporting change(s).

29 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Context filtering and tool integration

Why it matters: The gateway, capability index, and tool-process seams are where another agent or client plugs into fak, and where results are screened before they reach the model. Work here changes what integrations are possible and what a tool call is allowed to return.

In this window: 26 stamped changes across capindex, gateway, mcp — 10 feature(s), 12 fix(es), 4 supporting change(s).

22 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Fleet, dispatch, and account routing

Why it matters: These subsystems run many sessions across many machines and accounts: which worker picks up which unit of work, which seat or endpoint serves it, and how a stalled or leaked lease is recovered. Work here changes throughput and operational safety of a fleet.

In this window: 48 stamped changes across accounts, dispatchtick, dos, fleetaccounts, launchshim, leaseref and 2 more — 12 feature(s), 18 fix(es), 18 supporting change(s).

44 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Model runtime, kernels, and caching

Why it matters: The loader, compute kernels, and cache tiers are the hot path: they decide how fast a token is produced and how much of a prior context is reused instead of recomputed. Work here shows up as latency and cost, not as new surface.

In this window: 147 stamped changes across cachevalueledger, cachevaluereport, compute, ggufload, metrics, model and 3 more — 55 feature(s), 26 fix(es), 66 supporting change(s).

143 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Policy, adjudication, and audit

Why it matters: Policy and adjudication are the boundary that blocks a poisoned result or a destructive operation, and the audit trail is what proves the boundary held. Work here changes what an agent is allowed to do and what evidence you keep afterwards.

In this window: 41 stamped changes across adjudicator, architest, guard, hooks, quality, usagelog — 6 feature(s), 21 fix(es), 14 supporting change(s).

37 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Documentation and discoverability

Why it matters: These changes maintain the pages, indexes, and machine-readable feeds a reader or answer engine uses to find the right authority. Work here changes what is findable, not what the kernel does.

In this window: 261 stamped changes across devindex, docs — 2 feature(s), 15 fix(es), 244 supporting change(s), 104 research/plan.

257 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Command line and developer workflow

Why it matters: The fak verbs and the repository’s own tooling are how both humans and automated contributors drive everything above. Work here changes the commands you run, not the behavior they govern.

In this window: 240 stamped changes across agent, cmd, gitdaily, tools — 64 feature(s), 104 fix(es), 72 supporting change(s).

236 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Other maintained subsystems

Why it matters: These are witnessed changes in subsystems no theme above claims yet. They are listed rather than dropped so the totals on this page reconcile with git history; the theme table in internal/marketing/recentchanges.go is where a leaf graduates into a named theme.

In this window: 628 stamped changes across abi, affectedtests, agentic, agenticbench, agenticbenchcoverage, agentquery and 209 more — 250 feature(s), 176 fix(es), 202 supporting change(s), 14 research/plan.

624 further change(s) in this theme are counted but not listed. To read the complete stamped history for this range and filter by the subsystems above:

git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak "

Where can I verify each item?

Every line above is a commit sha, and the sha is the verification. From a checkout:

git show <sha>                                   # the exact diff behind any line above
git log --no-merges --oneline 2523ce149c36a3cf5c9f8338ddc743090f97c8bc..9a0fb818ed8880e1b010b6d76e0d0bf49ff50024 --grep "(fak <leaf>)"   # every counted change in one subsystem
fak version modules --only internal/marketing    # current derived module@rev identity
fak marketing whats-new --check --json                # this page's own freshness, as JSON

Each entry also links its commit on GitHub and, when the subject names one, the issue that scoped it. Scope labels come from CLAIMS.md, which records what is shipped, simulated, or stubbed; tagged release notes live in the release-notes index. The generator identity above uses the repository’s derived module@rev contract, pinned to the page’s anchor rather than borrowed from whatever binary performs the refresh.

What this page does not claim

Where to go next

This page is a recent-changes view, not a general entry point. For anything other than “what changed lately”, use the authority that owns it: