ONE APP. EACH CAPABILITY, IN CONTEXT.
Start local.
Build something capable.
Build Operations Desk, a .NET assistant that grows from its first reply into a connected, observable application. Understand the how and the why at every step.
Two ways to bring chat to your users
Before you start
Use .NET 10 and a matching FabrCore 2.0 package set. Start with the source checkout if the release packages are not available in your feed. The first echo agent needs no model key, database, Microsoft tenant, or Cloud Server account. Later lessons call out those prerequisites when they become useful.
Each lesson explains the feature, walks through its use, and shows how to interpret the result. Where configuration has two supported paths, Files & code contains the local JSON or C# and Cloud Server explains the equivalent management contract. Vulcan365 Insights is one implementation of that open Cloud Server contract.
Download the Operations Desk source checkpoints — echo/AI host, C# client, reusable WebSocket service and Blazor SurfaceChatLink app. The README explains package versions and local ports.
The complete learning path
Get a complete app running on localhost
A developer runs a host, creates an agent, and gets a reply from a C# client, then upgrades the same agent to use a model.
Open module →Design agents and messages that compose
Operations Desk has a well-defined contract, safe lifecycle behavior, and observable routing.
Open module →Give agents tightly integrated tools and plugins
The assistant can look up and update fixture service requests through explicit business operations.
Open module →Manage state, sessions, and context
The assistant remembers the current conversation and application state within the configured storage lifetime, without unbounded prompts.
Open module →Build a remote WebSocket chat client and user experience
Build a standalone chat client that reaches Operations Desk over HTTPS/WebSocket without direct access to the Orleans cluster, then add a richer interface and actionable cards.
Open module →Use the full harness for multi-step work
The assistant investigates a request, tracks remaining work, consults specialists, and reports completion honestly.
Open module →Package the app with blueprints and squads
One reusable definition provisions the cooperating agents for each principal.
Open module →Turn the workstation app into a durable platform
The same app survives restart and has an explicit identity and authorization boundary.
Open module →Add durable Memory and grounded knowledge
The assistant recalls useful facts and answers policy questions with scoped source evidence.
Open module →Integrate deeply with the Microsoft ecosystem
Operations Desk can securely use Microsoft resources and participate in Microsoft agent experiences.
Open module →Publish interoperable interfaces
Other applications can use the assistant without adopting its UI or internal runtime.
Open module →Observe, verify, and test the application
A developer can explain a request's behavior, measure quality/cost, and distinguish monitoring from signed evidence.
Open module →Operate with a Cloud Server
Readers can manage the app across environments and understand enough of the open contract to build their own cloud implementation.
Open module →Finish, extend, and keep the app current
Review the complete app, choose its next architecture and keep it current.
Open module →