Deployment composition and local migration
Use createLiteAgent() for computers, NAS deployments, local models and remote models. The @lite-agent/local package and its createLocalAgent / LocalAgent interfaces have been removed without compatibility aliases. query() delegates to the same constructor; Core's createAgent() remains a low-level kernel factory.
Local models
Endpoint presets now live in @lite-agent/provider 0.10.0:
Omit codec for models supporting native tool calls. localOpenAI provides loopback HTTP(S) presets for Ollama, vLLM, LM Studio and llama.cpp and returns a standard ModelProvider. Construction neither creates an agent nor probes the endpoint. A loopback URL does not prove offline isolation. Use openai() / anthropic() for remote services.
contextWindow feeds the standard provider context capability and shared SDK ContextEngine. The old nativeTools, tokenEstimator, probeTimeoutMs, .local metadata and markLocalProvider are removed. Implement ModelProvider directly for custom providers. Tokenizing JSON-serialized messages is no longer described as an exact count of the full model request.
Compose persistence, sandbox and permissions
Hosts own externally supplied databases and sandboxes. Initialize them explicitly and close them after the agent stops, including failed-construction paths:
This is explicit composition, not an implicit replacement for the former strict preset. Configure permissions, sandbox requirements, MCP transports, snapshots, background limits and audit deliberately. Sandboxes without requireSandbox: true may still degrade; createLiteAgent() does not require an OS sandbox by default.
resourceLimitedSandbox, probeResourceLimits, DEFAULT_RESOURCE_LIMITS and ResourceLimits moved to @lite-agent/sandbox-anthropic 0.9.0. The wrapper initializes before execution and stops if a limit cannot be set. CPU limits are process CPU time; ulimit -u has OS/user-specific semantics, not per-agent job quotas. Linux uses ulimit -v for virtual address space; macOS has no equivalent hard memory limit here. Configure SDK bash.memoryBytes separately for Bash RSS monitoring. These controls are not model/GPU or whole-runtime budgets.
Migration map
Offline and extension boundaries
Loopback classification and Tool.security are declarations, not isolation guarantees. Arbitrary custom providers, JavaScript tools and programmatic hooks are trusted host code. Command sandboxes cannot constrain those functions. Fully offline deployments must also constrain the model service and host process network.
Community implementations can already target provider, checkpointer, sandbox, permission and middleware interfaces. This migration does not add a plugin loader, privacy redaction or outbound model filtering. Local execution and log redaction must not be described as remote-model data protection.