Using Uru Architect
17 steps - 8 minutes
Learn how to use Uru Architect to build automations with natural language.
What is Uru Architect?
Uru Architect is an AI assistant integrated with the automations builder that uses GraphPatch DSL to express changes. It auto-applies changes for empty builders (Live Build) and proposes edits for existing builders with side-by-side interactive visual diffs. Patches appear as custom-styled tool bubbles with undo functionality via version snapshots. Architect uses platform tools to create resources and list_tools to discover integrations.
Navigate to Automations
From the sidebar, click on "Automations" to access your automations.
Open or Create an Automation
Either create a new automation or open an existing one you want to modify.
Click "Uru Architect" Tab
Click the "Uru Architect" tab to switch to the AI-powered automation builder. This opens a chat interface integrated with the automations builder.
Understanding Live Build vs Proposals
For empty builders, Live Build is enabled by default and changes are auto-applied. For existing builders, Architect proposes edits that you can review and apply.
Describe What You Want
Type a natural language description of the automation you want to build. Be specific about the workflow, triggers, and desired outcomes. The chat uses SSE streaming matching normal chat behavior.
Architect Uses GraphPatch DSL
Architect expresses changes using GraphPatch DSL with operations: add_node, remove_node, update_node, connect, disconnect, set_persona, set_prompt, attach_contexts, detach_contexts, set_tool_whitelist, set_trigger, layout.
Before
After (Proposed)
Patch Bubbles in Timeline
When Architect generates a patch, it appears as a custom-styled tool bubble in the timeline (not in the chat response text). The patch JSON is displayed in the bubble.
Review the Visual Diff
For existing builders, Architect shows a creative side-by-side visual diff with two fully interactive ReactFlow builder views (movable nodes, normal edges, openable nodes).
Interact with the Visual Diff
Both sides of the diff are fully interactive. You can move nodes, open them, and inspect the proposed changes. Any change request typed in the diff appears as a new user message in the Architect conversation.
Apply or Undo Changes
When a patch bubble completes, it shows only an "Undo" option. The system saves a snapshot of the automation state at that time so you can revert to it at any time.
Undo via Version Snapshots
Click "Undo" on any patch bubble to restore the automation to the state before that patch was applied. This uses version snapshots stored when each patch is applied.
Architect Sends Full Graph Snapshot
Architect always sends the full unsaved graph snapshot each turn, including node types and schemas in the static system prompt.
Ask Architect to Create Resources
Architect can create personas, prompts, and context blocks using platform tools. It can list available resources and then use them in automations.
Request Tool Discovery
Ask Architect to find specific tools or integrations. It uses list_tools to discover subtools and can add them to your automation with full schemas.
Non-Patch Responses Allowed
Not every Architect response must change the automation. It can answer questions, provide guidance, or explain concepts without generating a patch.
Architect Conversations are Separate
Architect conversations are fully separate from main chat. They never appear in the chat page and are specific to the automation builder.
Test the Automation
Once satisfied with the design, switch back to the builder view and run a test to verify it works as expected. Test runs use the current in-builder (unsaved) state.
Best Practices
- •Be specific about your workflow requirements
- •Review proposals carefully before applying changes
- •Use the visual diff to understand what will change
- •Iterate with feedback to refine the automation
- •Test automations after applying Architect changes
- •Use Undo if changes do not work as expected