Weekly release notes

​

Week of August 21, 2026

​

New features

• Tickets and Epics. Every project now carries a Tickets list where each item captures status, priority, work type, expertise (Agent, Human, or both), estimated effort, an assignee, and a link back to the CAB element it came from. Group Tickets into Epics to set the build order; an Epic’s position is its Wave, so reordering Epics renumbers Waves automatically. Filter and sort state lives in the URL so a view can be shared as a link. See What are Tickets and Epics.
• Generate Tickets from a CAB. Convert a blueprint into a working set of Tickets in one step, with each Ticket keeping a CAB Reference back to its source element. See CAB-to-Ticket conversion.
• Reference a Ticket in Build Mode. Mention a Ticket in a build conversation to hand its full description and acceptance criteria to the build agent as context. See Using Tickets in Build Mode.
• Web Apps: Prototype Mode. Build a working front end with mock data, no backend, and no infrastructure to stand up. Iterate on layout, colour, typography, and copy in seconds, then hand the output into Build. See Prototype Mode overview and Output handoff.
• Web Apps: Build Mode. Generate a full application (front end, backend, database) through a conversation with the build agent, with a per-message quality selector for Medium or High. See Build Mode overview and the Workflow.
• Ask sub-mode for read-only questions. Inside Build Mode’s composer, switch to Ask to query your codebase without any risk of changes. The agent is given read-only tools only, cites answers with path/file.ext:line, and can produce a plan for a change before you switch back to Build to apply it. See Ask Mode.
• App testing agent. With App testing enabled in agent settings, a separate testing agent runs browser-based scenarios against your built application after each build and reports pass or fail scenarios in the chat. Provide test logins and app notes in Testing Context. See App testing and Testing Context.
• MCP integrations. Connect a remote MCP server to extend what the build agent can reach, with Streamable HTTP or SSE transports, optional custom headers, and per-project Shared or Individual credential sharing. URLs are validated to block private and internal addresses. See MCP Integrations.
• Credentials panel. Third-party keys are requested by the agent as it needs them and stored in a project credentials panel; internal secrets (database password, session keys) are generated for you. Values are masked before the agent reads them, so the agent references credentials by name only. See Credentials.
• Git integration for generated projects. Checkout, Pull, and Push controls in the Codebase panel footer let you sync a generated project with its repository, with a commit message prompt when there are uncommitted local changes. See Git Integration.
• Custom domains for Web projects. New Web projects on the gateway architecture can be given a custom subdomain of apps.bluegenai.ai in place of the generated address. See Deployment guide.
• Codebase and Database viewers. Browse the generated source in a tree with a file viewer, and inspect the application’s database either by browsing tables row-by-row or by running SQL against it. See Codebase and Database view.

​

Updates

• Tips and tricks section. A new guides area covers prompting best practices, common workflows by role, a BD / pre-sales usage guide, and a troubleshooting FAQ.
• Files panel across modes. A shared Files panel now lists everything uploaded to or generated by a project, available from the panel rail in both Prototype and Build. See Files.

​

Week of August 18, 2026

​

New features

• Clone a project from the dashboard. The project card menu now has a Clone Project option that copies a project into a new one, letting you rename the title, description, and client name as you copy. Web projects bring the blueprint, requirements, uploaded files, source code, design system, credentials, and MCP connections; low-code projects bring the blueprint only. Tickets, Epics, conversation history, and collaborators are never copied. Failed clones retry up to three times. See Cloning your project.
• Edit CAB with review-before-save. A generated blueprint can now be edited in two ways: change values inline yourself, or ask the CAB agent to make changes for you. Both routes end at a review screen where you accept or discard each change before anything is written. See Editing your CAB.
• Version history for blueprints. Every save creates a version you can open, compare, and restore. A badge on the toolbar shows how many versions exist. See Editing your CAB.
• Share a blueprint outside the platform. The new Share CAB control gives you a link that opens the whole blueprint for anyone, with no BlueGenAI account required. Use it for stakeholder review. See Editing your CAB.
• Download blueprints as Markdown or PDF. Two new toolbar buttons export the current blueprint as a .md file or a PDF. See Editing your CAB.

​

Updates

• Choose Model Quality before generating a CAB. CAB Configuration now offers Low, Medium, and High for the whole run, trading speed and cost against output quality. The footer reports final cost and elapsed time once the run completes. See Step-by-step workflow.
• Pause, resume, and stop a CAB run. While generation is in progress you can pause and resume at will, or stop with a confirmation. Each of the seven generation phases now reports its own status so you can see which one is active. See Step-by-step workflow.
• Pick which sections to generate. The Sections to Generate checklist lets you deselect any of the 10 blueprint sections before a run, which also narrows what earlier phases look for in your source material. See Step-by-step workflow.
• Integrations page added. A new Integrations page lays out the services the platform runs on (identity, source control, search, application hosting), the credentials each low-code platform needs, and where to connect external tools via MCP.
• Project collaborators now carry a billing preference. When you invite an Editor, you choose whether their agent runs draw from the project owner’s credits or from the collaborator’s own balance. Select Owner to charge activity to the project owner, or Collaborator to charge the invitee’s account. See User & role management.
• Clearer three-level project permissions. The Owner, Editor, and Viewer roles are now spelled out end to end, including what each can do, how invitations are accepted, rejected, or withdrawn, and how Viewers can still ask read-only questions of the agent on projects they cannot build. See User & role management.
• Two distinct ways to share a project. Shareable Link Access lets any signed-in platform user request access to a whole project (still requires approval). Read-only share links let anyone open a generated CAB without an account. See Collaboration features.

​

Week of August 11, 2026

​

New features

Low-code platform support: TAP, ServiceNow, PowerApps, and Salesforce. You can now build projects that produce configuration in a platform you already own, instead of a hosted codebase. Select Low Code Application as the Project Type when creating a project to choose between Tyler Application Platform, ServiceNow, PowerApps, or Salesforce. See the Low Code overview for the platform comparison and where direct configuration stops.

• Tyler Application Platform. Connect a TAP environment and configure data model, security, forms, workflows, and user management within the operations the platform exposes. Full component inventory in the TAP component reference.
• ServiceNow. Connect a ServiceNow instance and configure across seven areas including tables, forms, business rules, workflows, and portals. Cross-area requests are supported. See the ServiceNow component reference.
• PowerApps. Connect a Dataverse environment and configure model-driven apps, tables, columns, views, and relationships. Security roles, Power Automate flows, and form JavaScript are specified rather than applied; the overview page shows exactly what the agent applies versus what it specifies. Full inventory in the PowerApps component reference.
• Salesforce. Connect an org and configure the widest surface of the four: objects and fields, profiles and sharing rules, page layouts, Lightning apps and pages, Lightning Web Components, flows and Apex, and reports. Everything is applied to the org rather than specified, and existing Aura components and Visualforce pages can be migrated to Lightning Web Components. Full inventory in the Salesforce component reference.

​

Updates

• Low Code overview rewritten. The overview page now includes a full-code vs low-code comparison, a per-platform capability table, and explicit notes on where direct configuration stops for each platform.