Release Notes

MCP and AI integrations

• CR-241 — MCP resources, prompts, and transport rules: refined the contracts for the MCP Server, MCP tokens, and tool trace files; added or updated MCP resource modules and resources for units, artifacts, Change Requests, and app manifests; formalized MCP Resource Templates, MCP Prompts, transport rules, and the retrieval of MCP connection parameters for subsystems
• CR-242 — MCP attribute removal: removed the specified attributes from MCP resource modules and individual MCP resource module definitions, narrowing and clarifying the public MCP contract
• CR-229 — Findings in get-artifact: extended the MCP artifact retrieval operation to include Findings and their related context, allowing AI tools to access both an artifact and its verification results
• CR-228 — Partial updates to AI code prompts: added support for partial changes to subsystem.code_ai_prompt and unittype.ai_code_prompt, including AI Subsystem Architect workflows for saving draft items and applying results
• CR-225 — Consistent purpose text for tool calls: standardized first-person purpose messages across AI Analyst, AI Subsystem Architect, and AI Expert tools to align progress messages with prompt templates

AI tasks, chat, and AI credits

• CR-236 — Instance-level AI credit accounting: extended AI credit charging to task starts, continuations, reruns, and automatic or manual AI checks; aligned AI Task, AI Task Message, instance settings, AI Model Presets, credit transactions, pricing plans, queues, canonical transcripts, and the AI Task Browser UI
• CR-237 and CR-238 — Consistent AI credit billing: resolved conflicts in charging, refunds, and billing error handling; standardized the use of AI credit transactions and billing error records across task lifecycle, archiving, reruns, and AI Task display
• CR-232 and CR-235 — Separate AI Task result application state: separated result application from the main task status with a dedicated application flag, preserving the original execution status while showing whether the result has been applied
• CR-239 — Route-based AI Task Draft opening: AI Task drafts now open through a route when an AI Assistant type is selected, improving quick task creation and navigation between assistants
• CR-234 — Updated AI Assistant names: renamed AI Assistant navigation items and consolidated separate New Task actions into a single navigation item
• CR-226 — Follow-up with Cmd/Ctrl+Enter: added a keyboard shortcut for sending follow-up messages in AI Task chat
• CR-224 — Progress, web search, and tool calls: unified the display of progress messages, web searches, tool calls, and tool results around a shared tool-call, tool-result, and progress model

Requirements Browser, folders, and Issues

• CR-245 — Required subsystem selection for new Requirements: creating a Requirement now requires at least one subsystem on both the frontend and backend; the rule applies only during creation and does not prevent removing the last subsystem from existing Requirements
• CR-244 — Save folders with Enter: standardized Enter-key submission for creating and editing module, Data Entity, User Interface, API Operation, and Unit folders
• CR-243 — Unified module context menu: aligned module actions across table and detail views in the Requirements Browser, including Requirement creation, module moves, Markdown exports, and deletion
• CR-227 — Configurable active Issue column: added an optional Requirements Browser column showing the active Issue, its status, and its relationship to the Requirement
• CR-222 — Requirements column in the Issues Browser: added an optional column showing linked Requirements in both active and archived Issue views, including metadata and list API support
• CR-221 — Issue details in Change Request parameters: Change Request details now show the selected Issue when an Issue is linked, with corresponding updates to the detail API and Issue relationship operation

Settings and navigation

• CR-240 — Feature toggle visibility in experimental mode: feature toggle visibility now depends on whether experimental mode is enabled in general instance settings and project settings, including Project General Settings retrieval

Findings and quality assurance

• CR-230 — Project-aware Finding numbering: public Finding numbers are now scoped to projects, preventing ambiguous keys and providing the correct Finding context to AI verifiers
• CR-233 — Finding severity group order: Active Findings Browser and table views now show severity groups from highest to lowest priority, starting with High
• CR-231 — Changing the type of locked Units: improved individual and bulk type changes for locked Software Units, including correct restoration of the Unit status and related Revision when an operation fails
• CR-223 — Results in the QA Dashboard: added a Results section where users can switch Test Environments and review test run results for the selected environment across Requirements, Test Cases, Test Runs, execution results, and environment states

• Updated navigation logic between sections
• Implemented a new AI Analyst that works with all specification types simultaneously
• Revised the Questions Mode workflow and context preparation when switching to execution mode
• Improved AI agent logic for searching across specifications and the codebase
• Added a tabular view for spec–code alignment
• Introduced configurable rules for automating specification and code processing, including warning generation
• Minor UI improvements

• Major update, product renamed to Reqode
• Ability to use AI Assistants from Issues
• Unit Architect AI Assistant added

• AI: Business Requirements writer assistant reworked
• AI: Code writer assistant reworked
• AI: Features (software requirements) writer assistant reworked
• AI: Assistant is able to require artifacts automatically (can be switched on/off)
• AI: Assistant question mode: writes a plan and asks questions before starting a task (can be switched on/off)
• AI: Ability to add context while working with the assistant
• Business Requirements: Bugs fixed, new way to create and view relations
• Issues: Issues sidebar navigation uses requirements tree
• Change Requests: Multiple applications per change request allowed
• Change Requests: Change Request can be linked with artifact revisions
• QA: Test coverage widget now shows coverage by software requirements structure (module folders)
• User Interfaces: Beta implementation of wireframing tool integration in User Interfaces
• Minor UI improvements
• Code: Gitlab integration bugs fixed.
• Issues: Yandex Tracker priority fix

• Quick Verification
• Test Case editor improvements
• Requirement statement as an artifact
• UI minor improvements
• Commit impact on test case runs
• Test case runs suspicious state UI added
• Issue - Requirements relation reworked
• Personal workspace (issues, test cases) bug fixes

• Show artifact revision name when revision is opened (istean of actual name)
• Requirements tracing table open issues assignee fix
• Wysiwyg editor draft cancel (reset) button added
• Wysiwyg editor draft auto recover
• Commit Actions and commits UI improvements
• Issue set reworked (ordering added, improved behavior)
• Re-sync commits button in code → commits section
• Multiple issues related to requirement branches fixed
• Closed baseline functionality improved
• Baseline closed improved
• Package icon removed
• Code highlighting for php/c/js styled source code
• Issues: open context inline (requirement and data entity so far)
• Issues: external sync improvements (bulk action button)
• AI Tasks: Context tab added
• UI minor fixes