What changed

You can now perform bulk actions on documentation review items! Within a documentation page or the action items list, you can use the newly added checkboxes to select multiple review suggestions and accept, reject, or mark them as resolved externally all at once.

What changed

To help keep your knowledge base up to date and clean, Solo will now send you a direct message in Slack to remind you about documentation drafts that have been open for over two weeks. This makes it easier to track which drafts need to be finished or discarded.

What changed

We've added a new filter to the documentation action items page. You can now easily filter pending review suggestions by specific feature flags, helping you prioritize documentation updates related to particular product releases.

What changed

The documentation parser has been improved to fully support markdown images that include title attributes (e.g., ![alt text](image-url "Image Title")). Solo can now correctly identify, extract, and suggest updates for these images during documentation review runs.

What changed

Businesses can now be configured to run documentation reviews in a text-only mode. When enabled, Solo will only suggest text replacements based on code changes and will bypass evaluating or suggesting updates for potentially outdated images.

What changed

When syncing documentation from Intercom, Solo now accurately maps and associates synced articles with their respective parent collection names, providing better categorization and context within the system.

What changed

We've added the ability to configure custom, business-specific instructions for the AI. This allows you to define specific guidelines that Solo will follow when identifying and proposing documentation updates or answering code queries.

What changed

For users utilizing a "Blume" docs-as-code setup with GitHub, Solo now supports mapping the internal GitHub file paths to your live, public documentation URLs. This ensures the "View Page" links route you accurately to the live published article.

What changed

We've upgraded the GitHub documentation sync logic to reliably process massive updates. If a branch update includes more than 300 changed files, Solo will automatically paginate through the individual commits to ensure no file changes are missed.

What changed

MDX documentation files containing literal expression tags (like {variableName}) are now safely escaped and rendered as plain text within the Solo UI, preventing rendering crashes.

What changed

The automated browser agent (used for image flows and navigation) has been upgraded with a new tool to simulate complex keyboard presses, allowing it to trigger keyboard shortcuts like "Shift+Escape" or "Enter" to navigate more complex UI elements.

What changed

You can now easily remove individual items from multi-select combobox dropdowns across the application by clicking the new "x" button on the selected item's badge.

What changed

Users can now optionally enter a custom branch name when accepting an individual documentation review or bulk-accepting multiple reviews. This gives you more control over which branch the updates are pushed to in GitHub, rather than relying on a Solo-generated branch name.

What changed

You can now exclude specific images from being automatically updated by our image automation feature. When an image is excluded, you will be prompted to manually upload the replacement image instead of recording a browser flow. This is especially useful for images that are difficult to reproduce using the automated agent.

What changed

You can now add global, product-specific instructions in your Account Settings to guide the automated browser agent when capturing images. This allows you to provide tips for navigating your UI or handling edge cases (e.g., "Expand the workspace switcher before choosing a project") to ensure the agent captures the correct image.

What changed

A new filter has been added to the documentation action items page, allowing you to easily filter the pending review items by their suggestion type (Text or Image).

What changed

If your image flow recording involves navigating through multiple pages or opening new tabs, the session replay will now display multiple video tabs. You can easily switch between these tabs to review the agent's actions across different pages.

What changed

Our automated browser agent now supports retrieving and entering One-Time Passwords (OTP) received via email. This allows the agent to successfully log into platforms that require two-factor authentication when capturing your documentation images.

What changed

The browser agent used for capturing documentation images now supports performing drag-and-drop actions and resizing UI elements (e.g., resizing sidebars), allowing it to reliably recreate complex UI states.

What changed

When recording a new image flow, you can now view the outdated image that is being replaced directly within the setup dialog. This makes it easier to reference the original image and ensure the new recording captures the correct state.

What changed

When accepting an image update that uses relative image paths in your GitHub documentation repository, Solo now correctly replaces the actual image file in the repository branch and correctly updates the relative path in the markdown.

What changed

Users can now optionally enter a custom branch name when accepting an individual documentation review or bulk-accepting multiple reviews. This gives you more control over which branch the updates are pushed to in GitHub, rather than relying on a Solo-generated branch name.

What changed

You can now exclude specific images from being automatically updated by our image automation feature. When an image is excluded, you will be prompted to manually upload the replacement image instead of recording a browser flow. This is especially useful for images that are difficult to reproduce using the automated agent.

What changed

A new filter has been added to the documentation action items page, allowing you to easily filter the pending review items by their suggestion type (Text or Image).

What changed

When recording a new image flow, you can now view the outdated image that is being replaced directly within the setup dialog. This makes it easier to reference the original image and ensure the new recording captures the correct state.

What changed

When accepting an image update that uses relative image paths in your GitHub documentation repository, Solo now correctly replaces the actual image file in the repository branch and correctly updates the relative path in the markdown.

What changed

You can now add global, product-specific instructions in your Account Settings to guide the automated browser agent when capturing images. This allows you to provide tips for navigating your UI or handling edge cases (e.g., "Expand the workspace switcher before choosing a project") to ensure the agent captures the correct image.

What changed

If your image flow recording involves navigating through multiple pages or opening new tabs, the session replay will now display multiple video tabs. You can easily switch between these tabs to review the agent's actions across different pages.

What changed

Our automated browser agent now supports retrieving and entering One-Time Passwords (OTP) received via email. This allows the agent to successfully log into platforms that require two-factor authentication when capturing your documentation images.

What changed

The browser agent used for capturing documentation images now supports performing drag-and-drop actions and resizing UI elements (e.g., resizing sidebars), allowing it to reliably recreate complex UI states.

What changed

Superadmins can now easily remove team members from the workspace via the Account Settings. A confirmation dialog has been added to prevent accidental removals.

What changed

We have introduced Image Flows to help you keep your help center screenshots and images up to date automatically.

What changed

When reviewing AI-suggested documentation updates, you can now see a Why Solo suggested this change section. This provides a clear explanation of why the documentation copy or image should be updated based on the recent product changes.

What changed

If a documentation update automatically generates a Pull Request in GitHub, a View Github PR button will now appear directly on the review item, allowing you to quickly jump to the PR and review the changes.

What changed

We've added an exit confirmation dialog when you attempt to close a documentation task you are actively working on. This ensures you won't accidentally lose any unsaved changes or edits.

What changed

You now have the flexibility to easily toggle between a Visual (WYSIWYG) editor and a Markdown editor when editing your draft documentation content.

What changed

We have introduced Image Flows to help you keep your help center screenshots and images up to date automatically.

What changed

Ask Solo can now proactively find and present pending suggested documentation updates related to a feature you are asking about. It will prominently display clickable links to the documentation review URLs so you can easily review the suggestions directly from chat.

What changed

You can now connect your Pylon knowledge base to Ask Solo! This integration allows you to sync your Pylon articles, chat with your Pylon documentation to get instant answers, and publish new or updated documentation directly back to your Pylon collections.

What changed

You can now easily add or remove release note labels directly from the documentation review screen. Simply click the edit icon next to the labels to open a dropdown menu and update them without leaving the page.

What changed

To speed up your review workflow, we've added a "Review next article with items assigned to you" link at the bottom of the documentation review screen. This allows you to quickly jump to the next article that requires your attention without returning to the main list.

What changed

When viewing the version history of a documentation article, you now have the ability to easily restore a previous version. Clicking "Restore as draft" will apply the old content as a new draft, allowing you to review and publish the changes.

What changed

Ask Solo now automatically fetches and displays images stored inside your connected code repositories. If your markdown files reference images from the repo, they will now be correctly rendered directly within the documentation viewer.

What changed

You can now ask Solo to update your documentation directly from chat (such as Slack)! Simply ask Solo to run a documentation task and provide a description of the updates. Solo will create the task, execute it, and notify you when the updates are ready for review.

What changed

A new "Type" column has been added to the Documentation Action Items table. This column clearly indicates whether the suggested action item is a "Text" update or an "Image" update, helping you prioritize your review workload.

What changed

You can now connect your Pylon knowledge base to Ask Solo! This integration allows you to sync your Pylon articles, chat with your Pylon documentation to get instant answers, and publish new or updated documentation directly back to your Pylon collections.

What changed

You can now ask Solo to update your documentation directly from chat (such as Slack)! Simply ask Solo to run a documentation task and provide a description of the updates. Solo will create the task, execute it, and notify you when the updates are ready for review.

What changed

Our Linear integration has been improved to automatically sync new issues and projects in real-time. Additionally, you can now tag @asksolo in Linear agent sessions to prompt Solo to instantly analyze your codebase and provide a response.

What changed

We've upgraded the pagination across the app, including the Documentation, Action Items, Projects, Tasks, Questions, and Release Notes pages. Instead of simple "Previous" and "Next" buttons, you'll now see the current page, total number of pages, and the number of items per page, making it much easier to navigate through large lists.

What changed

Our Linear integration has been improved to automatically sync new issues and projects in real-time. Additionally, you can now tag @asksolo in Linear agent sessions to prompt Solo to instantly analyze your codebase and provide a response.

What changed

You can now easily add or remove release note labels directly from the documentation review screen. Simply click the edit icon next to the labels to open a dropdown menu and update them without leaving the page.

What changed

Users can now easily resize images directly within the documentation editor. By clicking on an image, drag handles will appear around it, allowing you to click and drag to adjust the width, height, or both simultaneously.

What changed

To improve visibility into what changes are live for mobile users, the system now automatically checks commits against the latest published version of your app on the App Store. When a code change is detected that hasn't been pushed to the App Store yet, a new Mobile (will be rolled out in next push to app store) label is automatically applied to the relevant documentation reviews and release note items.

What changed

When analyzing code diffs to suggest documentation updates, the system can now intelligently flag images that may be outdated. By evaluating the surrounding text and the related code changes, it will provide suggestions to review and potentially replace images that no longer match the current product behavior or user interface.

What changed

We have introduced a new setting to allow the system to write entirely new sections of documentation. If code diffs introduce new functionality that should belong in an existing article but isn't covered yet, the AI can now properly insert a new section with the relevant information rather than skipping it.

What changed

If a pending documentation review suggestion becomes outdated due to underlying document updates, the system will now automatically attempt to fix and re-evaluate the suggestion to ensure it remains relevant and accurate.

What changed

We have refined the logic that warns you about overwriting source changes when publishing a draft. The warning prompt will now only trigger if the source documentation was updated at least one minute after the draft was created, preventing unnecessary false alarms.

What changed

When creating a new documentation task, the description text area can now be vertically resized. This small but helpful change makes it much easier to write and review long task descriptions.

What changed

You can now manage your release notes more efficiently with bulk deletion. By selecting multiple checkboxes next to the release note items in edit mode, a new Delete items button will appear, allowing you to remove all selected items in a single action.

What changed

A floating Table of Contents has been added to the right side of the release notes editor. This feature automatically generates a list of all items within the release note, making it simple to overview the contents and quickly navigate to specific items by clicking on their titles.

What changed

To improve visibility into what changes are live for mobile users, the system now automatically checks commits against the latest published version of your app on the App Store. When a code change is detected that hasn't been pushed to the App Store yet, a new Mobile (will be rolled out in next push to app store) label is automatically applied to the relevant documentation reviews and release note items.

What changed

When grouped release notes are exported and sent via email, label headings (such as feature categories) will now be better formatted. Additional spacing is automatically inserted around headings to improve readability for the end user.

What changed

When generating release notes or documentation updates, the system now looks for issue tracker identifiers (like Linear or Jira tickets) within commit messages. If a ticket identifier is found, it automatically fetches the ticket's name and description to provide better context for generating accurate summaries and notes.

What changed

Improved the mechanism for exporting documentation updates to Notion. Updates are now pushed seamlessly as native Notion blocks instead of simply replacing text, and duplicated page title headers are correctly removed from the export.

What changed

Optimized the internal limits of how much context from various documentation sources (Website, Notion, Confluence, and GitHub Docs) is fetched and fed into the AI models, ultimately improving response relevance and generation speed.

What changed

Set a strict maximum character limit for the context provided to the Gemini AI models when querying changelogs or code diffs, preventing connection errors related to exceeding context windows on extremely large codebase repositories.

What changed

Adjusted the behavior for auto-generating empty documentation pages. The AI will now only automatically trigger content generation for documentations that were created within the past 30 minutes, giving users more control.

What changed

Added a user-friendly confirmation toast message ("The suggestion has been unsnoozed and is viewable in the 'Unreviewed' section") that appears after successfully unsnoozing a documentation review suggestion.

What changed

Updated the layout of documentation task sheets to better handle empty tasks. The "Edit and run" button will now properly remain available for tasks that have zero reviews generated, and the archive option will be hidden.

What changed

Fixed a formatting issue in the rich text editor where empty paragraphs or line breaks would visually lose their vertical spacing. Empty lines will now consistently maintain their proper height.

What changed

Improved the reliability of fetching large Slack message reply threads by adding pagination support and automatic retries to prevent failures caused by Slack API rate limits.

What changed

Optimized the internal limits of how much context from various documentation sources (Website, Notion, Confluence, and GitHub Docs) is fetched and fed into the AI models, ultimately improving response relevance and generation speed.

What changed

Set a strict maximum character limit for the context provided to the Gemini AI models when querying changelogs or code diffs, preventing connection errors related to exceeding context windows on extremely large codebase repositories.

What changed

The Repositories settings page has been enhanced to visually display the specific branch name connected to each repository. Additionally, an "Indexing..." status badge will now appear for new branches that are still being initially processed.

What changed

You can now integrate your GitLab repositories directly into Solo.

What changed

We've added native support for Front's Knowledge Base.

What changed

We've added native support for Front's Knowledge Base.

What changed

When publishing documentation updates to Help Scout from Solo, you now have additional controls.

What changed

Solo now detects and tracks translation status for your imported documentation, like Zendesk articles.

What changed

We've improved the visibility into Documentation Tasks. When a task completes, Solo now generates an AI-powered summary explaining exactly what was changed (or why no changes were made) for each article.

You can view these summaries by clicking into a task, which opens a new sliding side-sheet containing a breakdown of the task execution.

What changed

You can now create new documentation tasks directly from Slack threads. The system tracks the external message ID to ensure duplicate tasks aren't created from the same thread conversation.

What changed

Our rich text editor for documentation has been upgraded with new formatting options.

What changed

Never lose your unsaved edits again. The documentation editor now automatically saves your work in the background as a hidden draft while you type, preserving your changes even if you navigate away before officially saving.

What changed

Navigating suggested changes in the Review page is now smoother and more accurate.

Clicking on a specific change automatically scrolls to its exact location and temporarily highlights the background in yellow. It uses structural HTML matching, ensuring it jumps to the exact element even if the same text appears multiple times in the document.

What changed

You can now edit suggested documentation changes directly in the review screen. Clicking on the new text opens a full rich-text popup dialog, allowing you to easily tweak or rewrite the AI's suggested text before accepting it.

What changed

A new API endpoint has been added that allows you to retrieve your most recent release notes programmatically. The API response supports querying by date and allows enabling/disabling the inclusion of feature flags and labels.

What changed

We have added an HTML mode for viewing and editing documentation. Users can now easily toggle between Visual and HTML modes when viewing diffs between draft and published versions of an article, as well as when directly editing the content.

What changed

You can now quickly generate and share a preview link for your documentation drafts. A new "Share preview link" option has been added to the actions menu, allowing you to easily collaborate with others before publishing.

What changed

Your search and filter preferences on the Documentation Action Items page are now saved in your session. This means your filters will persist when you navigate away and return later. By default, the list will now also show action items assigned to you.

What changed

You can now use the Cmd/Ctrl + Click shortcut on any row in the documentation list to open that documentation article in a new browser tab, making it easier to review multiple articles at once.

What changed

We have added the ability to archive documentation tasks. When a task is archived, any pending documentation reviews associated with it will automatically be rejected to keep your workspace clean.

What changed

We have added a new snooze option for documentation reviews that are tied to feature flags. You can now snooze a review until its associated feature flag is fully turned on, keeping your documentation updates perfectly aligned with your product releases.

What changed

AskSolo now supports connecting and syncing your documentation updates directly with Featurebase and Help Scout. You can also import and track support conversations from Help Scout.

What changed

You can now create documentation tasks directly from Slack threads. AskSolo will automatically summarize the conversation thread to generate a concise task name and detailed description for the required documentation work.

What changed

When a documentation draft is canceled, any open comments that were left on that draft will now be automatically marked as resolved.

What changed

The system now provides better expert suggestions for documentation articles by looking at the original authors of imported external pages, in addition to identifying code committers.

What changed

When AskSolo successfully creates a GitHub Pull Request for your documentation updates, the associated documentation reviews are now automatically marked as approved.

What changed

You can now publish approved release notes directly into an external documentation platform (such as GitHub Docs). A new "Publish Externally" dialog allows you to select the specific documentation article where the release note should be appended.

What changed

AskSolo now supports connecting and syncing your documentation updates directly with Featurebase and Help Scout. You can also import and track support conversations from Help Scout.

What changed

You can now configure specific email addresses to be filtered out and ignored when importing customer conversations from Zendesk, Intercom, and Front. This helps keep out automated emails or unwanted senders from polluting your support insights.

What changed

You can now create documentation tasks directly from Slack threads. AskSolo will automatically summarize the conversation thread to generate a concise task name and detailed description for the required documentation work.

What changed

When answering questions based on Slack messages, AskSolo now automatically expands Slack List links to include the relevant list record details. This provides the AI with much better context for answering questions.

What changed

You can now connect Help Scout as a documentation source in Ask Solo. This integration allows Ask Solo to answer questions based on your Help Scout articles, automatically suggest documentation updates, and publish new or updated content directly back to your Help Scout knowledge base.

What changed

Ask Solo now integrates with Front to analyze your customer support conversations. By connecting Front, the Coverage feature can identify recurring customer questions and highlight documentation gaps, helping you proactively create articles that address your customers' needs.

What changed

Our Coverage feature now supports Zendesk tickets. Ask Solo will automatically analyze your closed Zendesk conversations to identify missing documentation and suggest new help center articles based on real customer inquiries.

What changed

We've added a "Resolved Externally" button to the Coverage opportunities list. If you've addressed a documentation gap outside of Ask Solo or decided it doesn't need an article, you can mark it as resolved externally to clear it from your opportunities queue.

What changed

You can now define specific exclusion rules for your documentation opportunities. Ask Solo will automatically filter out and archive any generated opportunity themes that match these exclusion criteria, keeping your coverage queue focused on the gaps you actually care about.

What changed

Collaborating on documentation drafts is now more seamless. If you mention an email address in a documentation review comment, Ask Solo will automatically send them an invitation to join the workspace as a Commentor and link them directly to the thread.

What changed

Ask Solo now supports Datadog feature flags. This integration allows the platform to extract feature flag states based on your rollout rules and environments, providing more accurate context for release notes and documentation tasks.

What changed

The coverage feature can now automatically merge multiple related opportunity themes into a single, comprehensive theme, helping to deduplicate your documentation gaps and keep your opportunities list clean.

What changed

We've added the ability to generate a public preview link for any documentation draft. This makes it easy to share proposed changes with external stakeholders or team members who don't have an Ask Solo account, allowing them to view the drafted content before it goes live.

What changed

You can now edit and re-run documentation tasks even after they have been marked as completed. When doing so, a warning will be displayed to let you know if any pending action items associated with the previous run will be overwritten.

What changed

Streamline your documentation workflow by creating new documentation tasks directly from release note items. Clicking "Create task" from a release note will automatically pre-fill the task form with the relevant changes and ticket links, making it easier to ensure your help center stays up to date with product updates.

What changed

When reviewing documentation updates, you can now toggle a split-view mode that highlights the exact differences between the proposed draft and the currently published version. This makes it much easier to see what content has been added, modified, or removed.

What changed

You can now upload custom CSS rules for your workspace. Ask Solo will apply this CSS to your documentation previews within the app, ensuring that the articles you review look exactly like they do in your live help center.

What changed

Managing your documentation review queue is now easier with the addition of a "Snoozed" filter on the Action Items page. This allows you to quickly view all the documentation suggestions you've temporarily postponed.

What changed

For teams using GitHub Docs, we've added a powerful new feature to bulk accept all pending documentation reviews. This action will automatically compile the accepted changes and open corresponding Pull Requests in your GitHub repository.

What changed

Ask Solo now automatically scans your documentation content to identify and flag any broken links, such as 404 errors or redirect loops. This helps ensure that your help center articles always direct customers to valid, working pages.

What changed

Streamline your documentation workflow by creating new documentation tasks directly from release note items. Clicking "Create task" from a release note will automatically pre-fill the task form with the relevant changes and ticket links, making it easier to ensure your help center stays up to date with product updates.

What changed

You can now define a custom prompt for release notes generation in your workspace settings. This allows you to give the AI specific instructions on the tone, formatting, and structure it should use when writing your release notes.

What changed

When generating and copying release notes, you can now use the label filter dropdown to select specific labels. The "Copy to clipboard" action will then only copy the formatted text for the labels you've selected, rather than the entire release note.

What changed

We've added validation to the Chat-with-Code tool that ensures incoming queries contain a clear question or information request before initiating a search, preventing empty or non-actionable queries from running.

What changed

Introduced a new Coverage page in the documentation section to provide insights into how well your help center addresses customer questions.

What changed

Added a new Documentation Tasks workflow to systematically update documentation using AI.

What changed

You can now assign specific team members to own documentation updates and release note items.

What changed

When creating a Jira ticket directly from a documentation action item, the generated ticket now includes a much more detailed description. It contains a summary of the change, a direct link to the article being updated, and a link to view the suggested AI change in Solo.

What changed

The rich-text documentation editor was upgraded to strictly preserve original HTML attributes (such as custom classes, styles, and data attributes) when importing or generating content. This ensures that custom formatting, sizing, and structural tags from your external knowledge base remain fully intact when editing in Solo.

What changed

Image assets uploaded within documentation are now hosted in a public-read bucket, ensuring they generate stable, permanent URLs. This prevents broken images when exporting or embedding the documentation externally.

What changed

We have introduced an OAuth-secured Model Context Protocol (MCP) server integration. This allows supported external tools and IDEs to securely query and read your product context, documentation, and codebase knowledge directly from Solo.

What changed

We have introduced an OAuth-secured Model Context Protocol (MCP) server integration. This allows supported external tools and IDEs to securely query and read your product context, documentation, and codebase knowledge directly from Solo.

What changed

We've completely overhauled the documentation editor to use a powerful new rich text editor. This update introduces several enhancements to make formatting and structuring your docs easier:

What changed

Collaboration on documentation is now much easier with the introduction of inline comments!

What changed

You can now save documentation changes as drafts and view the version history!

What changed

Keep your workflows synced by linking external task issues directly to your documentation action items.

What changed

We've introduced a "Knowledge Base Audit" option when creating or managing a Documentation Project. When enabled, it performs targeted document reviews and flags action items based heavily on your recent codebase changes to keep large projects up to date.

What changed

Sometimes you just want to write documentation from scratch without AI generation. We've added a "Write manually" option under the "Write Doc" dropdown on the documentation page, allowing you to instantly create a blank document and start typing.

What changed

We've added a new "Commentor" role for your team members. Commentors have restricted, read-only access to documentations where they can view the content and leave feedback via inline comments, but they are prevented from making edits or publishing drafts.

What changed

When viewing a release note item, you will now see helpful indicators if the feature is referenced in your existing knowledge base. Clicking on "referenced in X docs" or "tangential docs" opens a dialog to review all relevant documentation articles linked to the feature update.

What changed

You can now sort the Documentation tables by "Last Updated" and "Drafted Changes" columns in both ascending and descending order to better organize your list of documents.

What changed

When using Ask Solo Chat, you can now check the "Use style guide as context" box. This will instruct the AI to format and structure its response using your company's predefined external documentation voice and style guidelines.

What changed

We've added a new "Commentor" role for your team members. Commentors have restricted, read-only access to documentations where they can view the content and leave feedback via inline comments, but they are prevented from making edits or publishing drafts.

What changed

When viewing a release note item, you will now see helpful indicators if the feature is referenced in your existing knowledge base. Clicking on "referenced in X docs" or "tangential docs" opens a dialog to review all relevant documentation articles linked to the feature update.

What changed

You can now group related documentation together using Documentation Projects. This allows you to track specific coding efforts or features and associate relevant documentation.

What changed

We have improved our Markdown parsing capabilities to properly extract and display tables (including from Notion integrations). We've also fixed an issue where the page wouldn't reliably scroll to the highlighted text for markdown files when reviewing action items.

What changed

You can now configure how often Ask Solo scans your codebase to generate new documentation action items. Choose between Daily or Weekly intervals to fit your team's development cycle.

What changed

When accepting a documentation action item, the button will now display an "Accepting..." state. This prevents accidental double-clicks and provides clearer feedback while the documentation is being updated.

What changed

You can now group related documentation together using Documentation Projects. This allows you to track specific coding efforts or features and associate relevant documentation.

What changed

When manually generating release notes, you now have the option to specify a custom End Date , giving you more control over the exact timeframes of the release notes.

What changed

The Release Notes list view has been updated:

You can now opt to hide the default "What changed" and "Why it matters" headers in your release note items, allowing for a cleaner output if your team doesn't require those sections.

What changed

When you snooze or delete an item while reviewing release notes, the page will now automatically smoothly scroll to the next (or previous) item, making it easier to power through large lists.

What changed

We've added Front to our list of integrations! You can now authenticate and connect Ask Solo to Front to let Ask Solo automatically answer customer questions directly in your Front chat conversations.

What changed

Ask Solo can now answer user questions directly through email! It will read incoming questions, retain conversation history, and reply with accurate answers using your knowledge base.

What changed

You can now collapse the left navigation sidebar to save screen space. The sidebar state is remembered across sessions, and hovering over the collapsed sidebar will temporarily expand it for quick navigation.

What changed

The Chat interface in the web application has now been enabled for all users. You can access it directly from the left navigation sidebar under Chat.

What changed

Added the ability to manually edit Solo-generated documentation directly within the app. Users can switch to "Edit" mode to tweak the generated markdown content and save their changes before publishing.

What changed

Added a dialog prompt when rejecting a documentation review suggestion, allowing you to optionally provide a reason for the rejection. This helps keep track of why certain updates were ignored.

What changed

Introduced a new Chat interface where users can ask questions directly within the Solo web app. The interface supports conversational history and allows users to seamlessly switch between chat threads.

What changed

Improved the display of asked questions in the history tab by rendering them clearly in markdown. Additionally, exporting the questions list to CSV now includes whether the question was asked in a direct message and if the answer was marked as unhelpful.

What changed

Release notes now display the current rollout status (e.g., Fully On, Partially On, Fully Off) alongside feature flags linked in release note items, providing more visibility and context on which features are actively visible to users.

What changed

You can now assign a custom name to your release note schedules to easily identify and manage them in your schedule list view.

What changed

Users can now customize the order of release note labels. This custom ordering determines how the release note items are grouped and displayed when previewing in the web app or publishing to Slack.

What changed

Cleaned up the user interface by moving top-level buttons (like Copy to Clipboard, Copy for Slack, Export to CSV, View PR, and Archive) into a clean, unified dropdown action menu in the Documentation and Release Notes views.

What changed

When scheduling release notes or generating new documentation, you can now specify exactly which repositories Solo should use for context, rather than defaulting to all connected repositories.

What changed

When creating documentation, users can now upload reference files (.txt, .md, .pdf, .doc, .docx) as extra context to guide the content generation process.

What changed

After Solo generates a piece of documentation, users can now enter an Edit Mode to manually revise, refine, and save the content before it's finalized or published.

What changed

The Documentation Action Items table now includes a sort dropdown, allowing users to order the list by "Newest first" (Created at) or "Documentation title".

What changed

Users can now specify a detailed outline or a list of sections when generating documentation. Solo will structure the generated content to adhere closely to the provided sections.

What changed

The Documentation Action Items table now features a "Change Summary" column, allowing users to quickly gauge the scope and nature of the codebase changes triggering the action item without clicking into it.

What changed

Users can now use Command+Click (or Ctrl+Click on Windows) to open individual documentation action items in a new browser tab directly from the action items table.

What changed

Release notes can now be configured to require approvals before they are automatically published to external channels. Designated users can review, approve, or force publish release notes to ensure quality control.

What changed

Users can now export generated Release Notes into a CSV format. This makes it easier to integrate release notes with other tools or share them in external reports.

What changed

Users can now drag and drop release note labels in the settings to dictate their order. When release notes are generated and grouped by label, they will respect this custom ordering.

What changed

When setting up release note schedules, users can now specify email addresses for the To, CC, and BCC fields, ensuring all relevant stakeholders are notified appropriately.

What changed

Users can now interact with Ask Solo via a conversational chat interface. This feature supports continuous context across follow-up questions within a thread and keeps a history of past chats for easy reference.

What changed

The Questions tab UI has been improved to properly render questions and answers using Markdown, providing better readability for code snippets, lists, and bold text.

What changed

Users now have the option to target specific repositories when manually generating or scheduling documentation and release notes, ensuring content is tightly scoped to the selected codebases.

What changed

The Release Notes and Documentation Action Items pages will now show the rollout status (Fully On, Partially On, Fully Off) alongside the LaunchDarkly feature flags associated with a change.

What changed

The Questions CSV export now includes two new columns: "Direct message" and "Marked unhelpful", providing more context on how questions were asked and received.

What changed

Solo now supports deeper integrations with external platforms. This includes real-time webhook syncing for Zendesk articles and Jira tickets, as well as daily automated indexing for Confluence pages and Featurebase articles.February 2026

What changed

The Documentation Action Items (previously "Needs Review") page has been redesigned into a table view for better management. Key improvements include:

What changed

We have added full support for Featurebase integration. You can now:

What changed

We have added support for publishing documentation to Mintlify. Publishing to Mintlify will generate a Pull Request in the connected GitHub repository containing the new documentation and updates to the navigation configuration.

What changed

We have added full support for Featurebase integration. You can now:

What changed

We have improved the Jira integration by implementing Webhooks. This allows Solo to fetch and index recently updated Jira issues in real-time, ensuring your data is always up-to-date.

What changed

Added a new Chat API endpoint (api/chat_docs). This allows developers to programmatically query indexed documentation and retrieve answers via API.

What changed

You can now export release notes to a CSV file. This is useful for analyzing release data or importing it into other tools like Pendo.

What changed

Added an option to "Include all changes" when generating release notes. This allows you to generate notes based on all detected changes in the codebase, rather than just high-confidence product features.

What changed

LaunchDarkly feature flags are now integrated into the workflow:

What changed

Added a warning message when viewing or editing documentation that contains Zendesk Content Blocks to help prevent formatting issues.

​

What changed

You can now disconnect the Slack integration directly from the settings page.

​

What changed

You can now organize your release notes with custom labels. Features include:

What changed

Support has been added for configuring multiple automated release note schedules, allowing you to manage different reporting cadences simultaneously.

What changed

LaunchDarkly feature flags are now integrated into the workflow:

What changed

Added a new 'Edit Mode' for documentation that allows users to manually edit content or use AI to add new sections and rephrase existing text based on instructions. Changes can be previewed before accepting, and for GitHub-sourced documentation, accepted changes automatically create a Pull Request.

​

What changed

Introduced the ability to comment on individual release note items and tag team members. Also added a snoozing feature to hide specific items until the next release or a specified date.

​

What changed

Release notes now automatically identify and pull images from linked Pull Requests to display them within the generated release note items.

​

What changed

Introduced the ability to comment on individual release note items and tag team members. Also added a snoozing feature to hide specific items until the next release or a specified date.

​

What changed

Release notes now automatically identify and pull images from linked Pull Requests to display them within the generated release note items.

What changed

Introduced a new 'Typed Release Notes' system that generates structured changelogs broken down by individual items (Title, Change, Why it matters) rather than a single text block. Users can now manually create, edit, reorder, and delete items, as well as upload images/videos and view source link authors for each change.

What changed

Added an integration to fetch and analyze LaunchDarkly feature flags. The system now uses active feature flag configurations as context when answering questions, allowing it to provide more accurate answers regarding the current state of product features.

What changed

Enhanced the documentation review system to better support .mdx files. The AI prompt has been updated to specifically handle MDX syntax and ensure valid tag closure during documentation updates.

What changed

Fixed a user interface issue in the documentation review view where automatic scrolling to a specific change would fail if the content was hidden inside a collapsed element. The system now automatically expands parent details elements to ensure the relevant code is visible.

What changed

Upgraded the underlying AI model to Gemini 3 Pro Preview to provide better query responses and documentation generation.

​

What changed

A new commenting system has been added to documentation reviews. You can now discuss suggestions by adding comments and tagging team members with @mentions, which will notify them via Slack.

​

What changed

You can now connect Github repositories specifically for documentation to keep your help center automatically synced with your Markdown and MDX files. This includes support for indexing and creating Pull Requests for documentation updates.

​

We've completely redesigned the experience for managing and reviewing your documentation to make it faster and more intuitive.

Connect more of your tools and get better visibility into your data.

Save time with new automation features for your release notes.

Tailor the platform's output to perfectly match your company's style and workflow.

We've made it easier to get started and find help when you need it.

A new "Action Items" page has been added under the Documentation section. This page provides a centralized place to review all suggested updates to your documentation, which can be triggered in two ways:

You can now easily navigate between different documents that have pending action items from this single page.

​

You can now connect your Bitbucket and Zendesk accounts.

Additionally, the "Integrations" section in Account Settings has been redesigned with tabs for "All", "Chat", "Code", and "Documentation" to make managing your connections simpler.

​

The main navigation menu has been updated to be more intuitive. "Documentation" and "Integrations" are now organized into collapsible sections, containing related sub-pages like "Action Items" and "Repositories". This makes it easier to find the pages you need and reduces clutter.

​

You can now assign roles to team members for better access control. When inviting a new user, you can choose to invite them as a "Regular" user or an "Admin". The roles of existing team members can also be changed at any time from the "Team" section in your Account Settings.

​

The process for publishing new documentation has been improved. When you publish a document, you will now first select the destination, such as Notion or Intercom. After selecting the source, you can then choose the specific parent page (for Notion) or collection (for Intercom) where the new document should be created.

​