Skip to main content
Once you open a project in BlueGenAI you enter the project workspace. The workspace has four tabs — CAB, Tickets, Prototype, and Build — each serving a distinct purpose in your project lifecycle. This page walks you through every element so you can move confidently between them.

​
The four tabs

Every project workspace has four tabs across the top. Click any tab to switch to that workspace.

​
The CAB tab

CAB — Common Application Blueprint — is where you upload an existing system’s artifacts and generate a comprehensive architectural blueprint. It is the starting point for legacy system modernization.
The CAB tab showing the upload area on the left and blueprint preview on the right
Left panel — CAB Configuration:
  • Upload area — drag and drop files or click Upload file
  • Supports PDF, documents, images, and source code files (as a ZIP)
Right panel — Common Application Blueprint Preview:
  • Displays the generated blueprint once analysis is complete
  • Shows “No Blueprint Yet” until files are uploaded and Generate Blueprint is clicked
Generate Blueprint button — starts the CAB analysis pipeline once files are uploaded. For full guidance on using CAB see Phase 2 Path B — Modernize a Legacy System.

​
The Tickets tab

The Tickets tab is a project management workspace where tickets generated from your requirements are tracked and managed. The Tickets tab showing the ticket list with Status, Priority, Source, and Work Type filters Left panel — Views:
  • All Tickets view with a count badge
Right panel — Ticket list:
  • Search tickets field
  • Four filter dropdowns: Status, Priority, Source, Work Type
  • Ticket list area — shows “No tickets found” until tickets are generated
Tickets is currently in Beta. Tickets are generated from approved requirements and represent individual units of work — some assigned to AI, some requiring human action. Full documentation for this tab is coming soon.

​
The Prototype tab

The Prototype tab is where you design your application. You interact with the Web Application Prototype Design Agent through prompts to generate interactive prototypes, design systems, and visual assets.
The Prototype tab showing the Requirement Folders panel on the left and chat workspace on the right

​
Requirement Folders panel (left)

Requirement Folders organize your design work by feature area, screen, or workflow step.
  • Click + to add a new folder
  • Use the Search field to find folders by name
  • Click any folder to work within it
  • Each folder shows a count of items inside

​
Chat workspace (right)

  • Welcome message — the Prototype Design Agent introduces itself and its capabilities when you first open the tab
  • Chat history — prompts and responses appear here as you work
  • Type your message — the prompt input field at the bottom

​
Chat input toolbar

You can attach virtually anything to a prompt in the chat — PDFs, Word documents, PowerPoint files, source code, ZIP archives, images, screenshots, CSVs, and plain text files. If you can attach it to an email, you can attach it here.

​
The Build tab

The Build tab is where you generate and deploy your full-stack application. It uses the same chat interface as the Prototype tab but without the Requirement Folders panel — the full workspace is dedicated to the build conversation. The Build tab showing the full-width chat workspace with the message input at the bottom
  • No left panel — the entire workspace is the chat area
  • The same chat input toolbar as Prototype: attachment, model selector, settings, send
  • Build conversations are separate from Prototype conversations — attach your design files in your first Build prompt
The Build tab starts a fresh conversation. The agent does not automatically see your Prototype chat history. Attach your relevant design files and include key context in your first Build prompt.

​
The toolbar

The toolbar runs across the top right of the workspace and is available in both Prototype and Build tabs. It gives you access to project tools without leaving your current conversation.

​
Application URLs panel

Clicking the URLs icon opens the Application URLs panel. This is where your deployed application endpoints appear after a successful build. 1 8 Application Urls Png
Application URLs populate automatically when your build completes. If you see “No Application URLs Found” it means no build has been deployed in this project yet.

​
The header

The header appears at the top of every page in the platform.