[roger-datocms]

(Claude here [Opus 5.5])

Closes #173. Closes #162.

Setup: a checklist that blocks chatting until it's done

With DatoCMS connected but no AI provider key, New chat looked enabled but did nothing (#173). The setup panel is now an Agent setup checklist:

• Two numbered steps, each marked Done or To do with an icon and a word, not color alone:
  1. Choose AI provider & model. It doesn't name the provider, since editors don't need to know which one an admin picked. Users who can edit the schema get Open plugin settings, with the environment prefix in sandboxes. Everyone else is told to ask a developer or project admin.
  2. Connect AI to DatoCMS MCP. A short intro, a regular Connect button, and what each access choice on the DatoCMS consent screen lets the agent do.
• No chat until setup is done: Chats shows the kit's disabled text box with a FieldError, "Finish setup first to start chatting.", and no New chat button or chat list.
• Sign-in errors say what to do: "The DatoCMS sign-in was cancelled or denied. Click Connect to try again." The extra "Start sign-in again with a new registration" button is gone. Connect already registers a new client when DatoCMS rejects the stored one (invalid_client), and no other failure needs one.

Once set up: chats panel, toolbar, and the "⋮" menu

• The chats panel is just the chat history. Setup details no longer appear there, so nobody changes the connection by accident.
• Auto-approve toggle: off shows a slashed bolt and "Auto-approve is off". On reads "Auto: On" with a "Danger" badge.
• A "⋮" menu in the toolbar:
  • AI settings. Disabled with a reason for users who can't edit the schema.
  • Current DatoCMS access level, with one line on what it allows ("The agent can edit content, but not the schema.").
  • Reconnect to change access… asks in a small dialog, then signs in again straight to the consent screen and revokes the previous token afterwards.
    • Each Connect registers its own OAuth client, and the consent screen stores the access level for that client only. So reconnecting is how an editor changes it, and it touches no other client's grant.
    • The dialog is inside the plugin frame on purpose. A browser lets the frame open the sign-in popup only shortly after a click in that frame, and a click on a host dialog happens in the parent page.
• The agent's own guidance (MCP_ACCESS_CHANGE_GUIDANCE, used in the system prompt) used to tell editors to revoke access in their account settings, which affects every MCP client of the account. It now points to Reconnect.
• No access flash on load: "DatoCMS access is not verified" no longer flashes above the composer while the first access check runs.

Agent tab width (#162)

• The chat starts at 300px, then at whatever width the editor last dragged it to. That width is saved in the plugin's localStorage, once per browser, so it applies in every project.

  • It isn't keyed by user ID, because a collaborator's ID differs in each project.
  • It saves on every resize. Telling a drag from a window resize by outerWidth failed in Firefox, which reports the iframe's own size there.
  • The plugin SDK has no per-user storage on the server.

• Below 300px, a notice covers the chat: "Sidebar too narrow. Drag its edge wider to see the Dato Agent." The chat stays mounted underneath, so a reply in progress survives.

• From Dato Agent: give the inspector chat a usable starting width #165, with Rodrigo as co-author:

  • the empty record pane says "Ask the agent to open a record and it appears in this pane. Drag the divider to resize it."
  • the conversation stays centred at 760px max

  Dato Agent: give the inspector chat a usable starting width #165's starting-width calculation is replaced by the remembered width.

• Back from an opened record no longer spins forever. The record editor's back arrow switches to the inspector's record list, and the CMS shows an empty list as an endless spinner. The plugin now fills that list before every record it opens. A CMS-side fix (back to the previous view, a real empty state) is in progress separately.

Fixes for master

• package-lock.json is resynced (@emnapi/wasi-threads), so npm ci works again.
• The model-limit parsing moved out of extractAnthropicModel, so npm run lint passes again.

Known limits

• The chat still marks a record "Current record" after the editor closes it. The inspector ctx doesn't tell plugins when its mode changes, so this needs a CMS and SDK change.
• The OpenAI error messages are covered by unit tests only.

Testing

• npm test: 983 pass. npm run lint and npm run build exit 0.
• Checked by hand in a test project, master against this branch:
  • setup with no key, before and after connecting
  • the "⋮" menu and the reconnect dialog
  • the starting width at 1440px and 820px windows
  • the remembered width after a drag in Firefox
  • Back from an opened record landing on the list

🤖 Generated with Claude Code