Repository navigation
whalegate v0.5.34
v0.5.34
Login in the account's own Chrome is now watched, and a suspended account is shown as such.
- Login refusals reach the dashboard. While an account's Chrome window is open, whalegate reads the
/users/loginreply. When DeepSeek refuses (wrong password, device risk, suspension…) the reason shows up as a dashboard message, in the log, and in the account's status. Captured from the real site: a suspended account answersbiz_code 10/USER_IS_BANNED("Do vi phạm, tài khoản của bạn đã tạm thời bị đình chỉ"). - Suspended accounts are closed out for you. On
USER_IS_BANNEDthe window closes by itself, nothing is saved, the account is switched off in the pool and the dashboard shows it struck through with a suspended label (no pointless log in again button). A later successful login or verify lifts the mark. A chat answer of40012is shown the same way. - No more silent login as somebody else. When you log in again for a specific account and the window ends up signed in as a different DeepSeek user, nothing is saved, no password is remembered, the wrong DeepSeek session is wiped from that profile and the account says so. A profile that another account already uses is no longer reused: a fresh machine is opened instead.
- Sign-in pre-fill never uses a masked label as the email, and the fill happens before whalegate starts recording what you type.
- Verify recognises a muted account; its status text is translated.
- Fix: remembered credentials could silently fail to save if the data folder was recreated at the wrong moment.