Skip to content
OpenPond
Join community
Desktop/Use OpenPond Desktop

Use OpenPond Desktop

Keep local projects, reviewable work, and improvement evidence in one workbench.

OpenPond Desktop is the local-first interface for working beside a project with conversations, files, terminals, browsers, approvals, and reviewable outputs. It uses the same source-owned runtime as OpenPond Web, CLI, and TUI.

What Desktop is for

Use Desktop when local project context matters and you want to connect useful work to a later Taskset, Evaluation, or model-training decision.

  1. Open or choose a local project.
  2. Use Chat for bounded questions or Work for a multi-step result.
  3. Inspect outputs, changes, and receipts before promoting evidence.
  4. Create a Taskset or start an evaluation only through the explicit product gates.

Desktop can use isolated cloud sandboxes when the task needs managed compute. The sandbox remains a distinct execution environment with its own lifecycle, budget, and cleanup boundary.

Download the current Desktop release from GitHub Releases, choose the installer for your operating system, and follow its installation flow. Open the app, choose a project folder, and configure the model and connections needed for your first task. Do not collect or share diagnostics that contain credentials, private project source, or personal conversation content.

Next: Understand the open-source Harness.

Configuration and recovery

Desktop, CLI, and TUI share an OpenPond home. Stable uses ~/.openpond; nightly uses ~/.openpond-nightly. An explicit OPENPOND_HOME or --home selects another location. Development Desktop normally uses ~/.openpond/openpond-app-dev. Reuse the running app’s home when working with its account from the CLI; an empty default CLI home does not mean Desktop has lost its session.

When a model, tool, or connection fails, inspect its current status and the retained task evidence before retrying. Keep the project and task context intact. Use the app’s recovery controls and support for diagnostic collection; remove credentials and unrelated private content from anything shared.

Terminal and contribution paths

Use CLI and TUI for terminal work and Use with your coding agent for supported external setup. Customer workflow Skills are bundled with Desktop; they do not need to be installed a second time. Their availability does not authorize a paid workload or an external write.

For source development, follow Contributing. Package names remain openpond, openpond-sdk, openpond-agent-sdk, @openpond/evals, and @openpond/harness.

Choose your entry point

Use Desktop for local project work, CLI and TUI for terminal workflows, or the Harness package when building your own host. Each surface keeps its own execution and permission boundary.

How-tos

Follow the Desktop setup walkthrough for your first project, Chat and Work for choosing the task mode, and Desktop training when reviewed work is ready for a separate training decision.

Follow the first Desktop task tutorial to connect setup, a bounded task and result inspection.

View as Markdown