Fix bridge compression history handling (#726)
* feat(bridge): refactor compression to use DB history and add structured logging - Extract buildDbHistory() to share message loading between buildCompressedHistory and forceCompressBridgeHistory - forceCompressBridgeHistory now reads from local DB instead of using Python-provided messages, ensuring consistency with api_server path - Pass sessionId to compressor for snapshot-aware compression - Add force_compress flag to bridge chat requests - Add bridgeLogger structured logging for compression lifecycle - Simplify schemas, session-sync, and providers Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix bridge compression history handling --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -14,7 +14,7 @@ export interface ProviderPreset {
|
||||
|
||||
export const PROVIDER_PRESETS: ProviderPreset[] = [
|
||||
{
|
||||
label: 'FUN-Codex',
|
||||
label: 'Codex-apikey.fun',
|
||||
value: 'fun-codex',
|
||||
builtin: true,
|
||||
base_url: 'https://api.apikey.fun/v1',
|
||||
@@ -27,7 +27,7 @@ export const PROVIDER_PRESETS: ProviderPreset[] = [
|
||||
],
|
||||
},
|
||||
{
|
||||
label: 'FUN-Claude',
|
||||
label: 'Claude-apikey.fun',
|
||||
value: 'fun-claude',
|
||||
builtin: true,
|
||||
base_url: 'https://api.apikey.fun',
|
||||
|
||||
Reference in New Issue
Block a user