Iris Workbench
Give the conversation
somewhere to go.
Ask Iris to research, write or build. Keep the relevant files, tool activity and project context beside the conversation.
“Make a small forecast app. Keep my saved location. Show me what changed.”
Preauthored Workbench Simulation
Open the plan. Try the work.
Approve a sample plan, inspect files, interrupt the work and change the provider choice. This is a fixed simulation, not a model run.
Not every job is code.
Use the parts that fit the task. Availability and costs depend on the model, tools and account you configure.
Talk It Through
Live voice calls use the optional Live Voice configuration and ask for microphone access. Review the displayed rate and duration before connecting. Spoken requests still pass through the normal tool and permission rules.
Make It Visual
Ask for a chart or a supported interactive explanation. Image generation and editing use the configured image tools. Generated output still needs review; the public examples do not make paid media requests.
Bring The Useful Context
Choose project material, knowledge and connected sources. Saved memory can help with continuity, but retrieval can miss important facts. Check the sources behind consequential conclusions.
What Is Happening Here?
The example is deliberately small. These are the parts to understand before bringing your own task.
From Request To Plan
Break a task into inspectable steps. Review a plan before execution when the workflow calls for it.
Tools In Context
Use the connected tools and selected knowledge available to the current agent. Inspect activity instead of relying on a final summary alone.
Work You Can Keep
Return to conversations, project material and files. Branch a conversation to explore another direction; remember that forks can share the account's file workspace.
Where It Stops
Models can make mistakes and retrieval can miss context. Review important output. Available tools, file operations and model features depend on permissions and configuration.