Greenfield
Goal: Let Azi build at full speed while you are shaping something new.
Azi works in one of two modes, shown on the button at the foot of her panel:
| Mode | What happens to Azi's proposals |
|---|---|
| Proposal Mode | They wait in Proposals until a person accepts them. The default |
| Greenfield Mode | They are accepted for you as soon as she makes them |
Turn it on
- Click the mode button at the foot of Azi's panel.
- Pick Greenfield Mode.
- Confirm Enter Greenfield Mode (tick Don't show this again to skip this step next time).
Going back to Proposal Mode takes effect at once, with no confirmation.
Each browser tab keeps its own mode. Changing it in one tab does not change another tab you have open on the same workspace, and every Azi panel in a tab sends the mode that tab shows. A new tab, or a reload, starts from your last choice for that workspace in this browser.
What it does
When Azi makes a proposal in Greenfield Mode, it is accepted through the same accept you would press, as you and with your rights, once the workspace confirms the proposal was saved. Only the proposals Azi made in that turn are accepted - never anyone else's.
Each change is saved to the workspace for everyone on it right away. Nothing reaches the cloud until you Deploy. You can change or remove anything before then.
An accept can be undone until the next Deploy, unless the undo is refused. Open Deploy in the top bar (save or revert your edits first): the Deploy window lists every accept since the last Deploy under Accepted since the last Deploy, the ones Greenfield made for you included, each with Undo, and Redo once it is undone. A Deploy that finishes clears the list. A job identity is not on it: it is accepted in the App Identity window, which writes no undo. When you undo a change, the Azi conversation in that tab is told, and she does not propose it again unless you ask. The refusals, and what each undo does, are in Undo an accept until Deploy.
So, as with any accept:
- Warm queries, surfaces and access records are live as soon as they are accepted.
- Data connections, API sources, simulators, hosted workbenches and licences are built only when someone presses Deploy. Greenfield never deploys.
- Code in a warm query is accepted like any other change.
- A cloud connection or a landing zone is only recorded on accept; Azi names the window where you connect it (Cloud Connections) or create it (Manage Private CALZ).
Azi tells you the change was applied to the workspace, and names the kinds in it that still need Deploy to be built.
What still waits for a person
Some proposals are not accepted for you, even in Greenfield Mode. They stay in Proposals, and Azi tells you the change was not applied:
| Change | Why it waits |
|---|---|
| Removing something | A removal needs a person to confirm it |
| A job identity | It is accepted only in the App Identity window |
| Turning off a data store's delete protection | A person confirms it and signs in again |
| Setting up your directory for app calls | A person signs in again to approve it |
| A change that needs a right you don't hold | Your rights apply, and it is refused as your own accept would be |
A refusal for a missing right also stops Greenfield from accepting the rest of Azi's proposals from that turn; they wait in Proposals too.
Azi in other windows
The Databases window has no Azi panel; ask the main Azi panel for database changes. The Azi in the Warm Query Manager never proposes: she drafts the query into the window, and you save it with the canvas Save icon, in either mode.
Agents you bring over MCP
Greenfield changes only Azi. An agent connected over MCP - Claude, Cursor, ChatGPT or any other - only ever proposes: there is no accept tool over MCP, and Greenfield never accepts a proposal it did not see Azi make. See You stay in the loop.
Turning Greenfield off for a workspace
A workspace can turn Greenfield off for everyone; when it is off, nobody sees the toggle and every Azi change waits for a person to accept it.
Where to set it
Open Workspace -> Settings and use the switch Let Azi apply its own changes (Greenfield) in the
Greenfield section. Only the workspace owner or someone with Workspace.Access.Manage can change it;
everyone else sees it disabled, with the reason: "Only the workspace owner or someone with the
'Workspace.Access.Manage' right can change this setting." A proposal can never change it
(GREENFIELD_SETTING_NOT_PROPOSABLE), and a member without the right is refused
(GREENFIELD_SETTING_CHANGE_NOT_ALLOWED).
The window answers "Greenfield is off for this workspace. Open workspace tabs show the change after a reload." (or "on"). Turning it off stops Azi applying its own changes at once, even in tabs that are already open. After turning it on, people reload to see the toggle; a reloaded tab starts from the last mode chosen for that workspace in that browser, which may be Greenfield. The section is also described in Workspace Settings.
Next steps
- What Save, accept and Deploy each do -> Save, accept and Deploy
- Who can accept what -> Team Review & Access Rights
- Ask Azi well -> Working with Azi