Widgets

Maya's homepage hero can start in the agent. She names the team, the project, and Development, and the draft shows up in the same Widgets list as Add Widget. Widget Access is the same grant as the dashboard. Publish to Staging is still the button on the widget — the agent's publish call is refused, because it never sends which widget.

What you can do

Maya's homepage hero does not exist yet, and she is already in the agent. She can create the draft in Development, name it, change the layout, and read the CSS settings the composer would show. It is the same widget list as Add Widget.

The page is the better door for some jobs. The agent is better for others.

Use the agent when you are already in the chat and you want the draft, a rename, a CSS setting, or a publish without opening the environment.
Use the Widgets page when you want the orange card, the composer canvas, or the confirm step on Publish to Staging.

The same list, the same permission

The agent does not get a side door. It acts as the RuleCMS account that signed in when you connected MCP.

You need a Widget Access group — View, Manage, or Admin — for that environment. View can open the list and the CSS settings. Manage can create the draft, save the layout, and save a CSS setting. Admin is what can delete. The dashboard still has no delete button. The agent does.

Rename is stricter than a single environment. It changes the name on every copy of that widget, so you need Manage on Development, Staging, and Production, not only the environment you are looking at.

Create the homepage hero

She wants the campaign draft in Development, not on top of the Production Default Widget. The name has to be new for the whole team. Two projects cannot share it.

Connect RuleCMS in the agent, if you have not. The steps are on MCP.
Tell the agent the team, the project, and Development. The name can be the homepage hero. Leave the name off and RuleCMS assigns one. The version starts at 1.0.0.
Open the environment, the orange Widgets card, View Widgets. The draft is there. Nothing is published. A Staging token still has no snapshot.

Change the draft

The layout is the composer's rows. Saving it from the agent is the same write as the composer. A rename is the name on the list, and it follows the widget into Staging and Production when those copies exist.

CSS settings are the same cards as the widget's CSS page: CSS Variables, Class Definitions, Fonts, Keyframes, Themes, CSS Properties, Widget chrome, Cascade layers, and Position try. Each one can be read, and each one can be saved, including whether that setting is included when a published widget is rendered.

Saving the whole CSS catalog replaces every setting. An empty list clears the color variable you just set on CSS Variables. Save the one setting you mean to change.

A Tailwind pass can look first and write second. Looking counts the classes in this layout and does not save. Writing saves that catalog. An empty layout finds nothing. Sync from the project copies the project's CSS catalog onto this widget. If the project has no catalog yet, the sync says so and changes nothing.

Publish the homepage hero

Development has no publish button. The tab is Integrate. Staging and Production have Publish. The walkthrough for the buttons is on Publishing.

The agent can do the same moves. Name the widget. Promote to Staging copies the Development draft into Staging. It does not publish. Also say whether to update shared collections. No keeps shared collections that already exist in the destination. Yes refreshes them. Embedded collections always come along, and a missing shared collection is created either way. Publish to Staging writes the snapshot a Staging token can fetch. Production is the same pair, from Staging. Make a copy stays in this environment. Copy to another environment needs that environment named as well. A tag name and a short description are optional labels on the snapshot.

If the project requires approval, a direct publish is refused and the agent submits instead. The signed-in person still needs Post Publish To Staging or Post Publish To Production to submit, and to publish once the request is approved. Approving is a separate step, and only a person on that environment's approver list can do it — with their own sign-in, not with Maya's. The dashboard guide is Approvals.

Post Publish To Staging and Post Promote To Staging are the groups under Utility Functions, the same as the page. A dependency lookup names the widget, or the published key once a snapshot exists.

You can still ask whether Staging has a snapshot. Before the first publish the answer is no, and history is an empty list. After you publish, history is the page on History, compare, and restore. Usage numbers are a Production snapshot. Until that exists, the agent says the published widget was not found.

The edit link for a published widget is the environment id, three hyphens, then the widget key. Until you publish, that link is not found. A key with no environment id in front is rejected before the lookup.

Names you may see

You do not have to type these. They are the labels in the agent's tool list, if you open it. Each one still checks Widget Access.

What you asked for	The tool
Create the draft	`post_t_teamId_p_projectId_e_environmentId_widgets`
List widgets, including by name	`get_t_teamId_p_projectId_e_environmentId_widgets`
Open one widget	`get_t_teamId_p_projectId_e_environmentId_widgets_widgetId`
Save the layout	`put_t_teamId_p_projectId_e_environmentId_widgets_widgetId`
Rename it everywhere	`post_t_teamId_p_projectId_e_environmentId_widgets_rename`
Read or save CSS Variables	`get_t_teamId_p_projectId_e_environmentId_widgets_widgetId_css_variables` / `put_t_teamId_p_projectId_e_environmentId_widgets_widgetId_css_variables`
Publish to Staging	`post_t_teamId_p_projectId_e_environmentId_widgets_publish_to_staging`
Promote to Staging	`post_t_teamId_p_projectId_e_environmentId_widgets_promote_to_staging`
Delete a draft	`delete_t_teamId_p_projectId_e_environmentId_widgets_widgetId`

Class Definitions, Fonts, Keyframes, Themes, CSS Properties, Widget chrome, Cascade layers, and Position try follow the same pattern: a read and a save, one tool each. The dashboard names them View and Edit on the CSS cards.

When it does not land

What you see	What it usually means
The agent says you cannot open or create it	This account does not have Widget Access on that environment, or it is not on the team. View is enough to look. Manage is required to create or save.
The name is already taken	Some widget on this team already has that name, in any project or environment. Pick another name.
Promote or publish did nothing	The call left without the widget, or this account is missing Post Publish To Staging or Post Promote To Staging. Name the widget, say whether to update shared collections, and open the environment you are moving into.
Delete was refused	You have Manage but not Admin, or an active ruleset still names this widget. The widget stays. Admin under Widget Access is the group that can delete.
The color variable disappeared	A later save replaced the whole CSS catalog, often with an empty list. Set the variable again on CSS Variables. Do not save the catalog unless you mean every setting.