Sign In

Use Agent Canvas with Agent Composer

Canvas and Composer integrate through capability discovery while keeping presentation and workflow policy separate.

  • Canvas owns templates, template parts, patterns, styles, semantic tokens, and final rendering.
  • Composer owns Config Sets, Site Contracts, Blueprints, validation, audit, portability, and draft-only execution.

Canvas ships a static, read-only presentation manifest. Composer may inspect it as discovery input, but the theme does not create, update, or activate Composer configuration.

Initial setup​

  1. Install and activate Canvas.
  2. Open SmartCloud → Agent Composer → Theme & providers.
  3. Choose Rescan site and confirm the Canvas name, version, templates, patterns, and core blocks.
  4. Create an inactive Config Set from a suitable preset, Detected Theme Starter, or a manual configuration.
  5. Review Configuration & blueprints and verify every target template, allowed pattern, nested block, required sequence, excerpt policy, and constraint.
  6. Apply staged changes, validate the complete Config Set, and activate it explicitly.
  7. In a compatible client, load the design context, Blueprint, and approved patterns; validate one minimal plan; create one agent-owned draft; and inspect its preview.

After a Canvas update​

A site scan discovers current capabilities; it does not regenerate or rewrite the active Config Set. After upgrading Canvas:

  1. rescan the site;
  2. keep the active set immutable;
  3. clone it when a template, pattern, block, or manifest change requires an update;
  4. adjust the working copy;
  5. validate representative page types and previews;
  6. activate the successor only after review.

Troubleshooting​

  • Blueprint validation reports a missing pattern or block: rescan, confirm that the capability is registered, then correct a cloned working Config Set.
  • A theme change caused a duplicate H1: pair a content-owned H1 pattern with a no-title template, or let the template render the title and remove the content H1 requirement.
  • The agent receives an old Blueprint: confirm the active Config Set, restart the MCP runtime if needed, then refresh or recreate the client app's scanned actions and start a new conversation.
  • Validation reports Custom HTML blocks cannot be enabled by a Blueprint: clone or replace the Config Set and remove core/html, custom_html: true, JavaScript-in-HTML allowances, and related stale extension settings. Rescanning alone does not change the Config Set.
  • The client returns INVALID_ARGUMENT after a new contract is activated: refresh the client action schema and send the exact content_language returned by the Blueprint with validation and draft operations.

Do not fix a discovery mismatch by editing Canvas theme files to store site-specific Blueprint policy. Correct the Composer Config Set unless the required presentation capability is genuinely missing from the theme.