Build Architect AI
Say what you want.
Approve what it builds.
Describe the agent you need in one message. The Architect reads your workspace, writes a plan you can check step by step, and builds it in Test, where no customer sees it until you release.
- 180
- tools it can call across your workspace
- 29
- ready agents it can start from
- 3
- approval modes, from every step to end to end
- 2:17
- to build our demo clinic agent, in 17 steps
Approval
Nothing changes until you say so.
Every request becomes a plan of named steps, each saying what it does and why. You choose how much of it waits for you.
Manual
Every step waits for you, lookups included. Approve them one at a time, or all at once.
Auto-read
DefaultLookups run on their own, so the plan you review is only the changes. Anything that writes asks first.
Autopilot
Runs end to end. Deletes, costly runs and sensitive steps — credentials, invitations, sends, activations — still ask.
The server checks every call against the same rules, so a plan can never do more than its mode allows. Production is read-only. The Architect builds in Test, and changes reach customers only in a release you activate.
On every page
It knows where you are.
Open the Architect from the corner of any dashboard page. It already knows the page, the bot and the tab, so “add a field here” is enough. The change shows up on the page behind it, no reload.
Edit what exists
The smallest change that works.
Most of the work is changing what already runs. The Architect reads the bot and everything attached to it, changes only what the request needs, then checks it. Here, a fix for a flagged reply is replayed in Test before it’s marked done.
Reach
One conversation, the whole workspace.
The Architect works through the same 180 tools your AI editor can use, with your permissions and your plan's limits.
- 01Agents
Bots, prompts and their versions, skills, session and memory settings.
bots.create - 02Knowledge
Websites, files and connections, synced and tested for retrieval.
kb.add_source - 03Tools
HTTP connectors, MCP servers and the tools a bot may call.
connectors.create - 04Conversations
Flows, workflows and agent teams with routing and handoffs.
flows.create - 05Safety
Guardrails, test cases, red-team attacks and edge-case fixes.
guardrails.create - 06Reach
Channels, automations, broadcasts and alert rules.
channels.create
Say it, or show it
Speak, and the words are typed for you to fix before you send. Or attach up to 4 screenshots of a page or a form and build from those.
A checklist of what you asked
Each chat keeps your requirements as a numbered list and marks which ones show up in the changes applied so far. Nothing you asked for quietly drops.
Three builds at once
Run up to three chats side by side. Each keeps its own draft, its own subject and its own place in the work.
Your model, your key
Pick the model it plans with, and it stays picked across chats. Every call runs on your own provider key. Rylvo adds no markup.
Questions
