- Introduced new plugin management section in the application.
- Added translations for English, Russian, Simplified Chinese, and Traditional Chinese.
- Created new API endpoints for managing plugins, including listing, enabling/disabling, and configuring plugins.
- Updated routing to include a dedicated PluginsPage.
- Defined new types for plugin configuration and metadata in TypeScript.
- Enhanced the existing API client to handle plugin-related requests.
feat(authFiles): refactor OAuth provider handling and improve alias validation
feat(config): implement unsaved changes guard in ConfigPage
feat(dashboard): extend provider stats to include vertex and ampcode
fix(logs): enhance incremental log merging and improve error handling
feat(system): format build time display using utility functions
feat(api): normalize OAuth provider keys in authFiles API
feat(provider): update OpenAI provider deletion method to use index
feat(format): add date formatting utilities for better date handling
- Refactored MainLayout to always show logs in the sidebar.
- Updated i18n files for English, Russian, Simplified Chinese, and Traditional Chinese to include new log-related messages.
- Improved LogsPage styling for better layout and added runtime notices.
- Enhanced LogsPage logic to handle different server runtime kinds (CPA and Home).
- Added new API methods to handle logs fetching and request log downloading with runtime checks.
- Introduced runtime kind detection during authentication and connection status updates.
- Updated types to include server runtime kind and adjusted API responses accordingly.
The backend OpenAICompatibilityAPIKey struct only has api-key and
proxy-url (internal/config/config.go:570-577). PUT /openai-compatibility
unmarshals into this struct (config_lists.go:439) and discards any
unknown field, so per-entry headers submitted from the UI never persist
and never reach the runtime request path. The GET response wrapper
also has no headers field (config_auth_index.go:31-34).
Drop the per-entry headers input from BaseProviderForm and the
ApiKeyEntry/ApiKeyEntryInput types. Connectivity test and model
discovery stop reading entry-level headers — they continue to apply
provider-level headers, which is the supported contract.
Backend's POST /auth-files and DELETE /auth-files single-item paths
return only {status:"ok"}, with no uploaded/deleted/files
(auth_files.go:680 and :794). Multi-item paths return the full payload.
85c8b34 simplified the normalizer assuming the full payload was always
present, which caused single-file uploads and single-item deletes to be
read as "0 succeeded" — the upload page skipped its success toast and
list refresh, and batch delete reported "(0)" with no row removal.
Re-introduce a narrow fallback: when failed is empty and the count
field is omitted, derive uploaded/deleted and files from requestedNames.
The fallback only kicks in for the documented single-item shape, not
for the partial/failure paths.
All bool-tagged config fields on the backend are Go bools and serialize
as JSON true/false (e.g. Debug, RequestLog, WebsocketAuth, Disabled,
Websockets, ForceModelPrefix). normalizeBoolean is only called against
those response paths, so the number / string / Boolean(value) fallbacks
never fire.
Backend batch upload/delete handlers always return a complete payload:
status (string), uploaded/deleted (number), files (string array), and
failed (only on partial). See auth_files.go:702-711. The fallback chains
that re-derived uploaded/deleted counts and file names from the
requestedNames list were unreachable.
Likewise, runtime_only is always a real bool from Go (auth_files.go:403),
and entry.modified is never emitted, so isRuntimeOnlyEntry collapses
to a strict equality check and readDateField drops the modified alias.
The backend api-call response schema (api_tools.go:54-56) fixes the
field names to status_code / header / body. camelCase statusCode and
plural headers are never emitted.
Backend list endpoints (config_lists.go: GetGeminiKeys / GetClaudeKeys /
GetCodexKeys / GetOpenAICompat / GetVertexCompatKeys) always wrap the
result as {"<kebab-section>": [...]}, never as a raw array, never under
"items" or "data". And /config emits the same kebab keys, so the camelCase
aliases (geminiApiKey, openAICompatibility, ...) are unreachable.
Remove RAW_SECTION_ALIASES and inline the lookup; drop the raw-array
and items/data fallbacks from extractArrayPayload.
The backend emits provider config with kebab-case JSON tags only
(internal/config/config.go: ClaudeKey/CodexKey/GeminiKey/OpenAICompatibility,
internal/api/handlers/management/config_auth_index.go for auth-index).
The camelCase / snake_case entries in PROVIDER_KEY_FIELDS,
OPENAI_PROVIDER_FIELDS, MODEL_ALIAS_FIELDS, API_KEY_ENTRY_FIELDS,
CLOAK_FIELDS, RESPONSE_ONLY_FIELDS were dead — same for the identity
helpers and the apiKeyEntries fallback in mergeOpenAIProviderPayload.
The backend always serializes config fields with kebab-case JSON tags
(internal/config/config.go). The camelCase and snake_case fallbacks in
normalizeApiKeyEntry / normalizeProviderKeyConfig / normalizeGeminiKeyConfig /
normalizeOpenAIProvider / normalizeAmpcode* / normalizeConfigResponse are
dead paths. Read kebab-case only.
The legacy openai-compatibility `api-keys` (flat string array) flat-string
branch is also gone — backend startup migration is disabled
(internal/config/config.go:657).
Prepending new API key entries shifted all existing indices, causing useConnectivityTest index-based status tracking to desync.
Fix: keep array operations as append (stable indices) and reverse the rendering order so new entries appear at the top visually. Use realIdx for status lookups, React keys, and all updateField operations.
Add eye toggle button for all API key input fields so users can verify their keys before saving.
Changes:
- BaseProviderForm: wrap single API key field (Gemini/Codex/Claude/Vertex) with passwordField + toggle button
- BaseProviderForm: wrap per-entry API key fields (OpenAI-compatible) with passwordField + toggle button
- BaseProviderForm: extract applyRawApiKey helper to populate apiKey from resource.raw in edit mode
- BaseProviderForm: sync initialFormSignature with applyRawApiKey to prevent false isDirty
- sharedForm.module.scss: add .passwordField, .passwordInput, .passwordToggle styles
- i18n: add showApiKey/hideApiKey keys to en, zh-CN, zh-TW, ru locale files
- accessibility: add aria-label and title attributes on both toggle buttons
Previously confirmDiscardIfDirty only fired for Sheet-driven close paths
(Cancel button, backdrop, escape). Clicking a different provider in the
left rail bypassed the prompt and silently dropped the form changes.
ProviderSheet now exposes the existing guard via an imperative handle,
which the workbench page calls before swapping the active brand.
- useModelDiscovery: openaiCompatibility branch now forwards
resolvedAuthIndex into modelsApi.fetchModelsViaApiCall, mirroring the
gemini/codex/claude branches. Configs that rely on a backend-resolved
auth index without a local plaintext key can now list models.
- useConnectivityTest: runOpenAIKey accepts an authIndex fallback when
entry.apiKey is empty, sets Authorization: Bearer $TOKEN$ in that
case, and forwards authIndex on the /api-call request so the gateway
can substitute the upstream token.
- useModelDiscovery: reset stale results when baseUrl / apiKey /
apiKeyEntries / headers / authIndex change, so reopening the discovery
panel after editing fields re-fetches instead of showing the previous
endpoint's models.
The new workbench only wired refreshRecentRequests into the manual refresh
button; the hook itself just set an interval (240s). As a result the
status bar showed empty/zero until the first poll. Load on mount when
enabled (cache hit avoids a network round-trip).
The actual login page lives at src/pages/LoginPage.{tsx,module.scss};
this stale src/pages/Login/Login.module.scss has had no importers since
it was committed in 450964f.
- Remove the legacy ai_providers.* block (~268 keys per locale) — only
nav.ai_providers under a different namespace is still referenced
- Remove providersPage.{disconnected,error,actions.back,
actions.openModelCatalog,ampcode.behaviorSection,detail.empty,
status.notAvailable,modelCatalog.{loading,openAction,summaryCount,
summaryError,summaryTitle}} which were never wired up after the
ProvidersWorkbench rewrite
These helpers were only consumed by the old AiProviders edit pages and
became orphaned after the providers refactor. modelInputListUtils.ts was
only used by ModelInputList, so it goes too.