Bump the version and write a CHANGELOG.md release-notes entry after a user-facing change ships. Use when asked to "bump the version", "cut a release", "add a changelog entry", or "write release notes". Produces one minimal, user-facing, technical bullet per change.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Two files, one commit. VERSION drives the release; CHANGELOG.md is the
human-readable history.
VERSION — a single line, MAJOR.MINOR.PATCH (e.g. 0.0.448). The
Release workflow (.github/workflows/release.yml) reads it, tags vX.Y.Z,
and extracts the matching CHANGELOG.md section as the GitHub release body.CHANGELOG.md — newest version first. Served to users at /changelog
(parsed by backend/app/routes/changelog.py), so the format is load-bearing.VERSION. Increment the patch by one (0.0.448 → 0.0.449)
unless told otherwise. No leading spaces, no trailing newline changes —
just the number.CHANGELOG.md, directly under
# Release Notes:
## Version <new-version> (<Month DD, YYYY>)
- <One short line stating the change> (#<PR>)
July 12, 2026. One bullet per user-facing
change; group the whole release under this single version heading.Bump version to <X.Y.Z> with changelog entry.One short plain line per change. That's the whole note.
- Added Google Chat as a new chat channel (#771)
Added …, Fixed …, Renamed …, Removed ….(#PR) — the pull request number, if known. Omit if there's no PR. — detail clause when the user needs a concrete knob to
use the change (a setting name, env var, or changed default). One clause,
not a sentence.<name>, acme) if an example needs one.Feature:
- Added Google Chat as a new chat channel (#771)
Feature with a knob (the only case that earns a detail clause):
- Added concurrent multi-tool execution (#598) — controlled by the `ai_tool_concurrency` org setting (default 4)
Fix:
- Fixed iOS focus-zoom on the report prompt box (#600)
Config/model change (no PR):
- Updated OpenAI model presets — GPT-5.6 Terra is the new default
A full release section:
## Version 0.0.438 (July 7, 2026)
- Added Triggers: webhooks that spawn agent sessions, under a new Automations page (#562)
- Added per-file QVD indexing progress with stop, size, and duration (#564)
- Fixed WhatsApp delivery of agent replies and verification-page branding (#565)
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a new data source / connection type (e.g. a SQL Server-like database) end to end — client with get_schemas/execute_query, config + credentials schemas, registry entry, icon, tests — plus the verification steps. Also covers adding or updating an MCP connector (a preset, not a new type). Use when adding or significantly extending a connector.
The English summary is being prepared. Showing the original description.
Add a new LLM model to the preset catalog, or a whole new LLM provider — with the mandatory pre-flight verification of model id, pricing, and context window against the provider's official docs. Use when asked to add/update LLM models, providers, or pricing.
The English summary is being prepared. Showing the original description.
Query, visualize, and analyze data in a Bag of Words (BOW) workspace via the bagofwords MCP tools. Use for creating reports, running tracked queries, and building dashboards.
The English summary is being prepared. Showing the original description.
Update the product docs at docs.bagofwords.com (Mintlify) with text and fresh screenshots after a user-facing change ships. Use when a merged change alters user-visible behavior, adds a feature, or when asked to update/refresh documentation.
The English summary is being prepared. Showing the original description.
The locale/i18n architecture of bagofwords — catalogs, resolution order, RTL, backend contracts — and the procedures for adding strings, adding a locale, or translating UI. Use when adding/changing user-facing strings, working on RTL, emails, localized errors, or anything locale-related.
The English summary is being prepared. Showing the original description.
Run a live QA pass over the app — first map all user-facing functionality, then boot the full stack and manually exercise flows with Playwright, recording pass/fail evidence and filing a QA report. Use for release QA, post-merge smoke passes, or "QA the app / this area" requests.
The English summary is being prepared. Showing the original description.