Resources

Changelog

What shipped, when. Newest first.

Braingent versions the starter template and the CLI together. Both follow SemVer. Records you wrote in one version will always read correctly in the next; frontmatter additions are backwards-compatible and removals are versioned migrations.

Latest

12 October 2026: 1.3.0

  • Weekly plan. braingent weekly and braingent weekly-add keep one human-written weekly/YYYY-Www.md per ISO week with Priorities, Notes and Not this week, plus a Progress block rolled up from the week’s daily logs. Unticked priorities and notes carry into the next week. Agents read it before choosing work, and workflows/daily-pm.md reports against it.
  • Carry-over and agent entry points. Plain notes survive carry-over alongside unticked checklists. Claude and ChatGPT starter instructions also load the weekly plan before choosing work.

7 October 2026: 1.2.0

  • Epics. An epic is an ad hoc anchor for work that spans many tickets and repositories. It has a page at orgs/<org>/epics/epic--<org>--<slug>/, an optional epic: list on records, a tracker and PR label epic:<slug>, and braingent new epic to scaffold it. Dangling epic references fail validation.
  • Config-to-enable ledger. A config-to-enable/v1 YAML block records each setting that must be set before work is live, where it lives and its status. braingent config-ledger merges the blocks in labelled PR bodies with the epic page and can --sync the page.
  • Config drift. braingent config-drift --contracts <dir> --deployed <dir> reports environment keys present in one place and missing from the other.
  • Epic indexes and queries. reindex writes indexes/epics.md and indexes/config-ledger.md, adds an Active epics section to CURRENT_STATE.md, and fills record_epics and config_items in the SQLite cache. find, recall, synthesize and MCP braingent_find accept --epic.
  • Daily log. braingent daily-log --epic tags events, the status block rolls up spawned work per epic, and the sprawl warning names the epics behind it. Lines without an epic are unchanged.
  • Fix. braingent --root <dir> reindex writes the SQLite cache under the selected root instead of the directory the package was imported from.

6 October 2026: 1.1.0

  • Daily log. braingent daily-log and braingent daily-status keep one append-only daily/YYYY-MM-DD.md per day across every agent, with a generated ongoing/review/blocked/todo/done view, carry-over of unfinished work, and a sprawl warning at [daily] sprawl_threshold. workflows/daily-pm.md adds a PM catch-up agent that reconciles GitHub, the issue tracker, and Braingent records.
  • Reliable concurrent logging. Readers and writers share file locks, human Goals are preserved, and only Log entries affect status. Windows uses its native locking backend.
  • Deterministic indexes. CURRENT_STATE.md reports the latest source-record date, so unchanged indexes remain current across midnight.
  • CLI version string. braingent --version reports the package version instead of a leftover 0.1.0.
  • Dependencies. Refreshed Python tooling, MCP, website and example dashboard packages; Python 3.14 joins the supported CI matrix.

17 September 2026: 1.0.1

  • PyPI republish. 1.0.0 is already on PyPI (26 June 2026) and cannot be replaced. This patch ships the post-1.0 work: MCP SDK 2.2 (MCPServer), braingent factcheck, token-efficient retrieval, and hatchling metadata 2.5 with a matching publish action.

2026-06-26 — 1.0.0

  • Stable package metadata. The braingent Python package is now versioned as 1.0.0 and marked Production/Stable on PyPI.
  • Stable starter-template baseline. The packaged starter template manifest now reports 1.0.0, making the current memory repo shape the first stable baseline for braingent init and braingent update.
  • Release baseline. This release includes the hardened publishing pipeline, optional config.toml, built-in secret scanning, MCP retrieval tools, QA test planning, and the refreshed Node 24 website/example dependency baseline.

2026-06-16 — 0.1.1

  • Optional config.toml. braingent now reads .braingent/config.toml (repo-local) and ~/.braingent/config.toml (user-level). Supports [safety] forbid patterns/paths enforced by doctor, [doctor]/[recall] default knobs, and [task_ids] prefix/pad. See Configuration.
  • Built-in secret scanning in doctor. Always-on patterns for AWS, GitHub, Google, and OpenAI/Anthropic keys plus PEM private keys; config can add more.
  • Hardening. braingent_get (MCP) is restricted to Markdown records; release tooling pins all GitHub Actions by SHA and verifies build provenance before publishing.

2026-05-20 — Python package flow

  • pipx install braingent is the primary install path.
  • braingent init creates a private memory repo from the packaged template.
  • braingent update reports add/update/conflict status before applying starter-template changes.
  • braingent qa generate ships the QA plan generator with Markdown, Xray JSON, TestRail CSV, and Gherkin outputs.
  • braingent mcp serve --path <repo> starts MCP retrieval tools for agents.
  • Release checks now include package build, wheel smoke, metadata validation, and extracted-artifact safety scanning.

2026-05-07 — Documentation, public site

2026-04-30 — QA generation v4

  • Strict, reviewable QA plans from ticket + memory + evidence.
  • Output formats: Markdown, Xray JSON, TestRail CSV, Gherkin.
  • Deterministic precheck for AC coverage, duplicates, weak expected results, and evidence truncation.
  • Native Gather Step integration via --gather-workspace and --gather-target.

2026-04-15 — Live multi-agent tasks

  • tasks/active/BGT-NNNN.md convention for parallel agent coordination.
  • braingent task-* commands for create, claim, comment, status, list, and archive.
  • Optional local Bun + Astro dashboard renders the live queue.

2026-04-01 — Source-indexed synthesis

  • braingent synthesize produces synthesis pages with inline citations back to source records.
  • Topic / repo / project synthesis modes.

2026-03-15 — MCP server

  • braingent mcp serve exposes braingent_guide, braingent_find, and braingent_get over MCP.
  • Token-efficient retrieval for Claude, Codex, and any MCP-aware agent.

2026-03-01 — Core memory commands

  • braingent doctor health checks.
  • braingent find / braingent recall.
  • braingent validate / braingent reindex.

2026-02-15 — Starter template

  • Eight record kinds: task, decision, review, learning, repo, project, topic, tool.
  • Five memory surfaces formalized.
  • Agent entrypoints for Claude, Codex, ChatGPT, Gemini CLI.
  • Workflows for index-repo, cleanup-braingent, retrieve-context.

2026-01-10 — Public manifesto

  • First public release of the Braingent manifesto repo.

Upgrade Notes

Check available starter-template updates with:

braingent update ~/Documents/repos/braingent --dry-run

Apply non-conflicting updates with:

braingent update ~/Documents/repos/braingent --write
braingent doctor
braingent validate
braingent reindex --check