Platform

Protected Workspaces

How SeaSnoke keeps generated work separated from production.

Edit this page

Separation

SeaSnoke keeps generated work separated from production systems. Agent changes are prepared in controlled workspaces and must pass review before they can be merged.

Access Controls

Use repository permissions, workspace settings, and CI checks to decide what agents can access and what must be reviewed by a human.

repositories:
  default_branch: main
  require_review: true
checks:
  test: required
  lint: required
  security: optional

On this page