Projects

A Project is durable repository and workspace identity. It can provide source, environments, and Agent association across work, but it is not itself a running sandbox or a permission to execute commands.

Projects work especially well with the open-source OpenPond repository: keep the source you want to review in Git, then connect that repository as the Project's durable source boundary.

Create a project

Open Sandboxes → Projects in OpenPond, then select Create project. Choose one starting point:

• Import source connects an approved GitHub installation or accepts a source path, then lets you select the repository and branch.
• Empty project creates a clean Cloud project for code you will add later. Name it, choose its environment and sandbox defaults, then finish creation.

After creation, open the Project and use its Files workspace to add or edit code. For a web application, add the application files, install its dependencies in a Sandbox, start the development server, and expose a preview only when you need one. Keep the Project as the durable source boundary; start or stop Sandboxes independently for the actual compute lifecycle.

Bring an existing app into a Project

Use Import source for an existing repository. Select the connected GitHub account, choose the repository, confirm the branch, then complete the environment and sandbox setup. The repository becomes the Project's source identity, so later Work and Agent activity stays tied to the same codebase.

Use Empty project when you want to start from a blank workspace. Create the Project first, add the application files in Files, then use a Sandbox to run installs, tests, and a preview. Do not put credentials directly in source; add them through the Project's environment-secret controls instead.

Use a Project to retain the context that makes future Work tasks reviewable. When a task needs compute, choose Work or a Sandbox explicitly and keep its lifecycle, files, budget, and cleanup separate from the Project record.

Next: Workflows.