Airbyte introduces agentic execution flow using Crabbox sandboxing for ETL workflows

Airbyte has introduced an agentic execution architecture where an AI harness reads a goal, writes a bounded spec, and orchestrates data movement through sandboxed workers via Crabbox (a credential and environment isolation layer).

The system separates concerns into four contracts: Goal becomes Spec (refs, profile, retry policy, validation); Spec becomes Run (sandboxed command with durable run id); Profile becomes Env (scoped variables in worker only); Execution becomes Evidence (logs, JUnit, metrics, redacted config). The prompt never touches the data plane—Airbyte connectors move rows directly.

Evidence signals (finish, retry, repair, or alert) feed back into the loop, allowing the agent to replay failures or repair from the same boundary without re-examining the full execution history.