Overview
Understand the value of Runiq Studio in a .NET agent application.
Runiq Studio is the embedded developer surface for a Runiq-powered .NET application.
AI features are hard to trust when developers cannot see how the runtime reached an answer. A final assistant message does not show which instructions were active, whether a tool was called, what arguments were passed, which source excerpts were retrieved, or which workflow step produced the output.
Studio solves that by making the runtime visible from the same ASP.NET Core host as your application. Developers can open it at the path they configure, inspect registered components, run agents, test tools, execute workflows, browse Context Spaces, and debug streaming execution events without deploying a separate control plane.
The current hosting API is named UseRuniqDashboard, but the developer-facing product concept is Studio.
What problem Studio solves
AI runtime behavior is hard to debug when everything is hidden behind a single chat response.
When an agent gives a surprising answer, a developer usually needs to know:
- Which agent handled the request?
- What instructions and model settings were active?
- Which tools were attached?
- Did the model call a tool?
- What arguments did it pass?
- What did the tool return?
- Was source context retrieved?
- Which skill instructions were active?
- Which workflow step produced the final output?
Studio makes those runtime details inspectable from the application that owns them. That changes the development loop: instead of guessing why an AI feature behaved a certain way, you can inspect the actual runtime path.
Why embedded matters
Runiq is designed for .NET-native embedded AI applications. Studio follows the same model.
You do not need a separate hosted dashboard service just to inspect your agents. The same ASP.NET Core app that registers agents, tools, workflows, and Context Spaces can also serve Studio.
For .NET teams, that matters. You can build, run, and debug the AI runtime the same way you debug the rest of the app: locally, inside the host, with the same registrations and configuration the application uses.
This keeps the development loop simple:
What Studio shows
| Area | What developers can inspect |
|---|---|
| Agents | Registered agents, instructions, model, runtime settings, attached tools, and attached Context Spaces. |
| Tools | Tool names, descriptions, input schema, output schema, attached agents, and direct tool run output. |
| Workflows | Workflow definitions, steps, transitions, failure behavior, run results, and step outputs. |
| Context Spaces | Sources, source documents, previews, skills, attached agents, and context metadata. |
| Chat/run events | Assistant deltas, tool calls, context events, skill events, failures, and completion. |
Studio is not the production user interface for your app. It is the developer surface for testing and debugging the Runiq runtime inside your app.
Theme support
Studio supports both light and dark themes. The examples in this documentation use light theme by default so screenshots stay readable in print and docs pages, but developers can switch to dark theme from the Studio UI when that better fits their local environment.
Dark theme uses the same runtime metadata and debugging surfaces. Only the presentation changes; registered agents, tools, workflows, Context Spaces, and run inspection behave the same way.