Make your first decision in Studio
Use this guide to build and inspect a first run in Siliqun Rotor Studio. Account creation is free and does not require a payment card. Select Create a free account. If email confirmation is enabled, follow the confirmation link and then sign in.
1. Open your project
Open Siliqun Rotor Studio and create a free account or sign in. A new cloud workspace with no projects creates My first project automatically. When connected to your own engine, Studio uses a browser-stored project until that engine stores projects.
2. Copy the browser demo's tools
On the Siliqun Rotor home page, scroll to the browser demo and choose Download Demo tools. It downloads leave-tools.json, containing the same two read-only tool declarations used by that demo. The declarations describe tools; they do not include its fictional records or connect to an HR system.
3. Add the tools to your project
Open Connect tools. Expand Other ways to add tools, then find the Import MCP tools section. Paste the contents of leave-tools.json into Or paste a tools list (MCP tools/list, or OpenAI functions) and choose Add these tools. The download is a bare array of MCP tool declarations; the paste field accepts that array or an object with a tools array. The page reports when it saves the declarations to the current project.
4. Select the declarations and prepare a flow
Open Agent Harness. Select the leave declarations for the current project, enter a name in Flow name, and choose Prepare flow in Flow Designer. Studio opens Flow Designer with that project's draft. Review the draft and choose Save & Activate to make this version the project's active flow. If the project already has a saved flow, review the selected tools and intended changes before activating the new version.
5. Wire the activated flow into your application
To inspect a chat-completions request, open OpenAI Wire. To view integration details for the active flow, open Ship. The browser demo's leave-tools.json contains only tool declarations; it does not include the demo's fictional leave records. Studio configuration does not connect to an employer's HR system, execute an external handler, or return a real employee balance. Your application remains responsible for user authorization and executing approved actions.
For the engine request and response contract, see the local engine quickstart and agent-flow guide.
To turn the selected call into an employee-facing result, follow Return a leave balance to an employee. Ship provides the runnable customer application; connect it to your existing customer authentication and authorized HR service.