/** * Compute providers: where an agent's tools run. * * praisonai-ts had none, so `toolsRunOn` had nothing to select. Two real * providers ship here -- local and Docker -- and the registry is open, so a * remote provider (E2B, Modal, Daytona) can be added without touching callers. * * Python parity: `praisonai_sandbox.compute`. */ import { type ComputeProvider } from './types'; export * from './types'; export { LocalCompute } from './local'; export { DockerCompute } from './docker'; export { ComputeToolPlace, registerComputeToolPlaces } from './tool-place'; type Factory = () => ComputeProvider; /** * Add a provider. Lets a remote one be supplied without changing this file. * * The name is ALSO registered as a `toolsRunOn` place, so a caller who * registers 'e2b' can immediately write `new Agent({ toolsRunOn: 'e2b' })`. * Without this bridge the two registries drift: the provider exists here but * `resolvePlacement` validates against a separate place registry and still * rejects the name as "not a known place". */ export declare function registerComputeProvider(name: string, factory: Factory): void; /** Provider names available in this build. */ export declare function listComputeProviders(): string[]; /** * Resolve a `toolsRunOn`-style value to a provider. * * An unknown name RAISES and lists what exists. Falling back to local would run * on the host something the caller asked to run in a sandbox -- the silent * wrongness this package has repeatedly been bitten by, and here it would be a * security property rather than an inconvenience. */ export declare function resolveComputeProvider(target: string | ComputeProvider | undefined | null): ComputeProvider | null;