Use One Works in Your Project

This documentation is the user-facing entry point for integrating One Works into your own project.

Product Demo

This 21-second demo uses real desktop windows to open a workspace from the Launcher and select an AI adapter. The video follows the docs site's light or dark appearance; for a static preview, see the theme-aware image on the Desktop App page.

Start Here

• Install and Prepare
• Avatar Editor and Developer Integration
• Data Asset Directories
• Start Services
• Adapter CLI Installation and Versions
• Desktop App
• VS Code Extension
• Web UI and Terminal View
• Adapter Configuration and Multiple Accounts
• DeepSeek Harness (DSH) Adapter
• Cline CLI Adapter
• Factory Droid CLI Adapter
• Pi coding-agent Adapter
• Grok Build CLI Adapter
• Goose CLI Adapter
• Kiro CLI Adapter
• JetBrains Junie CLI Adapter
• Qwen Code CLI Adapter
• Token Usage
• PWA and Standalone Deployment
• Relay Hosting, Login, and Identity Model
• Diagnostics, Telemetry, and Support Bundles
• Channel Session Binding
• Channel Platform Integrations
• CLI and Examples
• Examples Directory
• Skills and Dependencies
• Workspace Scheduling
• Plugins, UI Extensions, and Data Assets
• Adapter Native Plugins and Marketplaces

Official Links

• Website: oneworks.cloud
• Docs: oneworks.cloud/docs
• GitHub: oneworks-ai/app
• Privacy: OneWorks Privacy Policy
• Support: support@oneworks.cloud

Integration Goals

• You do not need to clone this repository. Install only the packages you need.
• Configuration and sessions are scoped to your project directory, not to the One Works repository.
• The UI, CLI, MCP server, hooks runtime, adapters, plugins, and skills can be integrated independently.
• The Web UI session page includes a standalone terminal view, but terminal runtimes and chat message streams are separate execution paths.