# `desk` CLI — read-only reference The `desk` bin is a read-only overview surface for work items and projects. Never edit through desk — writes go through `pa work` and `pa project`. ## Verbs | Verb | Purpose | |---|---| | `desk overview` | Summary of all projects and in-flight work. | | `desk today` | What is active and needs attention today. | | `desk work` | List active work items. Filters: `--mine`, `--theirs`, `--status`, `--project`, `--category`. | | `desk projects` | List active projects. `--all` includes done/archived. `--all-teams` / `--team ` control team scoping. | Run `desk --help` for the current authoritative list. ## Team scoping `desk projects`, `desk overview`, and `desk today` scope projects to the local team-identity set (`executor`, falling back to `assignee`, matched against `teamIdentities` — string[], mixed agent + role names — else `[paName]`; `paName` is always a member) when `operator/config/preferences.json` sets `"scopeProjectsToTeam": true`. Unset — the historical default — everything shows, unchanged. Projects missing both fields always show (fail open). `--all-teams` bypasses scoping; `--team ` narrows to one identity. Full rationale: `packages/core/knowledge/work-management/desk-cli.md`. ## When to reach for `desk` - **Session boot briefing.** `desk overview` is the summary source. - **State check.** `desk work --status in-progress` before dispatching new work. - **Operator ask "what's in flight".** `desk work` or `desk overview` depending on granularity. ## When NOT to reach for `desk` - **Reading actual JSON.** Use `Read` on the file. - **Writing state.** Use `pa work` / `pa project`. ## Cache behaviour None. `desk` reads from disk on every invocation. ## Related - `pa-cli-reference.md` — write-side complement. - `packages/core/knowledge/work-management/desk-cli.md` — the discipline this bin supports.