@evelinka-ai/console
v0.6.4
Published
The complete, reusable Eve operator console shell and UI.
Readme
@evelinka-ai/console
The complete Eve operator console, published as a compiled static application.
eve-ai-layer remains the canonical source for the shell, navigation, routes,
operator screens, UI primitives, and block renderers. A standalone Eve product
serves these assets behind its own authenticated same-origin gateway instead of
copying the React application.
Hosting
Resolve @evelinka-ai/console/package.json, then serve the sibling dist/
directory as an SPA. Before the bundled entry script runs, a standalone host
injects its instance identity:
<script>
window.__EVE_CONSOLE_CONFIG__ = {
standalone: true,
instance: {
id: "my-agent",
basePath: "/my-agent"
}
};
</script>Capabilities come from the authenticated agent's /eve/v1/capabilities
manifest. Missing, invalid or unavailable capabilities stay disabled; a host's
legacy instance.caps declaration is ignored. The console calls global
/auth/* for identity and ${basePath}/eve/* for the control plane on the same
origin. The host must authenticate and authorize those routes server-side.
The package script builds with vite build --mode package, which emits relative
module and lazy-preload URLs. The fleet's ordinary build retains its root base.
For a prefix, serve the entire dist/ below that prefix and inject a matching
HTML <base href="/my-agent/"> before asset links so deep links reload correctly.
Rewrite any root-relative HTML/manifest asset URLs into the same prefix; set
manifest id, start_url and scope to the hosted prefix. Use an empty
basePath and <base href="/"> for a root deployment. Do not rewrite bundled
JavaScript or expose unprotected root asset aliases.
Standalone consoles do not register the fleet's origin-wide service worker or offer web-push subscriptions. The host owns cache policy and must account for any pre-existing service worker during a same-origin cutover; the console never unregisters another application's worker.
The default identity is Eve. label and shortLabel exist for tenant products
that already use a distinct Eve identity; a host that wants the unchanged Eve
console should omit both, as above.
