Design Mode and AIRA Agent Mode

Think of AIRA as another contributor. AIRA does not directly overwrite your manual design work.

WaveMaker uses a git worktrees–based approach to keep manual design changes and AIRA-generated changes isolated until you explicitly decide to merge them.

Separate Workspaces: Design vs AIRA

When you switch between:

• Manual Design mode
• AIRA AI (prompt-based) mode

WaveMaker maintains one workspace for design-time changes and another workspace for AIRA-generated changes. These changes are tracked independently and do not override each other automatically. They exist side by side until you take action.

Design Mode vs AIRA Agent Mode

You can build applications manually, use AI assistance, or switch between both at any time. WaveMaker Studio has a mode toggle that lets you switch between:

• Design Mode (Manual)
• AIRA Mode (Agent-Assisted)

Aspect	Design Mode (Manual)	AIRA Mode (Agent-Assisted)
Primary interaction	Direct manipulation of Studio canvas and properties	Natural-language prompts interpreted by AIRA
UI creation	Manually add pages, layouts, and components	UI generated or modified by UI / Prism UI agents
Logic handling	Developer writes JavaScript and backend logic	JavaScript / Java / API agents generate scoped logic
API integration	Manual API import, binding, and configuration	API Agent + API Binding Agent handle integration
Validation & rules	Manually implemented by developer	Generated by relevant agents based on intent
Workflow control	Fully manual, step-by-step	Orchestrated by WaveMaker Agent
Change execution	Immediate and direct	Isolated until explicitly accepted
Change storage	Design workspace	Separate AIRA workspace (git worktrees)
Override behavior	Direct edits to files	No automatic overrides; apply only on acceptance
Conflict handling	Manual resolution by developer	Explicit merge conflict UI when overlaps occur
Scope of changes	Exactly what the developer edits	Only what involved agents are authorized to change
Suitable use cases	Fine-grained UI tuning, custom logic, debugging	Multi-domain tasks, rapid feature creation, wiring
Developer responsibility	Full implementation and wiring	Review, accept, and refine agent-generated output

When Do AIRA Changes Affect the App

AIRA changes affect your design only after you explicitly accept them; until then, all AIRA-generated updates stay isolated from your design. Clicking Apply All merges the accepted changes into the design workspace. Before that, your manual work stays safe, the application state does not change, and the system does not auto-apply or silently override anything.

Scope of Changes (Page vs App)

You receive a list of proposed changes before anything is applied. Read this list to see exactly which parts of the application will be affected. When you accept and apply the changes, they take effect only in those specific areas, not across the entire app. Your manual work outside the accepted scope remains untouched.

AIRA does not blindly override the whole application. What gets applied depends on three things:

• the prompt you gave,
• the agents involved,
• the specific changes you accepted

For example, a UI-only prompt affects only the relevant pages or components, a backend prompt affects only the APIs, data, or models handled by that agent, and multi-agent prompts apply only the combined outputs you approved.

Can AIRA Break My App

If the same file is modified both in your manual design work and in the AIRA workspace, the system does not guess or auto-fix anything. Instead, it shows a merge conflict screen so you can clearly see where the changes clash.

You can keep your version, keep AIRA’s version, or merge the changes.

AIRA as a Contributor

The right way to think about AIRA is as another developer on your project. It proposes changes, but it never applies them on its own. You review every change, accept only what you want, and handle conflicts explicitly when they occur. You always stay in control of the final result.