v1.0.85-lzc.1 (based on upstream v1.0.85) This release follows upstream v1.0.81 through v1.0.85: - Proxy routes were reworked: a new "Settings → Proxy" page lets you add, edit, delete and bulk-import routes, test each one (latency, egress IP and location), and use SOCKS5. - Proxies are now a pool: a pool switch, a strategy (priority / round-robin / random / least-used) and an interval; each route has its own weight and enable switch. An account binds to at most one route; unbound accounts follow the pool strategy, and a global egress proxy acts as the fallback. Disabled or deleted routes never fail over silently — they report an error. - Account export / import: export a group's accounts as an archive and import JSON back (existing uids are not overwritten by default). Exports contain credentials, so they ask for confirmation first, are recorded in the audit log and are never cached. - A key can check its own quota: GET /v1/usage with the key returns used and remaining tokens / credits, expiry and the bound model list — and the lookup itself spends nothing. - Credit red packets can now be limited to specific models; key model allowlists can be picked from a searchable checklist instead of typed by hand. - New read-only endpoint GET /api/accounts/credits-snapshot returns each account's last recorded credits and the time it was recorded, without querying the provider — handy for dashboards and reconciliation scripts. - Fixes: long conversations with tool calls no longer fail with a spurious 400 "tool calls and tool results do not match"; the model list also exposes the fields third-party clients look for (image input, reasoning levels); pasting several model names into the allowlist no longer drops them; one-click update no longer reports a false success when dependency installation fails; egress proxies set in .env now actually take effect in container and systemd deployments. Two notes: the update *download* only honours http / https proxies (a SOCKS5 setting is ignored with a log line), and WB_PROXY_STICKY_SECONDS is deprecated — the sticky window now lives in Settings → Proxy. Lazycat-specific behaviour is unchanged: passwordless sign-in, per-user in-app roles, persistent data, and upgrades handled by Lazycat app management.

v1.0.80-lzc.1 (based on upstream v1.0.80) This release follows upstream v1.0.76 through v1.0.80: - Back up your data to your own PostgreSQL: a new "Data backup" section in Settings mirrors the local database to a PostgreSQL instance you provide (the panel keeps reading and writing the local database as before; PostgreSQL is only off-site insurance and never slows requests). Scheduled automatic backups are supported, and "restore from PostgreSQL" saves a local copy first so a wrong restore can be undone. - Per-account egress routes: when adding or editing an account you can pick a named proxy; login, check-in, credit queries and token refresh all use that route, and a broken route reports an error instead of silently falling back to the default egress. - Usage trend granularity now follows the selected range: "Today" is shown by hour (24 buckets, current hour highlighted), 7 days by day, and 30 / 90 days as an area chart. Days without traffic are drawn as 0 instead of being skipped. - The dashboard health snapshot adds a "view all accounts" link when more than 9 accounts exist. - More robust one-click update: when the GitHub API is rate-limited it falls back to the web redirect; while a new release is still being signed the UI explains the wait and keeps the button disabled; container deployments no longer wait for a timeout. - Fixes: upstream egress honours HTTP_PROXY / HTTPS_PROXY / NO_PROXY; escaped underscores in tool-call regexes no longer fail; self-hosted Redis URLs can be verified with "test connection"; the backup settings form is no longer overwritten by polling; dialog layout and error-message readability improvements. Lazycat-specific behaviour is unchanged: passwordless sign-in, per-user in-app roles, persistent data, and upgrades handled by Lazycat app management.

v1.0.75-lzc.2 Two additions around accounts and credits: - Refresh all tokens at once: a button on the accounts page renews the accessToken of every account in a single run, with a concurrency cap to avoid provider rate limits and a single upstream reload at the end. Results are reported per account. - Token refresh plan: schedule "refresh every account every N days" at a chosen hour, with last/next run times and a "run now" action. - New "Credit flow" card on the dashboard: income and expense are tracked separately with a selectable range (today / 3 / 7 / 15 / 30 days). Income comes from balance-increase records, expense from the actual per-request charge; the two use different accounting, so they are labelled honestly and never collapsed into a single number.

v1.0.75-lzc.1 (based on upstream v1.0.75) This release follows upstream v1.0.75, focused on navigation and settings usability: - The bottom dock is grouped into Overview / Operations / Governance with visible group names (also on phones), and collapsed from 11 entries to 8: Tasks, Red packets and the Chat playground moved into their parent pages and are switched with tabs at the top of those pages. The address bar follows, so old bookmarks and shared links still work. - The dock can be pinned to the bottom; a pinned dock is no longer draggable and stops covering page content, and the choice survives a reload. - Every settings tab now has its own URL (e.g. /settings/users) that can be bookmarked, shared and navigated with Back; switching tabs no longer refetches config, so a half-filled form is not lost. - New search panel: press Cmd+K (Ctrl+K on Windows/Linux) to search and jump to any page by name or path. The panel only navigates, it never performs an action. - Saving settings now shows whether the reload actually succeeded: "applying" then "applied", or a failure reason plus a hint to restart the container on the host (the config is already saved). - Fixes: the dock guide bubble can be dismissed at any time and stays dismissed; the update result and log can be cleared; one-click update supports a download proxy. Lazycat-specific behaviour is unchanged: passwordless sign-in, per-user in-app roles, persistent data, and upgrades handled by Lazycat app management.

v1.0.74-lzc.1 (the first lazy cat micro-service version, based on upstream v1.0.74) ·Secret-free login: Use your lazy cat account to enter directly, no longer requiring a separate administrator password. ·Roles and permissions: Lazy cat platform administrators have all management permissions, which can be viewed by ordinary members by default; administrators can assign intra-application permissions according to lazy cat users in "Settings → Manage Users", and the changes will take effect as they are made. ·Account pool management: Scan code to add CodeBuddy accounts, automatic check-in, Token validity period monitoring and automatic renewal, point balance and expiration reminder, and multi-account pool grouping. ·Key distribution: Create an API key for different users, which can independently limit quotas, IP whitelists and model whitelists. ·OpenAI-compatible gateway: Downstream clients use/v1 to directly access it, compatible with Anthropic clients. ·Observability: request log, usage statistics, model center and chat test bench. ·Data persistence: Account authorization, keys and logs are saved on the micro-service, and will not be lost when upgrading or restarting the application. ·Application upgrades are the unified responsibility of Lazy Cat Application Management, and container self-update entries no longer appear in the panel.