Hosting

Studio is served from your ASP.NET Core application.

The same host that owns your agents, tools, workflows, and Context Spaces serves the developer UI and runtime APIs.

Enable Studio

using Runiq.Core;

var app = builder.Build();

app.UseRuniqDashboard(options =>
{
    options.Authentication(auth =>
    {
        auth.AllowAnonymous();
    });
});

app.Run();

If no path is configured, Studio is served from the default /runiq path. For example, when your ASP.NET Core app is running locally, open:

http://localhost:{hostport}/runiq

auth.AllowAnonymous() is required in this example because Studio needs an authentication strategy. Anonymous access is useful for local development and demos, but production applications should use a different authentication configuration that protects the Studio surface.

Customize the Studio path and title

If you want Studio to use a different link or display title, configure Path and Title:

app.UseRuniqDashboard(options =>
{
    options.Path = "/dashboard";
    options.Title = "Runiq Context Travel Guide";
    options.Authentication(auth =>
    {
        // Demo/sample only. Do not use AllowAnonymous in production.
        auth.AllowAnonymous();
    });
});

If Path = "/dashboard", open /dashboard on the same host instead of the default /runiq path.

The root path / is not supported for Studio.

Why this helps developers

Studio runs inside the same ASP.NET Core application that registers and executes your Runiq runtime components.

That means developers inspect the same agents, tools, workflows, Context Spaces, configuration, and dependency injection graph that the application actually uses. There is no separate dashboard service to deploy, synchronize, or keep in step with the app.

For local development, run the sample or your application in Development, open /runiq or your configured path, and test the runtime from the application that owns it. This makes debugging simpler because changes to registrations, tool implementations, instructions, and context sources are visible through Studio as soon as the host app is running.