import * as React from 'react';
/**
 * Names the plugin that owns the subtree, and carries its configuration. Every
 * capability host wraps what it renders from the registry in one of these, which is
 * how the SDK hooks are scoped without a plugin passing its own id around.
 * `pluginId` comes from the registry entry, never from the plugin.
 *
 * Holds no reference to the host or `installed.ts`: plugin components import from
 * here and `installed.ts` imports plugin components, so reaching back would make the
 * module graph a cycle and leave the bindings undefined at render time.
 */
export declare function PluginScopeProvider({ pluginId, config, children, }: {
    pluginId: string;
    config?: Record<string, unknown>;
    children: React.ReactNode;
}): React.JSX.Element;
/** The owning plugin's id. Throws outside a plugin subtree: a shared fallback would mix plugins' data. */
export declare function usePluginId(): string;
/** The org's config for this plugin, layered with per-user overrides. Shaped by the manifest's `configSchema`. */
export declare function usePluginConfig<T extends Record<string, unknown> = Record<string, unknown>>(): T;
//# sourceMappingURL=scope.d.ts.map