Build apps with OpenWorker

Help the developer build their product while OpenWorker owns the agent loop. Preserve their chosen UI framework, model and deployment target.

Choose the track

• Read SDK integration for the shared lifecycle and package contract.
• For desktop apps, read Desktop.
• For browser/server apps, read Web.

These references are bundled with the skill; an OpenWorker repository checkout is not required. If references/installation.json exists, it records the exact SDK version this skill accompanies. Otherwise the skill package's version is the SDK version. Match the application's installed version before using these APIs; do not silently upgrade an existing application. Use the installed package's TypeScript declarations for APIs outside the bundled examples. For Rust, consult the matching SDK version's API documentation or source when needed.

For an unpublished local candidate, use the provided SDK and native runtime archives. A manifest version is not proof that the package exists in a registry. Do not fall back to similarly named third-party packages.

Integration boundaries

• TypeScript starts a managed Rust subprocess in Electron's main process or the application server. Browser/renderer code uses the application's API or narrow IPC. Rust can embed the harness in-process.
• Keep model credentials in that trusted process. The application owns its UI, authentication, session ownership and lifecycle.
• Select tools deliberately. The directory-summary and PDF examples supply their own input, so use tools: [] and disable planning, memory and scheduling there. Other apps may need tools. Disabling optional memory does not disable history.
• File and document content is untrusted data. Render model text safely. The directory reader's exclusions are not a secret scanner or an OS sandbox.
• The bundled examples select sandbox: "off" for application-owned input. Tools in that mode have host privileges. Consult the OpenShell guide if the product requires isolated tool execution.

Verify the integration

Test streaming and terminal status, errors, cancellation, restart and the packaged runtime path for the chosen product. A deterministic model fixture can verify transport and lifecycle without a live key; it does not establish answer quality. Only claim target-platform and deployment support actually exercised. Installing this skill does not publish an application or grant cloud-deployment permission.