# sxyazi/yazi architecture

> Architecture diagram of the GitHub repository sxyazi/yazi, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-18). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/sxyazi/yazi
- Repository: https://github.com/sxyazi/yazi

## Overview

1. This is a Rust monorepo for **Yazi**, a terminal file manager. The architecture is split into many small crates, with a clear separation between:
   - the interactive TUI application,
   - the core domain/state layer,
   - async task execution,
   - filesystem and virtual filesystem access,
   - plugin/Lua runtime support,
   - terminal/image rendering adapters,
   - and packaging/build tooling.

2. The **main executable** is `yazi-fm`. It is the user-facing terminal app and acts as the composition root: it wires together input handling, routing/dispatch, rendering, notifications, task progress, and the manager/selection/preview views. The repo also includes `yazi-cli` for auxiliary commands and `yazi-boot` for startup/diagnostic actions, but `yazi-fm` is the center of runtime behavior.

3. The **core application model** lives in `yazi-core`. This crate holds the long-lived state and business logic for tabs, directory navigation, search/filtering, open actions, preview state, tasks, notifications, and “which/confirm/help/input” modal flows. It is the main boundary between UI events and domain operations: the TUI dispatches actions into core, and core emits updated state and side effects.

4. The **filesystem layer** is split across `yazi-fs`, `yazi-vfs`, and `yazi-sftp`.
   - `yazi-fs` provides local path, metadata, sorting, mount, and provider abstractions.
   - `yazi-vfs` generalizes filesystem access and adds remote/provider support, including SFTP-backed operations.
   - `yazi-sftp` implements the SFTP protocol itself.
   This separation lets the rest of the app treat local and remote files through similar interfaces while keeping protocol-specific logic isolated.

5. The **async task pipeline** is handled by `yazi-scheduler` and `yazi-runner`.
   - `yazi-scheduler` coordinates jobs, progress, cancellation, transactions, and worker orchestration across file operations, processes, preloads, plugins, fetches, and sizing work.
   - `yazi-runner` executes plugin-side jobs such as loaders, fetchers, previewers, and preloader tasks.
   In diagram terms, these crates sit between core state and actual I/O/process work, absorbing concurrency and progress reporting.

6. The **event/action translation layer** is unusually explicit. There are generated or decomposed action crates such as `yazi-parser`, `yazi-actor`, and `yazi-proxy`.
   - `yazi-parser` parses incoming action names/events into typed operations.
   - `yazi-actor` groups action handlers by UI mode and domain area.
   - `yazi-proxy` provides dispatch proxies for app submodules.
   This suggests the app uses an internal action bus rather than tightly coupling UI events to state mutations.

7. The **plugin and Lua subsystem** is a major architectural boundary. `yazi-plugin` contains Lua presets and runtime support for UI plugins, previewers, spotters, fetchers, and other extension points. `yazi-binding` exposes Rust-side bindings and configuration models to Lua, while `yazi-runner` and `yazi-scheduler` execute plugin-related work. The plugin layer is how Yazi customizes UI rendering, previews, content detection, and user commands without embedding all logic in the Rust app.

8. The **data distribution service (DDS)** is implemented with `yazi-dds`. It provides a client/server pub-sub mechanism for cross-instance communication and state persistence, but it is embedded in the application model rather than requiring an external daemon. This subsystem is important for diagramming because it is a separate communication plane from the normal file-manager UI flow.

9. The **UI/runtime support stack** is layered:
   - `yazi-widgets` contains reusable input and scrolling widgets.
   - `yazi-term` and `yazi-tty` abstract terminal/TTY behavior.
   - `yazi-emulator` models terminal capabilities/dimensions.
   - `yazi-adapter` renders images through terminal-specific backends such as Kitty graphics, IIP, Sixel, Überzug++, or Chafa fallback.
   This layer is responsible for presentation, terminal feature detection, and image preview output, while the app logic remains elsewhere.

10. The **configuration and schema layer** is centralized in `yazi-config`. It defines TOML-based presets for keymaps, theme, layout, open rules, previewers, fetchers, spotters, VFS settings, popup behavior, and platform-specific options. This crate is the main configuration boundary, translating user config into strongly typed runtime structures used by the app, plugins, and filesystem tooling.

11. The **shared foundation crates** provide reusable primitives across the whole repo:
   - `yazi-shared` contains string/path/url/scheme/event/pool/time utilities and common data types.
   - `yazi-shim` wraps third-party crates to stabilize APIs.
   - `yazi-binding` provides rich domain types for files, handles, runtime, theme, input, and config.
   These are infrastructure crates rather than features; they keep higher-level crates focused on behavior.

12. The **platform and FFI surface** is isolated in `yazi-ffi` and parts of `yazi-shared`/`yazi-emulator`. `yazi-ffi` contains macOS-specific system integrations such as disk arbitration and IOKit. This indicates the repo supports platform-native filesystem/media integration while maintaining a cross-platform core.

13. The **build and packaging/tooling layer** is also substantial:
   - `yazi-build`, `yazi-boot`, `yazi-codegen`, and `yazi-macro` support code generation, build-time actions, and macro expansion.
   - `scripts`, `flake.nix`, `snap`, and GitHub workflows handle release, validation, icon generation, packaging, and CI.
   These do not affect runtime flows directly, but they are important boundaries for how the monorepo is assembled and distributed.

14. The main runtime data flow is: **terminal input → TUI/router/dispatcher → core app state → scheduler/runner for async work → filesystem/VFS/plugin/DDS backends → updated state/progress/notifications → render back to terminal**. Image previews and remote operations branch out through dedicated adapters/providers, but they rejoin the same core state and task progress pipeline.

Main entry points: [`yazi-core`](https://github.com/sxyazi/yazi/tree/main/yazi-core) (yazi-core), [`yazi-fm`](https://github.com/sxyazi/yazi/tree/main/yazi-fm) (yazi-fm), [`yazi-plugin`](https://github.com/sxyazi/yazi/tree/main/yazi-plugin) (yazi-plugin), [`yazi-scheduler`](https://github.com/sxyazi/yazi/tree/main/yazi-scheduler) (yazi-scheduler)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_runtime["Runtime"]
  node_yazi_fm["yazi-fm<br/>tui app"]
  node_dispatcher(("Dispatcher<br/>action router<br/>[dispatcher.rs]"))
  node_router(("Router<br/>[router.rs]"))
  node_executor(("Executor<br/>runtime glue<br/>[executor.rs]"))
end

subgraph group_core["Core state"]
  node_yazi_core["yazi-core<br/>domain state"]
  node_core_mgr(("Manager<br/>[mgr.rs]"))
  node_core_tab(("Tab state<br/>tab model<br/>[tab.rs]"))
  node_core_tasks(("Task state<br/>task model<br/>[tasks.rs]"))
  node_core_notify(("Notify<br/>notification model<br/>[notify.rs]"))
  node_core_proxy(("Proxy<br/>action bridge<br/>[proxy.rs]"))
end

subgraph group_io["Filesystem"]
  node_yazi_sched["yazi-scheduler<br/>job scheduler"]
  node_yazi_vfs["yazi-vfs<br/>virtual fs"]
  node_yazi_fs["yazi-fs<br/>local fs"]
  node_yazi_sftp["yazi-sftp<br/>sftp protocol"]
end

subgraph group_plugin["Plugins"]
  node_yazi_runner["yazi-runner<br/>plugin runner"]
  node_yazi_plugin["yazi-plugin<br/>lua plugin"]
  node_yazi_binding["yazi-binding<br/>ffi types"]
end

subgraph group_support["Support"]
  node_yazi_dds["yazi-dds<br/>pub-sub bus"]
  node_yazi_config["yazi-config<br/>config schema"]
  node_yazi_widgets["yazi-widgets<br/>ui widgets"]
  node_yazi_term(("yazi-term<br/>terminal"))
  node_yazi_tty(("yazi-tty"))
  node_yazi_emulator(("yazi-emulator<br/>terminal model"))
  node_yazi_adapter(("yazi-adapter<br/>image render"))
  node_yazi_shared["yazi-shared<br/>shared primitives"]
  node_yazi_shim["yazi-shim<br/>compat layer"]
  node_yazi_ffi["yazi-ffi<br/>platform ffi"]
  node_yazi_parser["yazi-parser<br/>action parser"]
  node_yazi_actor["yazi-actor<br/>action handlers"]
  node_yazi_proxy["yazi-proxy<br/>dispatch proxy"]
end

subgraph group_tooling["Tooling"]
  node_yazi_cli["yazi-cli<br/>aux cli"]
  node_yazi_boot["yazi-boot<br/>startup tool"]
  node_yazi_build["yazi-build<br/>build tool"]
  node_yazi_codegen["yazi-codegen"]
end

node_yazi_fm -->|"dispatches"| node_dispatcher
node_yazi_fm -->|"routes"| node_router
node_yazi_fm -->|"spawns"| node_executor
node_yazi_fm -->|"drives"| node_yazi_core
node_yazi_fm -->|"renders with"| node_yazi_widgets
node_dispatcher -->|"parses"| node_yazi_parser
node_dispatcher -->|"forwards"| node_yazi_proxy
node_yazi_actor -->|"mutates"| node_yazi_core
node_yazi_proxy -->|"dispatches"| node_yazi_actor
node_yazi_core -->|"owns"| node_core_mgr
node_yazi_core -->|"tracks"| node_core_tab
node_yazi_core -->|"tracks"| node_core_tasks
node_yazi_core -->|"emits"| node_core_notify
node_yazi_core -->|"queues"| node_yazi_sched
node_yazi_sched -->|"executes"| node_yazi_runner
node_yazi_sched -->|"orchestrates"| node_yazi_vfs
node_yazi_vfs -->|"adapts"| node_yazi_fs
node_yazi_vfs -->|"speaks"| node_yazi_sftp
node_yazi_fs -.->|"delegates remote"| node_yazi_sftp
node_yazi_plugin -->|"uses"| node_yazi_binding
node_yazi_plugin -->|"runs on"| node_yazi_runner
node_yazi_plugin -->|"requests work"| node_yazi_sched
node_yazi_binding -->|"reads"| node_yazi_config
node_yazi_dds -->|"served by"| node_yazi_cli
node_yazi_dds -->|"syncs"| node_yazi_core
node_yazi_config -->|"configures"| node_yazi_plugin
node_yazi_config -->|"configures"| node_yazi_vfs
node_yazi_term -->|"wraps"| node_yazi_tty
node_yazi_term -->|"models"| node_yazi_emulator
node_yazi_adapter -->|"targets"| node_yazi_emulator
node_yazi_adapter -->|"renders to"| node_yazi_term
node_yazi_parser -->|"feeds"| node_yazi_actor
node_yazi_build -->|"invokes"| node_yazi_codegen
node_yazi_boot -.->|"supports"| node_yazi_cli

click node_yazi_fm "https://github.com/sxyazi/yazi/tree/main/yazi-fm"
click node_dispatcher "https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/dispatcher.rs"
click node_router "https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/router.rs"
click node_executor "https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/executor.rs"
click node_yazi_core "https://github.com/sxyazi/yazi/tree/main/yazi-core"
click node_core_mgr "https://github.com/sxyazi/yazi/blob/main/yazi-core/src/mgr/mgr.rs"
click node_core_tab "https://github.com/sxyazi/yazi/blob/main/yazi-core/src/tab/tab.rs"
click node_core_tasks "https://github.com/sxyazi/yazi/blob/main/yazi-core/src/tasks/tasks.rs"
click node_core_notify "https://github.com/sxyazi/yazi/blob/main/yazi-core/src/notify/notify.rs"
click node_core_proxy "https://github.com/sxyazi/yazi/blob/main/yazi-core/src/proxy.rs"
click node_yazi_sched "https://github.com/sxyazi/yazi/tree/main/yazi-scheduler"
click node_yazi_runner "https://github.com/sxyazi/yazi/tree/main/yazi-runner"
click node_yazi_vfs "https://github.com/sxyazi/yazi/tree/main/yazi-vfs"
click node_yazi_fs "https://github.com/sxyazi/yazi/tree/main/yazi-fs"
click node_yazi_sftp "https://github.com/sxyazi/yazi/tree/main/yazi-sftp"
click node_yazi_plugin "https://github.com/sxyazi/yazi/tree/main/yazi-plugin"
click node_yazi_binding "https://github.com/sxyazi/yazi/tree/main/yazi-binding"
click node_yazi_dds "https://github.com/sxyazi/yazi/tree/main/yazi-dds"
click node_yazi_config "https://github.com/sxyazi/yazi/tree/main/yazi-config"
click node_yazi_widgets "https://github.com/sxyazi/yazi/tree/main/yazi-widgets"
click node_yazi_term "https://github.com/sxyazi/yazi/tree/main/yazi-term"
click node_yazi_tty "https://github.com/sxyazi/yazi/tree/main/yazi-tty"
click node_yazi_emulator "https://github.com/sxyazi/yazi/tree/main/yazi-emulator"
click node_yazi_adapter "https://github.com/sxyazi/yazi/tree/main/yazi-adapter"
click node_yazi_shared "https://github.com/sxyazi/yazi/tree/main/yazi-shared"
click node_yazi_shim "https://github.com/sxyazi/yazi/tree/main/yazi-shim"
click node_yazi_ffi "https://github.com/sxyazi/yazi/tree/main/yazi-ffi"
click node_yazi_parser "https://github.com/sxyazi/yazi/tree/main/yazi-parser"
click node_yazi_actor "https://github.com/sxyazi/yazi/tree/main/yazi-actor"
click node_yazi_proxy "https://github.com/sxyazi/yazi/tree/main/yazi-proxy"
click node_yazi_cli "https://github.com/sxyazi/yazi/tree/main/yazi-cli"
click node_yazi_boot "https://github.com/sxyazi/yazi/tree/main/yazi-boot"
click node_yazi_build "https://github.com/sxyazi/yazi/tree/main/yazi-build"
click node_yazi_codegen "https://github.com/sxyazi/yazi/tree/main/yazi-codegen"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_yazi_fm,node_dispatcher,node_router,node_executor toneBlue
class node_yazi_core,node_core_mgr,node_core_tab,node_core_tasks,node_core_notify,node_core_proxy toneAmber
class node_yazi_sched,node_yazi_vfs,node_yazi_fs,node_yazi_sftp toneMint
class node_yazi_runner,node_yazi_plugin,node_yazi_binding toneRose
class node_yazi_dds,node_yazi_config,node_yazi_widgets,node_yazi_term,node_yazi_tty,node_yazi_emulator,node_yazi_adapter,node_yazi_shared,node_yazi_shim,node_yazi_ffi,node_yazi_parser,node_yazi_actor,node_yazi_proxy toneIndigo
class node_yazi_cli,node_yazi_boot,node_yazi_build,node_yazi_codegen toneTeal
```

## Components

### Runtime

User-facing executable and runtime coordination.

- [yazi-fm](https://github.com/sxyazi/yazi/tree/main/yazi-fm): tui app · Composition root for the terminal file manager: input, routing, rendering, notifications, task progress, and views. · `yazi-fm`
- [Dispatcher](https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/dispatcher.rs): action router · Translates parsed actions into app-side dispatch and execution flow. · `yazi-fm/src/dispatcher.rs`
- [Router](https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/router.rs): event router · Routes terminal events and application commands to the active handler or mode. · `yazi-fm/src/router.rs`
- [Executor](https://github.com/sxyazi/yazi/blob/main/yazi-fm/src/executor.rs): runtime glue · Runs async/runtime work and bridges app requests to background execution. · `yazi-fm/src/executor.rs`

### Core state

Long-lived app state, modes, and domain operations.

- [yazi-core](https://github.com/sxyazi/yazi/tree/main/yazi-core): domain state · Central application model for tabs, navigation, search, preview, tasks, and modal flows. · `yazi-core`
- [Manager](https://github.com/sxyazi/yazi/blob/main/yazi-core/src/mgr/mgr.rs): dir manager · Core directory manager logic for browsing, selection, filtering, and file actions. · `yazi-core/src/mgr/mgr.rs`
- [Tab state](https://github.com/sxyazi/yazi/blob/main/yazi-core/src/tab/tab.rs): tab model · Tab history, folders, selection, preview locks, and tab-local preferences. · `yazi-core/src/tab/tab.rs`
- [Task state](https://github.com/sxyazi/yazi/blob/main/yazi-core/src/tasks/tasks.rs): task model · Core task definitions and prework/process tracking used by scheduler and UI. · `yazi-core/src/tasks/tasks.rs`
- [Notify](https://github.com/sxyazi/yazi/blob/main/yazi-core/src/notify/notify.rs): notification model · Notification messages, levels, and options emitted across the app. · `yazi-core/src/notify/notify.rs`
- [Proxy](https://github.com/sxyazi/yazi/blob/main/yazi-core/src/proxy.rs): action bridge · Shared proxy interface used to connect action dispatch to submodules. · `yazi-core/src/proxy.rs`

### Filesystem

Local, virtual, and remote filesystem access.

- [yazi-scheduler](https://github.com/sxyazi/yazi/tree/main/yazi-scheduler): job scheduler · Coordinates jobs, progress, cancellation, transactions, workers, and async orchestration. · `yazi-scheduler`
- [yazi-vfs](https://github.com/sxyazi/yazi/tree/main/yazi-vfs): virtual fs · Unified filesystem abstraction spanning local and remote provider implementations. · `yazi-vfs`
- [yazi-fs](https://github.com/sxyazi/yazi/tree/main/yazi-fs): local fs · Local filesystem primitives for paths, metadata, sorting, mounts, and providers. · `yazi-fs`
- [yazi-sftp](https://github.com/sxyazi/yazi/tree/main/yazi-sftp): sftp protocol · SFTP protocol implementation used by remote filesystem providers. · `yazi-sftp`

### Plugins

Lua runtime and plugin execution pipeline.

- [yazi-runner](https://github.com/sxyazi/yazi/tree/main/yazi-runner): plugin runner · Executes plugin-side loaders, fetchers, previewers, and preloader tasks. · `yazi-runner`
- [yazi-plugin](https://github.com/sxyazi/yazi/tree/main/yazi-plugin): lua plugin · Lua presets, runtime support, UI components, and plugin utilities. · `yazi-plugin`
- [yazi-binding](https://github.com/sxyazi/yazi/tree/main/yazi-binding): ffi types · Rust-side binding layer exposing domain types, config models, and runtime data to Lua. · `yazi-binding`

### Support

Terminal, rendering, config, and shared foundation crates.

- [yazi-dds](https://github.com/sxyazi/yazi/tree/main/yazi-dds): pub-sub bus · Embedded data distribution service for cross-instance communication and state persistence. · `yazi-dds`
- [yazi-config](https://github.com/sxyazi/yazi/tree/main/yazi-config): config schema · Typed TOML configuration and presets for keymaps, layout, themes, plugins, preview, and VFS. · `yazi-config`
- [yazi-widgets](https://github.com/sxyazi/yazi/tree/main/yazi-widgets): ui widgets · Reusable input and scrolling widgets used by the terminal interface. · `yazi-widgets`
- [yazi-term](https://github.com/sxyazi/yazi/tree/main/yazi-term): terminal · Terminal behavior and state abstraction. · `yazi-term`
- [yazi-tty](https://github.com/sxyazi/yazi/tree/main/yazi-tty): tty · TTY handle and platform-specific terminal I/O wrapper. · `yazi-tty`
- [yazi-emulator](https://github.com/sxyazi/yazi/tree/main/yazi-emulator): terminal model · Terminal capability and dimension modeling for layout and rendering. · `yazi-emulator`
- [yazi-adapter](https://github.com/sxyazi/yazi/tree/main/yazi-adapter): image render · Terminal image rendering backends and driver selection for previews. · `yazi-adapter`
- [yazi-shared](https://github.com/sxyazi/yazi/tree/main/yazi-shared): shared primitives · Common utilities and data types for paths, events, pools, URLs, time, and other foundations. · `yazi-shared`
- [yazi-shim](https://github.com/sxyazi/yazi/tree/main/yazi-shim): compat layer · Stable wrappers around third-party crates used across the monorepo. · `yazi-shim`
- [yazi-ffi](https://github.com/sxyazi/yazi/tree/main/yazi-ffi): platform ffi · macOS-specific system integration such as disk arbitration and IOKit. · `yazi-ffi`
- [yazi-parser](https://github.com/sxyazi/yazi/tree/main/yazi-parser): action parser · Parses incoming action names and events into typed operations. · `yazi-parser`
- [yazi-actor](https://github.com/sxyazi/yazi/tree/main/yazi-actor): action handlers · Grouped action handlers by mode and domain area for the application bus. · `yazi-actor`
- [yazi-proxy](https://github.com/sxyazi/yazi/tree/main/yazi-proxy): dispatch proxy · Proxy functions that forward app actions to the right submodule boundary. · `yazi-proxy`

### Tooling

Build, packaging, and auxiliary command crates.

- [yazi-cli](https://github.com/sxyazi/yazi/tree/main/yazi-cli): aux cli · Auxiliary commands for DDS and package operations. · `yazi-cli`
- [yazi-boot](https://github.com/sxyazi/yazi/tree/main/yazi-boot): startup tool · Bootstrapping and diagnostics commands for startup and environment checks. · `yazi-boot`
- [yazi-build](https://github.com/sxyazi/yazi/tree/main/yazi-build): build tool · Build-time crate for generating or orchestrating build steps. · `yazi-build`
- [yazi-codegen](https://github.com/sxyazi/yazi/tree/main/yazi-codegen): codegen · Code generation helper crate used during build or generation workflows. · `yazi-codegen`

## Connections

- yazi-fm → Dispatcher: dispatches · Application input is converted into internal actions and commands.
- yazi-fm → Router: routes · Terminal and application events are routed to the active mode or handler.
- yazi-fm → Executor: spawns · The app delegates async work and background execution to the runtime executor.
- yazi-fm → yazi-core: drives · UI events mutate core state and consume the resulting updates.
- yazi-fm → yazi-widgets: renders with · Interactive panels and inputs use reusable widget primitives.
- Dispatcher → yazi-parser: parses · Action names and event payloads are decoded into typed operations.
- Dispatcher → yazi-proxy: forwards · Parsed actions are forwarded through the proxy dispatch boundary.
- yazi-actor → yazi-core: mutates · Action handlers apply domain changes to core state.
- yazi-proxy → yazi-actor: dispatches · The proxy routes requests into the appropriate handler group.
- yazi-core → Manager: owns · Core manager logic owns navigation, selection, filtering, and file operations.
- yazi-core → Tab state: tracks · Tab-local state and history are maintained as part of the domain model.
- yazi-core → Task state: tracks · Task metadata and prework/process state are part of core state.
- yazi-core → Notify: emits · Notifications are modeled and emitted by the domain layer.
- yazi-core → yazi-scheduler: queues · Core state schedules file, process, plugin, and fetch work through the scheduler.
- yazi-scheduler → yazi-runner: executes · Scheduled plugin-related work is carried out by the runner.
- yazi-scheduler → yazi-vfs: orchestrates · Filesystem operations and remote provider work flow through the virtual filesystem boundary.
- yazi-vfs → yazi-fs: adapts · Virtual filesystem abstractions build on the local filesystem layer.
- yazi-vfs → yazi-sftp: speaks · Remote provider support is backed by SFTP protocol implementation.
- yazi-fs → yazi-sftp: delegates remote · Local abstractions stay separate from protocol-specific remote access.
- yazi-plugin → yazi-binding: uses · Lua runtime and presets consume the Rust-side binding and domain types.
- yazi-plugin → yazi-runner: runs on · Plugin loaders, fetchers, previewers, and preloaders execute through the runner.
- yazi-plugin → yazi-scheduler: requests work · Plugin work is coordinated as scheduled jobs with progress and cancellation.
- yazi-binding → yazi-config: reads · Binding models mirror typed configuration structures used at runtime.
- yazi-dds → yazi-cli: served by · The CLI interacts with DDS commands and package workflows.
- yazi-dds → yazi-core: syncs · Cross-instance state and events are integrated with the application model.
- yazi-config → yazi-plugin: configures · User presets define plugin components, previewers, fetchers, and spotters.
- yazi-config → yazi-vfs: configures · Configuration also covers VFS services and remote access behavior.
- yazi-term → yazi-tty: wraps · Terminal state sits on top of TTY handling.
- yazi-term → yazi-emulator: models · Terminal capabilities and dimensions are modeled for rendering and layout.
- yazi-adapter → yazi-emulator: targets · Image rendering backends adapt to terminal capabilities.
- yazi-adapter → yazi-term: renders to · Image output is emitted through the terminal layer.
- yazi-parser → yazi-actor: feeds · Typed actions feed grouped handlers.
- yazi-build → yazi-codegen: invokes · Build tooling includes code generation support.
- yazi-boot → yazi-cli: supports · Bootstrapping and diagnostic actions complement auxiliary commands.
