Automation Cockpit 2.0 — a workspace where code, data and automation sit together

The rewrite that made Cockpit a workspace rather than an editor with scripts bolted on.

1.x was an editor that could run things. The distinction sounds academic until you try to hold a codebase, the data it produces and the jobs that move that data in one head at the same time, and find yourself in three applications.

2.0 puts them in one workspace. Code, the datasets a job produced, and the job definitions themselves are all first-class and all addressable from each other — a dataset knows which job wrote it, a job knows which files it depends on.

The AI layer sits across all three rather than only over the editor, which is what later made whole-project review possible.

In this release

• Unified workspace: code, datasets and jobs in one place.
• Datasets carry their provenance — which job wrote them, and when.
• AI assistance across the whole workspace, not just the editor.
• Project settings move into a versionable file you can commit.

The product

• Automation Cockpit — read the case