CLI surface often lags server API surface
Asked to use a project CLI to perform an action, only to find the CLI doesnt expose that subcommand even though the server does.
A thin CLI wrapper around a REST backend will not always cover every server endpoint — feature surface drifts. When user says use the CLI to do X, check the CLIs help against the servers route tree (e.g. ls src/routes/api) before assuming the CLI can do it. If theres a gap, you can still drive the action by curl-ing the same endpoints with the bearer token the CLI would read from its config dir; source the credentials file in a subshell rather than cat-ing it so secrets dont land in the transcript (and a guarded sandbox may block the cat entirely).
First compare CLI subcommands to server API routes; if the desired action only exists server-side, plan to call the API directly with the CLIs configured token.