Changelog
FluentBot ships continuously. Notable user-facing changes are recorded here, newest first.
Conventions
- Added — new feature you can use today.
- Improved — existing feature is better; no migration needed.
- Changed — visible behavior is different; check if you depend on the old behavior.
- Fixed — bug fix.
- Deprecated — feature still works but will be removed in a future release.
- Removed — feature no longer exists.
Breaking changes (anything that requires a user action to keep working) are flagged with 🔴 Breaking and listed first.
Latest
Code sources
- Added — index a software repository as a knowledge source. Connect a GitHub Repo through the FluentBot Connector app, or upload a Codebase (zip). Your bot can now answer questions and produce code examples from your own source. Secrets, dependency/build directories, lockfiles, and binaries are skipped automatically; detected secrets are redacted. See Knowledge Sources → Code.
- Added — connect multiple GitHub accounts and organizations, managed from the GitHub tab on the Knowledge Base page (disconnecting uninstalls the app from GitHub).
- Added — a Playground temperature control (saved per browser) and a bot Settings page with a Purge chat cache action.
For detailed release history, use the release notes published by the FluentBot team.
Subscribing to updates
- In-app banner — the dashboard shows release notes briefly when a new build deploys.
- Email — billing-impacting changes (plan adjustments, retired features) trigger a separate email to team owners.
- RSS / Atom — not currently provided.
What you’ll not see here
- Behind-the-scenes maintenance with no user-visible effect.
- Security patches (disclosed responsibly through separate channels).
- Plan or pricing changes (announced through email and the Plans & Billing page).
Reporting issues with a release
If a release breaks something on your end:
- Open the Feedback page in your dashboard.
- Include the release date, the affected bot, and exact steps to reproduce.
What’s next
- Plans & Billing — for pricing-impacting announcements.
- Feedback — report a regression you saw after a release.