Composer & Generative AI

Composer is an AI-assisted workflow editing feature inside Workflow Studio. It helps you describe changes in natural language and proposes structured edits to your workflow graph.

Composer is powered by generative AI. Outputs may be incorrect, incomplete, or unsuitable for your use case. You remain responsible for reviewing proposed changes before applying them and for the workflows you publish or run.

Effective date: May 26, 2026 Last updated: May 26, 2026

On This Page

• What Composer is
• Third-party AI models
• How Composer works on Edgaze
• Guardrails and safety controls
• What Edgaze does not guarantee
• Your responsibilities
• Data handling
• External provider policies
• Related policies

What Composer Is

Composer is a constrained editing assistant for Workflow Studio. It is designed to help you:

• inspect the current workflow graph
• propose additions, configuration updates, connections, and other supported edits
• validate proposed changes before they are applied
• explain what it intends to change

Composer is not:

• a general-purpose chatbot
• a substitute for professional, legal, financial, medical, or other regulated advice
• a guarantee that a workflow will run correctly, comply with law, or produce accurate results
• an autonomous system that silently rewrites your workflow without review

Publication or use of Composer does not mean Edgaze endorses any suggestion, output, or resulting workflow configuration.

Third-Party AI Models

Composer sends prompts and relevant workflow context to external AI model providers to generate responses and proposed actions. Edgaze does not operate those models itself.

At the time of this writing, Composer may route requests through providers such as Anthropic (for example, Claude-family models). Providers, model versions, and routing may change over time.

When you use Composer, your use is also subject to the applicable third-party provider terms, policies, and acceptable use rules, in addition to Edgaze's terms and policies. Those providers may process requests according to their own privacy, retention, safety, and abuse-monitoring practices.

You should not submit information through Composer unless you are comfortable with Edgaze and the relevant provider processing that information for the purpose of generating a response.

How Composer Works on Edgaze

Edgaze uses a structured harness around the language model. The model does not receive unrestricted direct write access to your canvas.

In general:

1. You send a prompt describing what you want to build or change.
2. Composer inspects the current workflow state through controlled tools.
3. The model proposes structured actions (for example, add a node, update configuration, connect nodes).
4. Edgaze validates those actions against workflow rules, allowed blocks, and connection constraints.
5. Validated changes are converted into typed patches and applied in a controlled transaction, or held for your approval when required.
6. You can review, approve, reject, or roll back certain changes from the Composer panel where supported.

This design is intended to reduce accidental or unsupported edits, but it does not eliminate the risk of incorrect or undesirable suggestions.

Guardrails and Safety Controls

Edgaze applies multiple layers of controls to Composer. These are operational safeguards, not a warranty of correctness.

Structured actions only

The model proposes typed actions. It does not mutate the live graph directly. Unsupported or malformed proposals are rejected before application.

Allowed blocks and connections

Composer may only add or modify workflow elements from Edgaze's supported block library and permitted connection rules. Proposals outside those constraints are blocked.

Validation before apply

Proposed changes are checked for graph validity (for example, missing nodes, invalid handles, structural issues) before they are applied.

Confirmation for high-risk changes

Destructive or high-risk changes—such as deleting nodes or disconnecting edges—may be held for explicit user approval before anything is applied to the canvas. Nothing in that category should be applied silently without your confirmation when confirmation is required.

Transaction limits

Composer enforces practical limits to reduce runaway automation, including limits on agent turns, tool usage, nodes per transaction, and overall workflow size. These limits may change as the product evolves.

Concurrency protection

If you edit the canvas while Composer is working, Edgaze attempts to detect conflicting changes and avoid silently overwriting your manual edits.

Rollback

Where supported, you may undo the most recent Composer-applied change from the Composer changes panel. Rollback availability depends on the change type and current workflow state.

Rate limiting

Composer applies separate limits for new chat messages you send versus the in-session model turns Composer uses while building a workflow (tool loops). That way a single long run is unlikely to fail mid-session with a “too fast” error. If limits are reached, wait for the suggested retry window or send fewer prompts in a short period.

Locked or read-only workflows

Composer cannot edit workflows that are locked or otherwise read-only (for example, certain published or restricted states).

What Edgaze Does Not Guarantee

Edgaze does not guarantee that Composer will:

• understand your intent correctly on the first attempt
• produce optimal, minimal, or production-ready workflows
• avoid all incorrect configurations, unsafe prompts, or incompatible connections
• comply with your internal policies, industry rules, or legal obligations
• remain available without interruption

AI outputs and AI-assisted edits may be wrong even when they appear confident or detailed.

Your Responsibilities

You are responsible for:

• Reviewing proposed changes, diffs, and workflow behavior before applying or publishing
• Testing workflows with representative inputs before relying on them commercially
• Verifying that outputs, prompts, and integrations are accurate, safe, and lawful for your use case
• Not submitting passwords, API keys, secrets, or unnecessary sensitive personal data into Composer prompts
• Maintaining your own API keys and third-party account obligations where applicable
• Deciding whether a Composer suggestion should be applied, modified, or rejected

If you are unsure whether a workflow or output is appropriate, do not publish or deploy it until you have independently verified it.

Data Handling

Information you submit to Composer (including prompts, attachments where supported, and workflow context sent to the model) may be processed by Edgaze and by external model providers to operate the feature.

For broader information about collection, use, retention, and sharing of personal information, see the Privacy Policy.

Do not use Composer to process data you are not authorized to share with Edgaze or with the relevant AI provider.

External Provider Policies

Because Composer relies on external AI services, you should review the applicable provider documentation and terms. Provider policies may cover:

• acceptable use and prohibited content
• data handling and retention
• safety filtering and refusals
• service availability and model behavior changes

Edgaze is not responsible for third-party provider outages, policy changes, model behavior, or content moderation decisions made by those providers.

Related Policies

• Content Disclaimer — AI outputs, creator content, and reliance limitations
• Terms of Service — platform agreement
• Acceptable Use Policy — prohibited uses
• Privacy Policy — data handling
• Workflow Run Policy — hosted execution rules
• Workflow Studio — builder overview

Contact

Questions about Composer or this notice may be sent to `[email protected]`.