Design Chat
The design chat is the package's single conversational surface: ask questions about the current design, capture decisions, and request changes that you can apply with one click. It lives on the Architecture tab.
Plan Availability
Design chat is available on the Medium plan and above.
What It Can Do
The chat is grounded in this package: the current components and flows, your inputs, compliance state, and uploaded knowledge documents. Ask "why is there a dedicated secrets tier?" or "which components handle PHI?" and the answers cite the design in front of you, not general knowledge.
Tell it a decision ("we agreed to stay on the incumbent IdP until the contract renews") and it records an ADR with rationale into the package's decision log, alongside the ADRs generation writes. See Decisions and ADRs.
Ask for a change ("route payment callbacks through the gateway", "swap the cache for the in-use standard") and the chat returns a concrete change set: components and flows to set or remove: which you review and apply. Applied changes land exactly like your own edits: locked as architect decisions, surviving re-runs, and re-evaluated immediately. See Edit and Lock the Design.
Boundaries Worth Knowing
- Chat never changes the design silently; every modification goes through the visible apply step.
- Applied changes carry the same consequences as manual edits, including the risk sign-off requirement for approval.
- The chat reads the package it is opened in; it does not browse other packages or your wider estate.
- Like every AI surface in the product, usage is metered and attributed on your organization's usage ledger.