Whale widgets for DeepSeek Harness: balance and Bilibili

Whale widgets are not one plugin but three kinds: balance, companion, and platform-linked. Identify the kind before comparing same-name implementations; the wrong kind produces "why does it not show my balance."

Three kinds with different jobs

The difference is what they display and what they depend on.

The balance whale is a gauge; the companion whale is a companion. One cares about accuracy, the other about state and interruption; their troubleshooting differs.

Check the source for platform-linked variants. They involve third-party APIs and more configuration; do not enter sensitive credentials for unknown implementations.

Balance whale: where numbers come from

It shows three numbers: total balance, today usage, and per-turn spend. They come from an API query, not local estimation (source).

The data source determines refresh behavior. Real-time queries refresh live; local accumulation updates per turn. When a number stalls, confirm which model applies.

The key is a prerequisite. Implementations that need an API key show stale numbers when the key expires; that is not a broken widget.

Peak pricing is an extra. Some implementations show period-based price differences; without it, balance still works (source).

Companion whale: state and interruption

It turns work state into visible feedback. For example, busy while coding, a caring line when balance is low, a reminder after inactivity (source).

Its value is emotional feedback, not information density. For precise usage, choose a balance whale; for warmth, choose a companion.

Set the interruption boundary yourself. Frequent care prompts become noise; tune frequency and quiet hours before leaving it on.

State linkage needs an active session. Without one, the companion may sit still; that is design, not failure.

Choosing among same-name implementations

At least two sources publish dsh-whale-widget; they differ in data and options.

1. Owner and repository: different maintainers, different stability.
2. Data source: API query or local accumulation; accurate but network-dependent versus stable but possibly biased.
3. Options: bubble text, snapping and flipping, sound, peak pricing; choose by need.
4. Update time: recent updates are more likely to support the current version.
5. Install one: multiple widgets overlap and query repeatedly.

Do not use download count as the only signal. Widgets differ in details; documentation and updates are more reliable.

Confirm it does not ask for the main account password. Only an API key or local configuration is needed; abandon implementations that ask for credentials.

Install and placement

Installation is the normal flow; position is draggable and remembered.

1. Search the plugin in the Hub, verify owner, and install; or use the CLI.
2. Restart and confirm the widget appears in the lower-right corner.
3. Drag it away from the input area.
4. Configure key, refresh interval, and displayed fields in plugin settings.
5. Restart once and confirm position and toggle state are remembered.

The lower-right corner is the usual default. When a desktop pet or other widget is present, disable the others before adjusting position.

Position is stored locally. A new machine or cleared configuration returns to default; check the toggle and position before reinstalling.

Refresh and visibility failures

Stale numbers and invisible widgets are different problems.

1. Widget invisible: check the toggle, profile, whether position is off-screen, and overlap with other components.
2. Number stale: check key validity, endpoint reachability, and refresh interval.
3. Number biased: determine whether it queries live or accumulates; accumulation differs across devices.
4. Disappears after restart: check whether toggle state was saved and whether configuration went into the wrong profile.
5. UI stutters: reduce animation frequency and refresh interval.

Check presence before accuracy. Invisible is a loading problem; stale is a data problem; reversing the order wastes time.

Logs and network requests are evidence. Whether the plugin sent a request and whether it succeeded beats reinstalling.

Performance and privacy

A widget runs continuously; consider both performance and privacy.

1. Refresh interval drives request volume. Too frequent may hit limits; lengthen it.
2. Animation drives rendering. Multiple widgets compound; disable animation first when slow.
3. Least privilege. Give only the key needed for balance queries.
4. Trusted source. Widgets touch keys and usage data; avoid unknown implementations.

Widgets look light, but the long-run cost is requests and rendering. Enable when needed and turn off otherwise.

Next steps

Choose kind, then implementation, then position and frequency. For desktop pet forms, read What desktop pet plugins exist. For balance and usage plugins, read What balance plugins exist. To install a pet, read DeepSeek desktop pet setup.

Sources: dsh-whale-widget plugin page (ggxx001), dsh-whale-widget plugin page (tuweizhi), dsh-whale-musume plugin page, deepseek-balance-whale-widget plugin page