Title: SmartCloud Agent Composer
Author: Smart Cloud Solutions Inc.
Published: <strong>2026.08.04.</strong>
Last modified: 2026.09.04.

---

Bővítmények keresése

![](https://ps.w.org/smartcloud-agent-composer/assets/banner-772x250.png?rev=3634275)

![](https://ps.w.org/smartcloud-agent-composer/assets/icon-256x256.png?rev=3636177)

# SmartCloud Agent Composer

 Szerző: [Smart Cloud Solutions Inc.](https://profiles.wordpress.org/smartcloud/)

[Letöltés](https://downloads.wordpress.org/plugin/smartcloud-agent-composer.1.2.0.zip)

 * [Részletek](https://hu.wordpress.org/plugins/smartcloud-agent-composer/#description)
 * [Vélemények](https://hu.wordpress.org/plugins/smartcloud-agent-composer/#reviews)
 *  [Telepítés](https://hu.wordpress.org/plugins/smartcloud-agent-composer/#installation)
 * [Fejlesztés](https://hu.wordpress.org/plugins/smartcloud-agent-composer/#developers)

 [Támogatás](https://wordpress.org/support/plugin/smartcloud-agent-composer/)

## Leírás

SmartCloud Agent Composer adds a controlled WordPress layer for agent-assisted Gutenberg
workflows. Administrators define versioned Config Sets with site contracts, page-
type Blueprints, approved patterns, structured fields, relations, media policy, 
and safety rules. Agents can create or revise only validated, Composer-owned drafts,
or prepare a separate working proposal for a human-reviewed published-content update.

Composer registers its governed Abilities through the separate WordPress MCP Adapter
at `/wp-json/mcp/smartcloud-agent-composer`. A compatible authenticated MCP client
can connect directly; an OpenAI Connector tunnel is optional and is not bundled.

Core operation runs inside WordPress without requiring a WP Suite account, subscription,
hosted service, provider plugin, or proprietary theme. Optional integrations are
disclosed under **External Services**.

**Key features**

 * Draft-only agent execution with separate WordPress authorship and Composer ownership.
 * Explicitly validated and activated Config Sets; imports and edits never activate
   automatically.
 * Optimistic concurrency for configuration and draft changes.
 * Gutenberg block-tree, pattern, template, post-type, language, excerpt, field,
   and relation validation.
 * Document and structured-record Blueprints, including registered REST-visible 
   fields approved by the Site Contract.
 * Human-readable, ordered relation editing constrained by allowed target types,
   statuses, and cardinality.
 * Existing-image assignment and optional bounded raster ingestion from approved
   HTTPS hosts.
 * Short-lived preview drafts with ownership-checked cleanup.
 * Redacted, tamper-evident audit events in an append-only SHA-256 hash chain.
 * Checksum-protected Config Set lifecycle and active-theme/provider discovery.
 * Provider-neutral language discovery that distinguishes authored-language policy
   from actual site language switching.
 * Optional Polylang and WPML draft-language assignment and explicit linking of 
   separately authored translations without publishing them.
 * Human review can return the same update proposal for changes with an audited 
   instruction, without creating another draft.

Documentation: https://wpsuite.io/docs/

This plugin is not affiliated with or endorsed by the WordPress Foundation. All 
trademarks are property of their respective owners.

### Usage Notice

Composer does not grant anonymous access or general WordPress administration. The
dedicated `smartcloud_agent` role has no publishing, normal-content deletion, plugin,
theme, user, arbitrary media-upload, or unfiltered-HTML capabilities.

Composer never publishes agent-created content. It deletes only expired, Composer-
owned temporary previews. Optional remote ingestion is restricted to allowlisted
HTTPS hosts and Composer-owned drafts; it is not a general Media Library API.

### External Services

Composer’s configuration, validation, audit, ownership, concurrency, pattern assembly,
local media lookup, and preview handling run inside WordPress. Optional features
can make the following requests. Composer never downloads executable PHP from a 
remote service.

 1.  **Provider-owned WordPress Abilities (optional)**
 2.   * Used only when an administrator enables a provider integration and an authenticated
        agent requests that provider’s operation.
      * Composer passes the validated component input and non-secret execution context
        to the provider Ability in the same WordPress request. The provider plugin 
        may then contact its configured service.
      * Review the provider plugin’s terms, privacy policy, endpoint, transmitted data,
        and retention before enabling it.
 3.  **Administrator-approved remote media sources (optional)**
 4.   * Used only when the active Site Contract enables remote ingestion, lists the
        exact HTTPS host, and an authenticated Composer agent with the dedicated capability
        requests one image.
      * Composer sends a normal HTTPS image request with its user-agent and standard
        network headers. It does not send draft content, WordPress credentials, cookies,
        or portable configuration secrets.
      * The bounded response is restricted to allowed raster MIME types, validated,
        fingerprinted, stored in the local Media Library, and assignable only to a 
        Composer-owned draft. HTTP, redirects, embedded credentials, custom ports, 
        and non-allowlisted hosts are rejected.
      * The administrator must verify the source’s reuse rights, terms, and privacy
        policy.
 5.  **WP Suite platform connection (optional)**
 6.   * Used only when an administrator connects the packaged shared Hub to a WP Suite
        workspace or enables shared account, entitlement, license, configuration, or
        subscription features.
      * Minimal site/workspace identifiers, plugin and capability metadata, and authentication/
        session data may be sent by HTTPS to `wpsuite.io` or `api.wpsuite.io`. Opening
        Composer alone does not send draft content.
      * Privacy: https://wpsuite.io/privacy-policy
      * Terms: https://wpsuite.io/terms-of-use
 7.  **Amazon Cognito (optional)**
 8.   * Used when an administrator signs in through the shared Hub or a Cognito-protected
        integration.
      * Authentication identifiers, session data, and authorization tokens required
        by the configured user pool may be sent. Composer excludes Cognito passwords
        from portable packages and audit events.
      * AWS Service Terms: https://aws.amazon.com/service-terms/
      * AWS Privacy: https://aws.amazon.com/privacy/
 9.  **Stripe (optional)**
 10.  * Used only when an administrator opens an optional WP Suite subscription or 
        purchase flow in the shared Hub.
      * Browser/session and payment-flow data required by Stripe may be sent. Stripe
        handles card data; Composer does not store it.
      * Terms: https://stripe.com/legal/consumer
      * Privacy: https://stripe.com/privacy

The documentation, GitHub, and npm links in this readme are informational and are
not contacted merely because the plugin is installed.

### Privacy

Composer stores Config Sets, private execution metadata, validation state, and redacted
audit events in WordPress. Audit events retain hashes and allowlisted/redacted context
rather than credentials or full page content. Secret-like keys are rejected from
imports and redacted from audit context.

Uninstall removes Composer configuration, options, scheduled cleanup, dedicated 
role and capabilities, audit table, and owned temporary previews from sites where
it stored data. Ordinary drafts remain WordPress content. Export configuration first
if it may be needed later.

### Source & Build

Human-readable source and reproducible build instructions:
 https://github.com/smartcloudsol/
agent-composer

Public TypeScript contracts:
 https://www.npmjs.com/package/@smart-cloud/agent-composer-
core

The distributed JavaScript and CSS are built from public `admin/src` and `core` 
sources. PHP owns registration, authorization, persistence, audit, portability, 
and execution. The release assembler adds the shared Hub runtime, verifies the package,
normalizes timestamps, and records SHA-256 checksums.

## Képernyőmentések

[⌊Composer status and execution-boundary overview⌉⌊Composer status and execution-
boundary overview⌉[

Composer status and execution-boundary overview

[⌊Config Set lifecycle with an explicit Active-to-Selected comparison⌉⌊Config Set
lifecycle with an explicit Active-to-Selected comparison⌉[

Config Set lifecycle with an explicit Active-to-Selected comparison

[⌊Archived configuration validation and restore confirmation⌉⌊Archived configuration
validation and restore confirmation⌉[

Archived configuration validation and restore confirmation

[⌊Guided page Blueprint editor with target, excerpt, field, relation, media, pattern,
block, and policy controls⌉⌊Guided page Blueprint editor with target, excerpt, field,
relation, media, pattern, block, and policy controls⌉[

Guided page Blueprint editor with target, excerpt, field, relation, media, pattern,
block, and policy controls

[⌊Theme and provider discovery and readiness view⌉⌊Theme and provider discovery 
and readiness view⌉[

Theme and provider discovery and readiness view

[⌊Audit event details and hash-chain verification⌉⌊Audit event details and hash-
chain verification⌉[

Audit event details and hash-chain verification

## Telepítés

 1. Install the plugin ZIP through **Plugins -> Add New -> Upload Plugin** and activate
    it.
 2. Open **SmartCloud -> Agent Composer** and review runtime, theme, and provider status.
 3. Create or import an inactive Config Set, review its Site Contract and Blueprints,
    then validate and explicitly activate it.
 4. Install and activate the separate WordPress MCP Adapter if an MCP client will use
    Composer.
 5. Create a dedicated WordPress user with the `smartcloud_agent` role and configure
    the client to authenticate as that user.

Composer requires WordPress 6.9 or newer and PHP 8.1 or newer.

## GYIK

### Can Composer publish or delete site content?

No. Agent-facing operations create and update drafts only. Normal content cannot
be published or deleted through Composer. Only expired, Composer-owned temporary
previews are removed automatically.

### How does an agent connect?

Install the WordPress MCP Adapter, use a dedicated authenticated WordPress user,
and connect a compatible MCP client to `/wp-json/mcp/smartcloud-agent-composer`.
An optional Connector tunnel can expose the same endpoint without changing Composer’s
WordPress authorization boundary.

### How does media handling work?

Composer can search readable Media Library images and assign an existing image as
the featured image of a Composer-owned draft. If an administrator explicitly enables
remote ingestion and allowlists an exact HTTPS host in the active Site Contract,
Composer can download one bounded raster image, validate it, store it locally, and
assign it to that draft. It cannot browse arbitrary hosts, follow redirects, edit
existing media, or delete Media Library items.

### How can configuration be preserved before uninstalling?

Open **SmartCloud -> Agent Composer -> Audit & portability** and export all configuration.
The checksum-protected JSON contains Config Sets but excludes credentials and site-
specific audit history. Restored sets remain inactive until reviewed, validated,
and activated.

### What happens on multilingual and monolingual sites?

The `list-supported-content-languages` Ability reports the Site Contract’s authoring
policy separately from provider-backed language switching and draft linking. Without
an active localization bridge, Composer does not claim that the site can switch 
or link languages; a wildcard Site Contract may still permit an agent to author 
copy in the language requested by the user. With Polylang or WPML and its matching
optional Composer bridge active, newly created drafts receive a configured language.
Two or more separately authored drafts can be linked explicitly, or one owned draft
can be added to an empty language slot in an existing translation group without 
changing any existing member, regardless of its status. Composer does not translate
copy and never publishes those drafts. TranslatePress is treated like an ordinary
WordPress site until a stable content-translation Ability becomes available, so 
agents can still author drafts while editors translate them in WordPress.

### What happens when a proposal needs another editing pass?

An authorized human reviewer can return a submitted or rejected proposal for changes
with a required reason. Composer reopens the same agent-owned working copy with 
new concurrency tokens, exposes the instruction to the assigned agent, and requires
the revised proposal to be validated and submitted again. Proposal working and audit
copies remain available under Content proposals; ordinary post and custom-post-type
lists hide them by default and provide an explicit filter to reveal them with their
proposal state.

## Vélemények

Nincsenek értékelések erről a bővítményről.

## Közreműködők és fejlesztők

“SmartCloud Agent Composer” egy nyílt forráskódú szoftver. A bővítményhez a következő
személyek járultak hozzá:

Közreműködők

 *   [ Smart Cloud Solutions Inc. ](https://profiles.wordpress.org/smartcloud/)

[“SmartCloud Agent Composer” fordítása a saját nyelvünkre.](https://translate.wordpress.org/projects/wp-plugins/smartcloud-agent-composer)

### Érdekeltek vagyunk a fejlesztésben?

[Browse the code](https://plugins.trac.wordpress.org/browser/smartcloud-agent-composer/),
check out the [SVN repository](https://plugins.svn.wordpress.org/smartcloud-agent-composer/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/smartcloud-agent-composer/)
by [RSS](https://plugins.trac.wordpress.org/log/smartcloud-agent-composer/?limit=100&mode=stop_on_copy&format=rss).

## Változási napló

#### 1.2.0

 * Proposals: Allow agents to prepare durable working copies for published content
   while keeping merge and rejection human-only.
 * Localization: Add a provider-neutral localization contract, a manifest-driven
   provider selector, and separately installable WPML and Polylang bridges for existing
   translations and separately authored multilingual drafts.
 * Safety: Recheck source, proposal, Blueprint, localization, metadata, and taxonomy
   state under a locked human merge transaction.
 * TypeScript: Use NodeNext-compatible declaration imports in the separately published
   core package.
 * Languages: Add generic supported-language discovery with distinct authoring, 
   language-switching, and localized-draft-linking signals.
 * Drafts: Store an immutable BCP 47 content language on new Composer drafts and
   keep every translation as a separate draft.
 * Polylang and WPML: Let each optional bridge assign configured languages and explicitly
   link an exact set of Composer-owned drafts without publishing them.
 * Policy: Support the `*` Site Contract and Blueprint language wildcard while allowing
   a Blueprint to narrow it.

#### 1.1.2

 * Compatibility: Declared compatibility with WordPress 7.1.

#### 1.1.1

 * Compatibility: Allow governed draft creation on SQLite-backed WordPress installations
   with an atomic, expiring idempotency lock.

#### 1.1.0

 * Taxonomies: Add a governed search, optional creation, draft assignment, and read-
   back workflow for Site Contract-approved public terms.
 * Administration: Discover attached taxonomies and configure search, assignment,
   creation, limits, assignment mode, and hierarchical parent policy in the guided
   Site Contract editor.
 * Safety: Keep term creation confirmation-gated and idempotent, restrict relationships
   to Composer-owned assigned drafts with optimistic concurrency, and expose no 
   term edit or deletion operation.

#### 1.0.4

 * Relations: Make field contracts identify the required relation lookup, write,
   and verification workflow.
 * MCP: Add concrete result schemas and stronger descriptions, including the editable-
   content alias, so clients use `search-relation-targets` for post IDs.
 * Discovery: Count and paginate `list-content-drafts` only after Composer policy
   and WordPress capability filtering.

#### 1.0.3

 * Multisite: Store shared Hub ownership per site and recognize network-activated
   owners.
 * Hub admin: Load the WebCrypto vendor before the shared admin bundle.

#### 1.0.2

 * Dependency: Rebuilt the bundled WP Suite Hub and Amplify vendor runtime with 
   exact supported SmartCloud Amplify UI 6.15.5/3.6.5/6.15.5 versions.

#### 1.0.1

 * Compatibility: Restored ownership-safe WP Suite Theme CSS fragment updates on
   WordPress-managed Custom CSS storage.

#### 1.0.0

 * Initial public release.
 * Fixed guided rule-list editing so spaces and new lines remain available while
   typing, and added pointer feedback to enabled switches.

## Meta

 *  Version **1.2.0**
 *  Last updated **1 nap ezelőtt**
 *  Active installations **Kevesebb, mint 10**
 *  WordPress version ** 6.9 vagy magasabb **
 *  Tested up to **7.1**
 *  PHP version ** 8.1 vagy magasabb **
 *  Language
 * [English (US)](https://wordpress.org/plugins/smartcloud-agent-composer/)
 * Tags
 * [abilities](https://hu.wordpress.org/plugins/tags/abilities/)[Agents](https://hu.wordpress.org/plugins/tags/agents/)
   [automation](https://hu.wordpress.org/plugins/tags/automation/)[gutenberg](https://hu.wordpress.org/plugins/tags/gutenberg/)
   [workflow](https://hu.wordpress.org/plugins/tags/workflow/)
 *  [Bővített nézet](https://hu.wordpress.org/plugins/smartcloud-agent-composer/advanced/)

## Vélemények

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/smartcloud-agent-composer/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/smartcloud-agent-composer/reviews/)

## Közreműködők

 *   [ Smart Cloud Solutions Inc. ](https://profiles.wordpress.org/smartcloud/)

## Támogatás

Vélemény? Segítségkérés?

 [Támogatói fórum megtekintése](https://wordpress.org/support/plugin/smartcloud-agent-composer/)