PR Summary

Medium Risk
Introduces a new Dagster GraphQL integration with 14 callable operations and new UI block wiring; main risk is runtime/schema mismatch or parameter coercion issues causing tool execution failures, but changes are isolated to the new integration and registries.

Overview
Adds a new Dagster integration end-to-end: a DagsterBlock with an operation dropdown, conditional inputs, param remapping/coercion, and outputs for run execution, log retrieval, run lifecycle actions, and schedule/sensor management.

Implements and registers 14 Dagster GraphQL tools (launch/get/list runs & jobs, get logs, reexecute/terminate/delete runs, list/start/stop schedules and sensors) under apps/sim/tools/dagster, including shared GraphQL response parsing/error helpers.

Updates product surfaces to expose Dagster: new DagsterIcon in both docs and app icon maps, a new integrations catalog entry, and new docs page tools/dagster; also expands the internal add-tools skill doc to require block wiring after tool registration.

^{Reviewed by Cursor Bugbot for commit 7e26b13. Configure here.}

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 7, 2026 6:18pm

Greptile Summary

This PR expands the Dagster integration from 5 to 14 tools, adding full coverage of the run lifecycle (delete_run, get_run_logs, reexecute_run), schedule management (list_schedules, start_schedule, stop_schedule), and sensor management (list_sensors, start_sensor, stop_sensor). It also hardens all existing tools by replacing abstract ... on Error catch-all fragments with concrete union member fragments per the Dagster GraphQL schema.

• 9 new tools added: delete_run, get_run_logs, reexecute_run, list_schedules, start_schedule, stop_schedule, list_sensors, start_sensor, stop_sensor
• GraphQL union handling fixed across all tools — TerminateRunFailure, InvalidStepError, InvalidOutputError, RunConfigValidationInvalid, RunNotFoundError, and others now use concrete type fragments instead of the abstract ... on Error pattern
• Block wiring updated with condition-based show/hide for all 14 operations, correct params remapping (listRunsJobName→jobName, logsLimit→limit, runId→parentRunId for reexecute), and wandConfig for AI-assisted fields (run config JSON, tags, status filters)
• graphql.ts renamed to utils.ts with two well-typed helpers (parseDagsterGraphqlResponse, dagsterUnionErrorMessage) shared by all tools
• All three issues raised in prior review threads (abstract error fragments, nullable $id on stopSensor, RepositoryNotFoundError union membership) were addressed in follow-up commits

Confidence Score: 5/5

Safe to merge — no correctness bugs found; all three prior review concerns have been resolved in follow-up commits

All 14 tools follow consistent patterns with correct GraphQL union type handling, accurate block param remapping, and proper type safety throughout. The three issues raised in previous review rounds (abstract error fragments, nullable $id intent, RepositoryNotFoundError SDL membership) were each verified and resolved. No P0 or P1 issues remain.

No files require special attention; dagster.ts block config is intentionally complex to wire 14 operations but is correctly implemented

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant U as User
    participant SB as Dagster Block
    participant TC as Tool Config
    participant EX as Executor
    participant DA as Dagster GraphQL API
    participant RT as transformResponse

    U->>SB: Select operation (e.g. launch_run)<br/>Fill params (host, jobName, etc.)
    SB->>TC: config.tool(params) → "dagster_launch_run"
    SB->>TC: config.params(params) → coerce + remap fields
    EX->>DA: POST {host}/graphql<br/>Dagster-Cloud-Api-Token header<br/>Dynamic mutation/query + variables

    alt Success
        DA-->>EX: 200 { data: { launchRun: { __typename: "LaunchRunSuccess", run: { runId } } } }
        EX->>RT: parseDagsterGraphqlResponse → check HTTP ok + errors[]
        RT-->>SB: { success: true, output: { runId } }
        SB-->>U: runId output
    else Concrete union error (e.g. RunConfigValidationInvalid)
        DA-->>EX: 200 { data: { launchRun: { __typename: "RunConfigValidationInvalid", errors: [...] } } }
        EX->>RT: parseDagsterGraphqlResponse → no top-level errors, proceeds
        RT->>RT: concrete type check → throw RunConfigValidationInvalid: ...
        RT-->>SB: Error thrown
        SB-->>U: Typed error message
    else HTTP / transport failure
        DA-->>EX: 4xx/5xx or invalid JSON
        EX->>RT: response.ok === false → throw from parseDagsterGraphqlResponse
        RT-->>SB: HTTP error
        SB-->>U: Transport error
    end

_{Reviews (4): Last reviewed commit: "fix(dagster): always override jobName in..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review