> ## Documentation Index > Fetch the complete documentation index at: https://www.landbase.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # How the CLI fits into the Landbase platform > Understand how datasets, runs, sessions, and workflows created in the CLI relate to what you see in the Landbase web platform. # How the CLI fits into the Landbase platform landbase-cli is not a standalone tool — it is a terminal interface to the same Landbase platform you access through the web UI at `platform.landbase.com`. The data objects you create and manipulate in the CLI exist in the platform and vice versa. *** ## Datasets When you run a search, upload a file, or run a workflow, Landbase creates a **dataset** in your workspace. Datasets are the core data objects in the platform. In the CLI, you work with datasets via their IDs: ```bash theme={null} landbase-cli datasets list landbase-cli datasets show ``` These same datasets appear in the Landbase web UI under your account. A search you ran from the terminal shows up as a dataset in the web UI, and you can inspect it there. *** ## Agent runs Every search command creates an **agent run**. An agent run represents one invocation of the Landbase AI — what you asked for, what it produced, and the dataset it created. ```bash theme={null} landbase-cli runs list --session=my-session landbase-cli runs get ``` Agent runs are visible in the Landbase platform under your activity history. *** ## Sessions Sessions group related agent runs together. When you use `--session=uk-saas`, all runs under that label belong to the same session thread on the backend. In the web platform, session activity appears in your workspace history. The session ID (the UUID, not the label) is the identifier that links CLI runs to the platform view. *** ## Workflows Workflow runs (`workflow match`, `workflow enrich`, etc.) appear in the platform as processing jobs attached to their parent dataset. You can see the status of a workflow job in both the CLI and the web UI. ```bash theme={null} landbase-cli workflow status ``` The web UI shows the same status, along with any errors and the child datasets produced. *** ## What is CLI-only A few things live only in the CLI and do not have a web UI equivalent: * **Session labels** — the human-readable aliases you assign with `--session`. These are stored locally in `~/.landbase/sessions.json`. The web UI works with UUIDs, not labels. * **Local files** — downloaded files (`.jsonl`, `.csv`, `.parquet`) are on your machine and are not stored in the platform. * **Config and auth files** — `~/.landbase/` is local only. *** ## What the platform adds beyond the CLI The web UI offers: * Visual browsing of datasets and their lineage * Rich campaign management, monitoring, and outreach tools * Connecting sending channels — inboxes and LinkedIn accounts * Account-level settings and team management * Integrations (CRM sync, email, LinkedIn, dialer) The CLI is optimized for programmatic access, automation, and agent workflows. It can now **create and launch** outbound email and LinkedIn campaigns directly — see [How to launch a campaign](/docs/how-to/launch-a-campaign) — while connecting the sending channels (inboxes, LinkedIn accounts) and the richer campaign dashboards still live in the web platform. *** ## Related * [How sessions work](/docs/explanation/how-sessions-work) * [Workflows vs. direct commands](/docs/explanation/workflows-vs-commands) * [datasets reference](/docs/reference/datasets)