Local runtime
Private context, routing preferences, and direct capabilities stay on the user machine.
Elyan routes work through one coherent order: local capability, structured MCP context, MCP tools, browser automation, bounded crawl, then direct answer when no external action is needed.
Private context, routing preferences, and direct capabilities stay on the user machine.
Accounts, subscriptions, entitlements, credits, and hosted billing stay narrow and explicit.
MCP, browser, crawl, docs, charts, and structured tools remain optional and explicit.