cognition.ai/plugins* request,
flattened into each params struct so the wire shape stays flat.
Both methods resolve and filter to this scope before touching any plugin
state: a plugin (or its cached metadata) outside the caller’s directories
and managed origins is never exposed, even by key.
A client with no folder open omits cwd (and sends no
additionalDirectories): the scope is then the caller’s managed origins
alone — account, org and personal — with no repo tier. Nothing on disk
stands in for the missing directory.
Deliberately not session-scoped. Plugin state is a function of the
directories and the user’s governance, not of a conversation, so a session
id would be a second way to say what cwd already says — and one the agent
would have to either honour (resolving from a session’s older snapshot) or
silently ignore. Read-only clients with no session get the same answer as
ones that have one.