Add EyeAuras Tools To Another App

Use When

• The feature runs inside another app or plugin host.
• The host supplies ticks, render callbacks, or domain events.
• The user needs EyeAuras-powered windows, screen visuals, scripting, or automation in that host.
• A normal EyeAuras script is not the entry point.

Shape

• Reference EyeAuras.SDK.Embedded from the host app/plugin and create a host-owned EyeAurasEmbeddedBootstrapper subclass.
• Start the embedded SDK runtime explicitly from the host/plugin, usually on the UI-capable STA thread that owns EyeAuras UI work.
• Register host services in the host bootstrapper/container before running it.
• Declare only the embedded capabilities the host needs with ConfigureEmbeddedModules(IEyeAurasModuleSetBuilder modules).
• Run the bootstrapper, then call EnsureReadyAsync(...) before using services from requested modules.
• The embedded base loads static web assets and requested modules. It does not register REPL or scripting services unless an opted-in module does that work.
• Bridge host events into EyeAuras-facing services.
• Show complex controls through Blazor windows.
• Draw visuals through host rendering or OSD APIs.
• Add Behavior Tree or hosted scripting only if users need editable automation.

Minimal shape:

public sealed class MyEmbeddedBootstrapper : EyeAurasEmbeddedBootstrapper
{
    private readonly IMyHostService hostService;

    public MyEmbeddedBootstrapper(IUnityContainer container, IMyHostService hostService) : base(container)
    {
        this.hostService = hostService;
    }

    protected override void ConfigureContainer()
    {
        base.ConfigureContainer();
        Container.RegisterInstance<IMyHostService>(hostService);
    }

    protected override void ConfigureEmbeddedModules(IEyeAurasModuleSetBuilder modules)
    {
        modules.UseUiCore();
        modules.UseBehaviorTree();
        modules.UseMemory();
    }
}

var container = new UnityContainer();
var bootstrapper = new MyEmbeddedBootstrapper(container, hostService);
bootstrapper.Run(runWithDefaultConfiguration: true);
await bootstrapper.EnsureReadyAsync(cancellationToken);

Choices

• How much of the SDK runtime to load.
• Which thread can safely create UI.
• Whether visuals should use host rendering, OSD, Blazor windows, or mixed UI.
• Whether automation belongs to host callbacks, Behavior Tree, scripts, or services.

APIs To Look Up

• EyeAuras.SDK.Embedded
• EyeAurasEmbeddedBootstrapper
• EyeAurasEmbeddedBootstrapper.ConfigureEmbeddedModules
• EyeAurasEmbeddedBootstrapper.EnsureReadyAsync
• IEyeAurasModuleSetBuilder
• IEyeAurasModuleSetBuilder.UseModule
• IEyeAurasModuleSetBuilder.UseModules
• IEyeAurasModuleLoadPlan
• UseUiCore()
• UseBehaviorTree()
• UseMemory()
• UseOpenCVAuras()
• UseRoxy()
• EyeAurasWebAppBootstrapper
• IBlazorWindow
• IBlazorWindowAccessor
• IOnScreenCanvas
• IBehaviorTreeRootNode
• IReactiveBehaviorTreeEditor
• IAuraScriptFactory

Avoid

• Treating embedded-host code like a normal script context.
• Expecting script globals such as Log, AuraTree, Variables, Sleep, or cancellationToken in ordinary embedded host classes.
• Adding sandbox-style wrapper APIs around the bootstrapper; embedded host code is app/plugin infrastructure, not script infrastructure.
• Manually editing generated script files to add host glue; put standalone initialization in Program.cs and the bootstrapper.
• Assuming REPL or scripting services exist before an opted-in module registers them.
• Manually scanning static web assets, loading Prism modules, loading module payload DLLs, or calling IApplicationAccessor.ReportIsLoaded() from the consumer app when EnsureReadyAsync(...) can own that lifecycle.
• Creating UI windows from the wrong thread.
• Blocking host tick/render callbacks with SDK or UI work.
• Exposing host-private objects directly to user scripts.
• Persisting volatile host handles, pointers, or session objects.

Related Maps

• core/app-runtime-contexts.md
• core/app-modules.md
• windows-subsystems/blazor-windows.md
• osd/screen-overlay.md
• scripting/runtime.md