@elizaos/core 2.0.0-alpha.7 → 2.0.0-alpha.70

package/dist/onboarding-state.d.ts

@@ -1,209 +0,0 @@
-/**
- * Onboarding State Machine for ElizaOS.
- *
- * Manages the step-by-step onboarding flow across platforms.
- * Ported from the Python/Rust reference implementations.
- *
- * @module onboarding-state
- */
-/**
- * Steps in the onboarding flow.
- */
-export declare enum OnboardingStep {
-    WELCOME = "welcome",
-    RISK_ACK = "risk_ack",
-    AUTH = "auth",
-    CHANNELS = "channels",
-    SKILLS = "skills",
-    COMPLETE = "complete"
-}
-/** Canonical step order. */
-export declare const ONBOARDING_STEP_ORDER: OnboardingStep[];
-/** Human-readable step labels. */
-export declare const ONBOARDING_STEP_LABELS: Record<OnboardingStep, string>;
-/** Step descriptions. */
-export declare const ONBOARDING_STEP_DESCRIPTIONS: Record<OnboardingStep, string>;
-export interface OAuthTokens {
-    accessToken: string;
-    refreshToken?: string;
-    expiresAt?: number;
-}
-export interface AuthSettings {
-    modelProvider?: string;
-    apiKey?: string;
-    oauthTokens?: OAuthTokens;
-    setupToken?: string;
-    authMethod?: string;
-}
-export interface ChannelConfig {
-    type: string;
-    enabled: boolean;
-    credentials?: Record<string, string>;
-    settings?: Record<string, string | boolean | number>;
-}
-export interface ChannelSettings {
-    enabledChannels: string[];
-    channelConfigs: Record<string, ChannelConfig>;
-    dmPolicy?: Record<string, boolean>;
-}
-export interface SkillsSettings {
-    enabledSkills: string[];
-    skillsToInstall: string[];
-    useHomebrew?: boolean;
-    nodeManager?: string;
-}
-export interface OnboardingSettings {
-    auth?: AuthSettings;
-    channels?: ChannelSettings;
-    skills?: SkillsSettings;
-    riskAcknowledgedAt?: number;
-    riskAcknowledged?: boolean;
-    gateway?: Record<string, string | number | null>;
-}
-export interface OnboardingStepError {
-    code: string;
-    message: string;
-    step: OnboardingStep;
-    timestamp: number;
-    details?: Record<string, unknown>;
-}
-export interface OnboardingContext {
-    currentStep: OnboardingStep;
-    completedSteps: OnboardingStep[];
-    settings: OnboardingSettings;
-    errors: OnboardingStepError[];
-    startedAt: number;
-    lastActivityAt: number;
-    platform: string;
-    mode: string;
-    sessionId: string;
-    worldId?: string;
-    userId?: string;
-    interrupted?: boolean;
-    metadata?: Record<string, unknown>;
-}
-export interface WelcomeInput {
-    acknowledged: boolean;
-    userName?: string;
-}
-export interface RiskAckInput {
-    accepted: boolean;
-    warningText?: string;
-}
-export interface OAuthCallback {
-    code: string;
-    state: string;
-}
-export interface AuthInput {
-    method: string;
-    provider?: string;
-    apiKey?: string;
-    oauthCallback?: OAuthCallback;
-    setupToken?: string;
-    skip?: boolean;
-}
-export interface ChannelEntry {
-    type: string;
-    enabled: boolean;
-    token?: string;
-    credentials?: Record<string, string>;
-    settings?: Record<string, string | boolean | number>;
-}
-export interface ChannelsInput {
-    channels: ChannelEntry[];
-    dmPolicy?: Record<string, boolean>;
-    skip?: boolean;
-}
-export interface SkillsPreferences {
-    useHomebrew?: boolean;
-    nodeManager?: string;
-}
-export interface SkillsInput {
-    skills?: string[];
-    install?: string[];
-    preferences?: SkillsPreferences;
-    skip?: boolean;
-}
-export interface OnboardingResult {
-    success: boolean;
-    newStep: OnboardingStep;
-    isComplete: boolean;
-    error?: OnboardingStepError;
-    message?: string;
-    context?: OnboardingContext;
-    data?: Record<string, unknown>;
-}
-export interface StepProgressInfo {
-    step: OnboardingStep;
-    label: string;
-    status: 'completed' | 'current' | 'pending' | 'error';
-    errorMessage?: string;
-}
-export interface OnboardingProgress {
-    currentStepNumber: number;
-    totalSteps: number;
-    percentage: number;
-    steps: StepProgressInfo[];
-}
-export interface SerializedOnboardingState {
-    version: number;
-    context: OnboardingContext;
-    checksum?: string;
-}
-export interface ValidationResult {
-    valid: boolean;
-    error?: string;
-    details?: Record<string, unknown>;
-}
-export type StepHandler = (data: unknown, context: OnboardingContext) => Promise<OnboardingResult>;
-export type OnStepChangeCallback = (oldStep: OnboardingStep, newStep: OnboardingStep, context: OnboardingContext) => Promise<void> | void;
-export type OnCompleteCallback = (context: OnboardingContext) => Promise<void> | void;
-export type OnErrorCallback = (error: OnboardingStepError, context: OnboardingContext) => void;
-export interface OnboardingStateMachineConfig {
-    platform: string;
-    mode?: string;
-    worldId?: string;
-    userId?: string;
-    existingContext?: OnboardingContext;
-    onStepChange?: OnStepChangeCallback;
-    onComplete?: OnCompleteCallback;
-    onError?: OnErrorCallback;
-}
-/** Get index of a step in the canonical order (returns -1 if not found). */
-export declare function getStepIndex(step: OnboardingStep): number;
-/** Get next step after the given one, or null if at end. */
-export declare function getNextStep(current: OnboardingStep): OnboardingStep | null;
-/** Get previous step, or null if at beginning. */
-export declare function getPreviousStep(current: OnboardingStep): OnboardingStep | null;
-/** Check if a step is completed in the context. */
-export declare function isStepCompleted(context: OnboardingContext, step: OnboardingStep): boolean;
-/** Calculate progress percentage. */
-export declare function calculateProgress(context: OnboardingContext): number;
-/** Check if onboarding is complete. */
-export declare function isOnboardingComplete(context: OnboardingContext): boolean;
-/** Get a human-readable summary of onboarding state. */
-export declare function getOnboardingSummary(context: OnboardingContext): string;
-export declare class OnboardingStateMachine {
-    private context;
-    private readonly config;
-    private readonly handlers;
-    constructor(config: OnboardingStateMachineConfig);
-    getCurrentStep(): OnboardingStep;
-    getContext(): OnboardingContext;
-    getSettings(): OnboardingSettings;
-    canAdvance(): boolean;
-    getProgress(): OnboardingProgress;
-    advanceStep(step: OnboardingStep, data: unknown): Promise<OnboardingResult>;
-    skipStep(): Promise<OnboardingResult>;
-    goBack(targetStep?: OnboardingStep): OnboardingResult;
-    toJSON(): SerializedOnboardingState;
-    static fromJSON(serialized: SerializedOnboardingState, config: OnboardingStateMachineConfig): OnboardingStateMachine;
-    reset(): void;
-    registerHandler(step: OnboardingStep, handler: StepHandler): void;
-    private makeError;
-    private handleStepDefault;
-}
-/**
- * Factory function for creating an OnboardingStateMachine.
- */
-export declare function createOnboardingStateMachine(platform: string, mode?: string, worldId?: string, userId?: string, onStepChange?: OnStepChangeCallback, onComplete?: OnCompleteCallback, onError?: OnErrorCallback): OnboardingStateMachine;

package/dist/plugin.d.ts

@@ -1,55 +0,0 @@
-import type { Plugin } from './types';
-/**
- * Attempt to install a plugin using Bun
- * Returns true if installation succeeded, false otherwise
- */
-export declare function tryInstallPlugin(pluginName: string): Promise<boolean>;
-/**
- * Check if an object has a valid plugin shape
- */
-export declare function isValidPluginShape(obj: unknown): obj is Plugin;
-/**
- * Validate a plugin's structure
- */
-export declare function validatePlugin(plugin: unknown): {
-    isValid: boolean;
-    errors: string[];
-};
-/**
- * Load and prepare a plugin for use
- */
-export declare function loadAndPreparePlugin(pluginName: string): Promise<Plugin | null>;
-/**
- * Normalizes a plugin name by extracting the short name from scoped packages
- * Examples:
- *  - '@elizaos/plugin-discord' -> 'discord'
- *  - '@elizaos/plugin-sql' -> 'sql'
- *  - 'bootstrap' -> 'bootstrap'
- *  - 'plugin-custom' -> 'plugin-custom'
- */
-export declare function normalizePluginName(pluginName: string): string;
-/**
- * Resolve plugin dependencies with circular dependency detection
- * Performs topological sorting of plugins to ensure dependencies are loaded in the correct order
- *
- * Supports both scoped package names (@elizaos/plugin-discord) and short names (discord)
- */
-export declare function resolvePluginDependencies(availablePlugins: Map<string, Plugin>, isTestMode?: boolean): Plugin[];
-/**
- * Load a plugin by name or validate a provided plugin object
- * @param nameOrPlugin - Plugin name string or Plugin object
- * @returns Loaded Plugin or null if failed
- */
-export declare function loadPlugin(nameOrPlugin: string | Plugin): Promise<Plugin | null>;
-/**
- * Resolve multiple plugins with dependency ordering
- * Browser-compatible wrapper that handles Node.js-only plugin loading
- *
- * @param plugins - Array of plugin names or Plugin objects
- * @param isTestMode - Whether to include test dependencies
- * @returns Ordered array of resolved plugins
- *
- * Note: In browser environments, string plugin names are not supported.
- * Only pre-resolved Plugin objects can be used.
- */
-export declare function resolvePlugins(plugins: (string | Plugin)[], isTestMode?: boolean): Promise<Plugin[]>;

package/dist/plugin.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"plugin.d.ts","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,SAAS,CAAC;AAuBtC;;;GAGG;AACH,wBAAsB,gBAAgB,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAiE3E;AAMD;;GAEG;AACH,wBAAgB,kBAAkB,CAAC,GAAG,EAAE,OAAO,GAAG,GAAG,IAAI,MAAM,CAkB9D;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,MAAM,EAAE,OAAO,GAAG;IAAE,OAAO,EAAE,OAAO,CAAC;IAAC,MAAM,EAAE,MAAM,EAAE,CAAA;CAAE,CAkDtF;AAMD;;GAEG;AACH,wBAAsB,oBAAoB,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CA2DrF;AAMD;;;;;;;GAOG;AACH,wBAAgB,mBAAmB,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CAO9D;AAMD;;;;;GAKG;AACH,wBAAgB,yBAAyB,CACvC,gBAAgB,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,EACrC,UAAU,GAAE,OAAe,GAC1B,MAAM,EAAE,CA8FV;AAMD;;;;GAIG;AACH,wBAAsB,UAAU,CAAC,YAAY,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CAatF;AA+FD;;;;;;;;;;GAUG;AACH,wBAAsB,cAAc,CAClC,OAAO,EAAE,CAAC,MAAM,GAAG,MAAM,CAAC,EAAE,EAC5B,UAAU,GAAE,OAAe,GAC1B,OAAO,CAAC,MAAM,EAAE,CAAC,CA0BnB"}

package/dist/prompts.d.ts

@@ -1,7 +0,0 @@
-export declare const shouldRespondTemplate = "<task>Decide on behalf of {{agentName}} whether they should respond to the message, ignore it or stop the conversation.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>Decide if {{agentName}} should respond to or interact with the conversation.\n\nIMPORTANT RULES FOR RESPONDING:\n- If YOUR name ({{agentName}}) is directly mentioned \u2192 RESPOND\n- If someone uses a DIFFERENT name (not {{agentName}}) \u2192 IGNORE (they're talking to someone else)\n- If you're actively participating in a conversation and the message continues that thread \u2192 RESPOND\n- If someone tells you to stop or be quiet \u2192 STOP\n- Otherwise \u2192 IGNORE\n\nThe key distinction is:\n- \"Talking TO {{agentName}}\" (your name mentioned, replies to you, continuing your conversation) \u2192 RESPOND\n- \"Talking ABOUT {{agentName}}\" or to someone else \u2192 IGNORE\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <name>{{agentName}}</name>\n  <reasoning>Your reasoning here</reasoning>\n  <action>RESPOND | IGNORE | STOP</action>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const messageHandlerTemplate = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n  - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n  - For task execution: REPLY,SEND_MESSAGE or REPLY,EVM_SWAP_TOKENS (acknowledge first, then do the task)\n  - For multi-step operations: REPLY,ACTION1,ACTION2 (acknowledge first, then complete all steps)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list  \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n\nFirst, think about what you want to do next and plan your actions. Then, write the next message and include the actions you plan to take.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n</keys>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response. \nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <actions>ACTION1,ACTION2</actions>\n    <providers>PROVIDER1,PROVIDER2</providers>\n    <text>Your response text here</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const postCreationTemplate = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{twitterUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n  <post>AI is changing the world and it is important to understand how it works</post>\n  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n  <thought>I am thinking about writing a post about dogs</thought>\n  <post>Dogs are man's best friend and they are loyal and loving</post>\n  <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n  <thought>Getting a job is hard, I bet there's a good tweet in that</thought>\n  <post>Just keep going!</post>\n  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n  <thought>Your thought here</thought>\n  <post>Your post text here</post>\n  <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response. \nGo directly to the XML response format without any preamble or explanation.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
-export declare const booleanFooter = "Respond with only a YES or a NO.";
-export declare const imageDescriptionTemplate = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response. \nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <title>A concise, descriptive title for the image</title>\n  <description>A brief 1-2 sentence summary of the key elements in the image</description>\n  <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const multiStepDecisionTemplate = "<task>\nDetermine the next step the assistant should take in this conversation to help the user reach their goal.\n</task>\n\n{{recentMessages}}\n\n# Multi-Step Workflow\n\nIn each step, decide:\n\n1. **Which providers (if any)** should be called to gather necessary data.\n2. **Which action (if any)** should be executed after providers return.\n3. **What parameters** the action requires (if any).\n4. Decide whether the task is complete. If so, set `isFinish: true`. Do not select the `REPLY` action; replies are handled separately after task completion.\n\nYou can select **multiple providers** and at most **one action** per step.\n\nIf the task is fully resolved and no further steps are needed, mark the step as `isFinish: true`.\n\n---\n\n{{actionsWithParams}}\n\n{{providersWithDescriptions}}\n\nThese are the actions or data provider calls that have already been used in this run. Use this to avoid redundancy and guide your next move.\n\n{{actionResults}}\n\n<keys>\n\"thought\" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.\n\"action\" Name of the action to execute after providers return. Omit or use empty string \"\" if isFinish: true or no action needed.\n\"parameters\" JSON object with exact parameter names and values for the action. Use empty object {} if no parameters are needed.\n\"providers\" List of provider names to call in this step (can be empty if none are needed).\n\"isFinish\" Set to true only if the task is fully complete.\n</keys>\n\n\u26A0\uFE0F IMPORTANT: Do **not** mark the task as `isFinish: true` immediately after calling an action. Wait for the action to complete before deciding the task is finished.\n\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <action>ACTION_NAME or \"\"</action>\n  <parameters>\n    {\n      \"param1\": \"value1\",\n      \"param2\": \"value2\"\n    }\n  </parameters>\n  <providers>PROVIDER1,PROVIDER2</providers>\n  <isFinish>true | false</isFinish>\n</response>\n</output>";
-export declare const multiStepSummaryTemplate = "<task>\nSummarize what the assistant has done so far and provide a final response to the user based on the completed steps.\n</task>\n\n# Context Information\n{{bio}}\n\n---\n\n{{system}}\n\n---\n\n{{messageDirections}}\n\n# Conversation Summary\nBelow is the user\u2019s original request and conversation so far:\n{{recentMessages}}\n\n# Execution Trace\nHere are the actions taken by the assistant to fulfill the request:\n{{actionResults}}\n\n# Assistant\u2019s Last Reasoning Step\n{{recentMessage}}\n\n# Instructions\n\n - Review the execution trace and last reasoning step carefully\n\n - Your final output MUST be in this XML format:\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <text>Your final message to the user</text>\n</response>\n</output>\n";

package/dist/prompts.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,o+HA2DzB,CAAC;AAEX,eAAO,MAAM,oBAAoB,wwFA4C+M,CAAC;AAEjP,eAAO,MAAM,aAAa,qCAAqC,CAAC;AAEhE,eAAO,MAAM,wBAAwB,y8CAuB3B,CAAC;AAEX,eAAO,MAAM,yBAAyB,2gEAoD5B,CAAC;AAEX,eAAO,MAAM,wBAAwB,4wBAqCpC,CAAC"}

package/dist/request-context.d.ts

@@ -1,142 +0,0 @@
-/**
- * Request context management for per-entity settings in multi-tenant deployments.
- *
- * Follows the OpenTelemetry ContextManager pattern (same as streaming-context.ts):
- * - Interface for context management
- * - Platform-specific implementations (Node.js AsyncLocalStorage, Browser Stack)
- * - Global singleton configured at startup
- *
- * This enables sharing a single agent runtime across multiple users while ensuring
- * each user's API keys, OAuth tokens, and configuration are used for their specific requests.
- *
- * @example
- * ```typescript
- * // Before processing a user's message
- * const entitySettings = await prefetchEntitySettings(userId, agentId);
- *
- * await runWithRequestContext({
- *   entityId: userId,
- *   agentId: agentId,
- *   entitySettings: new Map([
- *     ['OPENAI_API_KEY', 'sk-user-specific-key'],
- *     ['TWITTER_ACCESS_TOKEN', 'oauth-token-for-user'],
- *   ]),
- *   requestStartTime: Date.now(),
- * }, async () => {
- *   // All getSetting() calls here check entitySettings first
- *   await runtime.handleMessage(message);
- * });
- * ```
- */
-import type { UUID } from './types';
-/**
- * The value types that can be stored in entity settings.
- * Matches the return type of getSetting().
- */
-export type EntitySettingValue = string | boolean | number | null;
-/**
- * Request-scoped context containing per-entity settings.
- * Used to isolate user settings across concurrent requests sharing the same runtime.
- */
-export interface RequestContext {
-    /**
-     * The entity (user) ID for this request.
-     * Used to identify which user's settings should be used.
-     */
-    entityId: UUID;
-    /**
-     * The agent ID for this request.
-     * Used for agent-specific entity settings lookup.
-     */
-    agentId: UUID;
-    /**
-     * Pre-fetched entity-specific settings.
-     * These take highest priority in getSetting() resolution chain.
-     *
-     * The Map contains setting keys and their values:
-     * - string/boolean/number: The actual setting value to use
-     * - null: Explicitly unset (use agent default)
-     * - undefined (key not present): Fall through to agent settings
-     */
-    entitySettings: Map<string, EntitySettingValue>;
-    /**
-     * Request start timestamp for observability and debugging.
-     * Useful for tracking request duration and timeout handling.
-     */
-    requestStartTime: number;
-    /**
-     * Optional trace ID for distributed tracing.
-     * Can be passed from incoming request headers (e.g., X-Trace-Id).
-     */
-    traceId?: string;
-    /**
-     * Optional organization ID for multi-tenant deployments.
-     * Used for logging and auditing purposes.
-     */
-    organizationId?: string;
-}
-/**
- * Interface for request context managers.
- * Different implementations exist for Node.js (AsyncLocalStorage) and Browser (fallback).
- */
-export interface IRequestContextManager {
-    /**
-     * Run a function with a request context.
-     * The context will be available to all nested async calls via `active()`.
-     *
-     * @param context - The request context to make available, or undefined to clear context
-     * @param fn - The function to run within the context
-     * @returns The result of the function
-     */
-    run<T>(context: RequestContext | undefined, fn: () => T): T;
-    /**
-     * Get the currently active request context.
-     * Returns undefined if no context is active (e.g., during plugin init).
-     *
-     * @returns The current request context or undefined
-     */
-    active(): RequestContext | undefined;
-}
-/**
- * Set the global request context manager.
- * Called during initialization by platform-specific entry points.
- *
- * @param manager - The context manager to use globally
- */
-export declare function setRequestContextManager(manager: IRequestContextManager): void;
-/**
- * Get the global request context manager.
- * Useful for testing or advanced use cases.
- *
- * @returns The current global request context manager
- */
-export declare function getRequestContextManager(): IRequestContextManager;
-/**
- * Run a function with a request context.
- * All getSetting() calls within this function will check entitySettings first.
- *
- * @example
- * ```typescript
- * const result = await runWithRequestContext({
- *   entityId: userId as UUID,
- *   agentId: agentId as UUID,
- *   entitySettings: new Map([['API_KEY', 'user-specific-key']]),
- *   requestStartTime: Date.now(),
- * }, async () => {
- *   // Inside here, runtime.getSetting('API_KEY') returns 'user-specific-key'
- *   return await runtime.processMessage(message);
- * });
- * ```
- *
- * @param context - The request context with entitySettings
- * @param fn - The function to run with request context
- * @returns The result of the function
- */
-export declare function runWithRequestContext<T>(context: RequestContext | undefined, fn: () => T): T;
-/**
- * Get the currently active request context.
- * Called by getSetting() to check for entity-specific settings.
- *
- * @returns The current request context or undefined if not in a request
- */
-export declare function getRequestContext(): RequestContext | undefined;

package/dist/request-context.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"request-context.d.ts","sourceRoot":"","sources":["../src/request-context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,SAAS,CAAC;AAEpC;;;GAGG;AACH,MAAM,MAAM,kBAAkB,GAAG,MAAM,GAAG,OAAO,GAAG,MAAM,GAAG,IAAI,CAAC;AAElE;;;GAGG;AACH,MAAM,WAAW,cAAc;IAC7B;;;OAGG;IACH,QAAQ,EAAE,IAAI,CAAC;IAEf;;;OAGG;IACH,OAAO,EAAE,IAAI,CAAC;IAEd;;;;;;;;OAQG;IACH,cAAc,EAAE,GAAG,CAAC,MAAM,EAAE,kBAAkB,CAAC,CAAC;IAEhD;;;OAGG;IACH,gBAAgB,EAAE,MAAM,CAAC;IAEzB;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;;;GAGG;AACH,MAAM,WAAW,sBAAsB;IACrC;;;;;;;OAOG;IACH,GAAG,CAAC,CAAC,EAAE,OAAO,EAAE,cAAc,GAAG,SAAS,EAAE,EAAE,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC;IAE5D;;;;;OAKG;IACH,MAAM,IAAI,cAAc,GAAG,SAAS,CAAC;CACtC;AAoBD;;;;;GAKG;AACH,wBAAgB,wBAAwB,CAAC,OAAO,EAAE,sBAAsB,GAAG,IAAI,CAE9E;AAED;;;;;GAKG;AACH,wBAAgB,wBAAwB,IAAI,sBAAsB,CAEjE;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,qBAAqB,CAAC,CAAC,EAAE,OAAO,EAAE,cAAc,GAAG,SAAS,EAAE,EAAE,EAAE,MAAM,CAAC,GAAG,CAAC,CAE5F;AAED;;;;;GAKG;AACH,wBAAgB,iBAAiB,IAAI,cAAc,GAAG,SAAS,CAE9D"}

package/dist/request-context.node.d.ts

@@ -1,36 +0,0 @@
-import type { RequestContext, IRequestContextManager } from './request-context';
-/**
- * AsyncLocalStorage-based context manager for Node.js.
- * Provides proper async context isolation across parallel async operations.
- *
- * When User A and User B send messages concurrently:
- * - User A's async chain sees User A's entitySettings
- * - User B's async chain sees User B's entitySettings
- * - No race conditions or cross-contamination
- */
-export declare class AsyncLocalStorageRequestContextManager implements IRequestContextManager {
-    private storage;
-    /**
-     * Run a function with a request context.
-     * The context is automatically propagated through all async operations.
-     *
-     * @param context - The request context to use, or undefined to clear
-     * @param fn - The function to execute within the context
-     * @returns The result of the function
-     */
-    run<T>(context: RequestContext | undefined, fn: () => T): T;
-    /**
-     * Get the currently active request context.
-     * Returns the context that was passed to the enclosing run() call.
-     *
-     * @returns The current request context or undefined if outside a run() scope
-     */
-    active(): RequestContext | undefined;
-}
-/**
- * Create and return a configured AsyncLocalStorage context manager.
- * Called by index.node.ts during initialization.
- *
- * @returns A new AsyncLocalStorageRequestContextManager instance
- */
-export declare function createNodeRequestContextManager(): IRequestContextManager;

package/dist/request-context.node.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"request-context.node.d.ts","sourceRoot":"","sources":["../src/request-context.node.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,cAAc,EAAE,sBAAsB,EAAE,MAAM,mBAAmB,CAAC;AAEhF;;;;;;;;GAQG;AACH,qBAAa,sCAAuC,YAAW,sBAAsB;IACnF,OAAO,CAAC,OAAO,CAAuD;IAEtE;;;;;;;OAOG;IACH,GAAG,CAAC,CAAC,EAAE,OAAO,EAAE,cAAc,GAAG,SAAS,EAAE,EAAE,EAAE,MAAM,CAAC,GAAG,CAAC;IAI3D;;;;;OAKG;IACH,MAAM,IAAI,cAAc,GAAG,SAAS;CAGrC;AAED;;;;;GAKG;AACH,wBAAgB,+BAA+B,IAAI,sBAAsB,CAExE"}

package/dist/roles.d.ts

@@ -1,23 +0,0 @@
-import { type IAgentRuntime, Role, type World } from './types';
-/**
- * Interface representing the ownership state of servers.
- * @property {Object.<string, World>} servers - The servers and their corresponding worlds, where the key is the server ID and the value is the World object.
- */
-export interface ServerOwnershipState {
-    servers: {
-        [serverId: string]: World;
-    };
-}
-/**
- * Retrieve the server role of a specified user entity within a given server.
- *
- * @param {IAgentRuntime} runtime - The runtime object containing necessary configurations and services.
- * @param {string} entityId - The unique identifier of the user entity.
- * @param {string} serverId - The unique identifier of the server.
- * @returns {Promise<Role>} The role of the user entity within the server, resolved as a Promise.
- */
-export declare function getUserServerRole(runtime: IAgentRuntime, entityId: string, serverId: string): Promise<Role>;
-/**
- * Finds a server where the given user is the owner
- */
-export declare function findWorldsForOwner(runtime: IAgentRuntime, entityId: string): Promise<World[] | null>;

package/dist/roles.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"roles.d.ts","sourceRoot":"","sources":["../src/roles.ts"],"names":[],"mappings":"AAKA,OAAO,EAAE,KAAK,aAAa,EAAE,IAAI,EAAE,KAAK,KAAK,EAAa,MAAM,SAAS,CAAC;AAE1E;;;GAGG;AACH,MAAM,WAAW,oBAAoB;IACnC,OAAO,EAAE;QACP,CAAC,QAAQ,EAAE,MAAM,GAAG,KAAK,CAAC;KAC3B,CAAC;CACH;AAED;;;;;;;GAOG;AACH,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,aAAa,EACtB,QAAQ,EAAE,MAAM,EAChB,QAAQ,EAAE,MAAM,GACf,OAAO,CAAC,IAAI,CAAC,CAaf;AAED;;GAEG;AACH,wBAAsB,kBAAkB,CACtC,OAAO,EAAE,aAAa,EACtB,QAAQ,EAAE,MAAM,GACf,OAAO,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,CA0BzB"}