Registry / workflow / dagit
library1.13.9pypypiunverified

Dagit is the web-based user interface for Dagster, providing observability, operational control, and debugging capabilities for data pipelines. It allows users to visualize assets, jobs, runs, schedules, and sensors defined within a Dagster project. Dagit's versioning is tightly coupled with the core Dagster library, typically released in sync with major and minor Dagster updates.

pip install dagit
INSTALL
IMPORT
SIG · DAGIT
D
dagit
workflowpythonv1.13.9
Install
16.6s avg
Import
Disk
205MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v1.13.9 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.920 runs
installs and imports cleanly · install 0.0s · import 0.000s · 199.4MB
glibc
py 3.103.920 runs
installs and imports cleanly · install 16.6s · import 0.000s · 198MB
205MB installed
● package 205MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

N/A
dagit is a CLI tool, not a Python library for direct import.
The `dagit` package primarily provides the `dagit` command-line executable, which launches the Dagster UI. Users typically run `dagit` from the terminal rather than importing symbols from it in Python code.

To start Dagit, first define some Dagster assets or jobs in a Python file (e.g., `my_repo.py`). Then, launch Dagit from your terminal, pointing it to your definitions file. This will open the Dagster UI in your browser.

from dagster import asset, Definitions, job @asset def hello_asset(): return "Hello, Dagster World!" @job def my_simple_job(): hello_asset() defs = Definitions(assets=[hello_asset], jobs=[my_simple_job]) # Save this as `my_repo.py` then run `dagit -f my_repo.py` in your terminal.
dagit --version
Debug
Known issues
breakingDagit (and the underlying `dagster-webserver` package) versions must closely match the `dagster` core library version. Mismatched versions (e.g., `dagster==1.12.0` and `dagit==1.13.0`) can lead to runtime errors or unexpected UI behavior.
fix
Always install `dagit` and `dagster` with matching major and minor versions (e.g., `pip install 'dagster==1.13.*' 'dagit==1.13.*'`).
affects: All versions
gotchaDagit is primarily a CLI executable (`dagit`) used to launch the Dagster UI. It is not designed to be imported as a Python module within user-defined Dagster code (e.g., `import dagit`).
fix
Interact with Dagit via the command line. Define your Dagster assets, ops, and jobs using the `dagster` library, and then use `dagit -f path/to/your_definitions.py` to view them in the UI.
affects: All versions
breakingSince `dagster` version 1.12.18, `psycopg2-binary` is no longer a transitive dependency of `dagster-postgres`. If your Dagster project utilizes `dagster-postgres` and relies on `psycopg2-binary`, you must explicitly install it.
fix
If you use `dagster-postgres`, explicitly add `pip install psycopg2-binary` to your project's dependencies.
affects: >=1.12.18
gotchaRunning `dagit` without specifying any Dagster definitions (e.g., via `-f`, `-m`, or a `workspace.yaml` file) will result in an empty UI. Dagit needs to know where to find your code.
fix
Always provide a target for Dagit to load definitions from. For local development, use `dagit -f your_definitions.py` or `dagit -m your_package`.
affects: All versions
Upgrade
Version history
1.13.9latest on PyPI · released Jun 11, 2026
Audit
Dependencies
dagster-webserverrequiredProvides the core web server and Dagit executable functionality.
dagsterrequiredProvides the core Dagster framework for defining assets and operations, which Dagit visualizes.
Agent activity
27 hits · last 30 days
node
24
OpenAI (training)
1
Resources
dagit — pip install dagit · libregistry