Skip to main content

In this release

Merge readiness in AI chat

Flow AI can check in one step whether a branch is ready to merge. It lists every blocking review, check, stage gate, editor group, and conflict. The chat shows the same status card as the review page. When the branch is ready to merge, you can merge it from the chat.

Redesigned GitHub integration settings

GitHub setup now ends with AI access. Choose repository browsing (on by default) and writeback (off by default), plus pull request review (on by default) and auto-review (off by default) for the current project’s repositories. The settings page shows connection status at a glance and explains the Review PR and Auto-review switches. Open an organization’s connection details from its name, find its actions in one menu, and disconnect it after confirming. Choose a project beneath Repositories to configure its pull request review and auto-review settings without leaving the page. GitHub activity stays under Settings → AI → Activity Log.

Improvements & Fixes

Agent

  • Unanswered questions. When Flow AI asks you something and you do not answer within two minutes, it continues with the work that does not need your answer. The question stays open on its card, and items that depend on it wait until you answer.
  • Long chats. Decisions made early in a long chat stay in Flow AI’s view, however long the chat runs. Flow AI can re-read an earlier part of the conversation word for word when a message refers to it.
  • Forked chats. A chat started from a message is now called a forked chat, and its title starts with “Forked chat:”.
  • Filtered responses. Responses blocked by the AI provider’s content filter show a clear warning, naming the filter category when the provider reports one. Earlier messages and completed changes remain available.
  • Item links on other branches. An item that is not on the chat’s current branch shows its name and branch, and opens on that branch, instead of “this item doesn’t exist”.

Branching

  • Branch wording. Activity, agent chats, the Inbox, sharing, and automation settings show branch wording and icons again, and you can filter the Inbox by branch.

Collaboration

  • @ mention search. Typing @ and a search term lists people and agents whose name matches before people whose email domain matches.

Diagrams

  • New diagrams. You can create a diagram from the + New menu in a Diagram view.

Formulas

  • Create referenced items. Typing = in a new item’s Description can create the item it references, such as a design value for a requirement. The new item opens in a dialog over the first one and keeps your unfinished draft.

Import and Export

  • ReqIF rich text. Imports keep bold text in more formats, including in table cells, and no longer add an empty line where a block ends in a line break. Exports keep Shift+Enter line breaks instead of turning them into spaces.

Integrations

  • One GitHub organization. Each workspace now connects one GitHub organization. Disconnect the current organization before connecting another. Repository review settings stay separate for each project and are kept when GitHub is disconnected.
  • Slack attachments. Project admins can let agents and automations inspect selected images, PDFs, text files, and CSVs attached to messages in an approved Slack channel. Existing channel grants stay text-only until attachment access is enabled.

Notifications

  • Inbox previews. Comment previews show their formatting, with people and items as pills. Agent replies, questions, and findings in the Inbox show their formatting and item pills.

Permissions and Sharing

  • Shares for editors. When editors may share views, they can open Settings → Shares to see and revoke the shares they created. Admins still see every share in the project.
  • Bulk revoke. Select shares in Settings → Shares to revoke them all at once from a bar at the bottom of the table. A share on a merged or closed branch shows the branch by name, marked Merged or Closed.

Review

  • Faster verification. Changed-item verification is faster in projects with many branches.
  • Merged review links. A link to a merged review in AI chat or comments shows and opens the baseline its merge created, instead of “review unavailable”.
  • Deleted branches and items. Filter deleted branches by who deleted them, owner, parent, tag, and when they were deleted or created. Filter deleted items by type, who archived them, owner, and when they were archived.
  • Shares table. Filter the shares table by any column, including whether a share’s branch was merged or closed. Search also matches the sharer, branch, view, and starting item.
  • Relationships search. On items with many relationships, the search box opens by default and matches linked items’ names, human IDs, and legacy IDs.
  • Semantic search (beta). Suggestions load faster on projects with many branches and use the current branch’s edited text. Indexing no longer stalls on projects with many branches, so recent edits become searchable.
  • Filtering with ancestors shown. Searches in views with shared hierarchies respond faster and keep every matching path visible.

Table

  • Select all. The header checkbox selects every item matching the current view and filters, including items inside collapsed folders. The Edit field menu states how many items a bulk edit will change.
  • Bulk edit after select all. Edits apply to everything the filter matches when you apply them, and unticked rows are left alone. Large selections apply in the background with a running count. Use the branch history to revert these edits.

Tree

  • Moving children up. Deleting items can move their children to the project root and to surviving parents together. Moving an item to the project root keeps its other parent relationships.

Views

  • Details panel fields. Configure Fields Visibility… now lives in the details panel’s Options menu. Name and Description always show, and Show more reveals hidden fields without changing your field selection.

API Changes

  • Merge readiness. Call GET /project/{projectId}/branch/{id}/merge-readiness to see whether a branch is ready to merge, with every blocking review, check, stage gate, editor group, and conflict listed. See the API reference.
  • Saved views over the API and MCP. Admins can list, create, edit, and delete one shared saved view at a time through the Customer API and the MCP server. Add or remove a single nesting rule without resending the view’s other rules.