description, kind
| description | kind |
|---|---|
| Account screens use authenticated Remote commands and a snapshot stream. The controller exposes login state without returning tokens or PKCE secrets. | package-reference |
@deepseek-ai/dsh-api-account-controller
English | 中文
Summary
Account screens use authenticated Remote commands and a snapshot stream. The controller exposes login state without returning tokens or PKCE secrets.
Table of Contents
Use this package
The account namespace exposes getState, getProfile / getBalance, startSignIn, cancelSignIn, signOut, and watch. watch emits an initial complete state and subsequent complete states; disconnecting stops observation, not the login attempt. Cancellation names the attempt ID so a stale screen cannot cancel a newer login.
Understand the implementation
The controller forwards operations to the account service and maintains no independent account state; no invariant companion is published.
Further Exploration
The credentials subsystem owns storage APIs; the architecture explains application composition.
Model Experience
None, as account credentials affect HTTP authentication and never enter model prompts, Session logs, or tool results.
KV Cache effect
No model request prefix changes.
Known Limitations and Deferred Work
- A disconnected UI can recover account state through watch, but cannot resume an attempt after the Host exits. Credentials and request-token resolution are not Remote operations.
Dev Note
The desktop login decision records cancellation and storage ownership.