Start a Workspace

Create a task, start a DevBox workspace, and review the generated result.

Prerequisites

Before starting a workspace, ensure you have the following:

• Access to https://app.seasnoke.com.
• The SeaSnoke GitHub App installed for the account or organization that owns the repository.
• A connected project with at least one repository.
• Repository setup instructions or checks that an agent can discover.

Connect Repositories

Use the project connection flow to install or refresh the GitHub App, then select repositories for the project. A project can include multiple repositories when the product change spans more than one codebase.

SeaSnoke creates exactly the workspace checkouts needed for the task. Users should not need to think in terms of local git worktrees.

Configuration

Project and workspace configuration describe how the DevBox should prepare and validate the codebase.

[project]
name = "acme-corp"
repos = ["github.com/acme/api", "github.com/acme/web"]

[environment]
setup = "auto"
snapshot = true
services = ["postgres", "redis"]

[checks]
test_runner = "auto"
coverage_threshold = 80
lint_on_completion = true
security_scan = true

[review]
require_human_approval = true

Verify Setup

Use the environment panel to confirm the workspace is ready:

• GitHub App installation is connected.
• Repositories are synced.
• Environment setup is ready or queued.
• Required secrets and environment variables are configured.
• The expected checks are detected.

First Workspace

Start with a narrow task to verify the workflow:

Add tests for the billing date parser.

Requirements:
- Cover valid monthly billing dates.
- Cover invalid date input.
- Run the existing parser tests.

SeaSnoke creates a workspace, prepares the DevBox, starts the agent thread, and keeps logs, messages, diffs, and checks attached to that workspace.

Next Steps

• Review generated changes in the workspace source-control panel.
• Retry failed workers with an additional message when the failure is recoverable.
• Configure environment variables for projects that need secrets or service credentials.
• Open a pull request only after the verifier and human review agree the change is ready.