Use natural-language prompts to ask questions about your architecture or instruct the Copilot to modify it. The assistant reasons over your model graphand any attached documents, returning answers with citations and visual diffs where relevant.
To provide context via a PDF in Copilot, import it under the Requirements page — the Copilot will automatically look through the generated requirements. You can also directly attach any image or text-based file via the Attach: + button.
Once the plan is identified, the assistant returns a changes response – a structured diff showing which nodes, edges, or requirements will be added, updated, or removed.Click Apply to stage the commit. The button then turns into Accept / Reject options:
Button
Meaning
Accept
Commits the change and unlocks the next commit in the sequence.
Reject
Discards the staged change.
Commits must be processed in the exact order they were generated. If an earlier commit is still pending, later commits show the Apply button in a disabled state with a tooltip explaining the sequence rule.
After a commit is accepted, a Reset (⟲) button replaces it. Reset rolls the change back to the Applied (Staged) state so you can reject it.
After changes are proposed, Copilot produces a concise summary of the plan & resulting diffs, capturing the rationale behind the design so stakeholders can quickly grasp the bigger picture.