mirror of
https://github.com/Significant-Gravitas/AutoGPT.git
synced 2026-02-11 23:35:25 -05:00
b84bc469c9
## Summary - Adds a new **Changelog** section to the platform docs sidebar navigation - Creates the first bi-weekly changelog entry covering January 29 – February 11, 2026 - Establishes the directory structure (`docs/platform/changelog/`) for future entries ### What's included in the changelog entry The entry covers voice input, persistent file workspace, Claude Opus 4.6 upgrade, marketplace agent customization, rebuilt chat streaming (Vercel AI SDK migration), reconnection during long tasks, agent creation UX improvements, homepage redesign, and agent library reuse — plus collapsible sections for smaller improvements and fixes. ### How to add future entries 1. Create a new markdown file in `docs/platform/changelog/` (e.g., `february-12-february-25-2026.md`) 2. Add a link to `docs/platform/SUMMARY.md` under the Changelog section ## Test plan - [ ] Verify the Changelog section appears in the GitBook sidebar after merge - [ ] Verify the changelog entry renders correctly (headings, table, collapsible sections) - [ ] Verify navigation between the changelog index and the entry works 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h2>Greptile Overview</h2> <details><summary><h3>Greptile Summary</h3></summary> Adds a new **Changelog** section to the platform documentation with the first bi-weekly entry (January 29 – February 11, 2026). The changelog documents major platform updates including voice input, persistent file workspace, Claude Opus 4.6 upgrade, marketplace agent customization, rebuilt chat streaming, reconnection during long tasks, agent creation UX improvements, homepage redesign, and agent library reuse. **Key changes:** - Created `docs/platform/changelog/` directory with a landing page (`README.md`) and the first entry - Added "Changelog" section to `SUMMARY.md` navigation with proper GitBook structure - Used collapsible `<details>` sections for minor improvements and fixes to keep the changelog scannable - Follows existing documentation patterns with clear headings, GitBook hint blocks, and markdown tables The structure allows for easy addition of future entries by creating new markdown files and linking them in `SUMMARY.md`. </details> <details><summary><h3>Confidence Score: 5/5</h3></summary> - This PR is safe to merge with minimal risk - it only adds documentation files. - The PR introduces only new documentation files with no code changes. The changelog structure follows GitBook conventions correctly, uses proper markdown formatting, and integrates cleanly into the existing documentation navigation. All files are well-formatted with clear headings, proper use of GitBook hint blocks, and collapsible sections for organization. - No files require special attention </details> <!-- greptile_other_comments_section --> <!-- /greptile_comment --> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>