3 Commits

Author	SHA1	Message	Date
Acbox Liu	1680316c7f	refactor(agent): remove agent gateway instead of twilight sdk (#264) ... * refactor(agent): replace TypeScript agent gateway with in-process Go agent using twilight-ai SDK - Remove apps/agent (Bun/Elysia gateway), packages/agent (@memoh/agent), internal/bun runtime manager, and all embedded agent/bun assets - Add internal/agent package powered by twilight-ai SDK for LLM calls, tool execution, streaming, sential logic, tag extraction, and prompts - Integrate ToolGatewayService in-process for both built-in and user MCP tools, eliminating HTTP round-trips to the old gateway - Update resolver to convert between sdk.Message and ModelMessage at the boundary (resolver_messages.go), keeping agent package free of persistence concerns - Prepend user message before storeRound since SDK only returns output messages (assistant + tool) - Clean up all Docker configs, TOML configs, nginx proxy, Dockerfile.agent, and Go config structs related to the removed agent gateway - Update cmd/agent and cmd/memoh entry points with setter-based ToolGateway injection to avoid FX dependency cycles * fix(web): move form declaration before computed properties that reference it The `form` reactive object was declared after computed properties like `selectedMemoryProvider` and `isSelectedMemoryProviderPersisted` that reference it, causing a TDZ ReferenceError during setup. * fix: prevent UTF-8 character corruption in streaming text output StreamTagExtractor.Push() used byte-level string slicing to hold back buffer tails for tag detection, which could split multi-byte UTF-8 characters. After json.Marshal replaced invalid bytes with U+FFFD, the corruption became permanent — causing garbled CJK characters (�) in agent responses. Add safeUTF8SplitIndex() to back up split points to valid character boundaries. Also fix byte-level truncation in command/formatter.go and command/fs.go to use rune-aware slicing. * fix: add agent error logging and fix Gemini tool schema validation - Log agent stream errors in both SSE and WebSocket paths with bot/model context - Fix send tool `attachments` parameter: empty `items` schema rejected by Google Gemini API (INVALID_ARGUMENT), now specifies `{"type": "string"}` - Upgrade twilight-ai to d898f0b (includes raw body in API error messages) * chore(ci): remove agent gateway from Docker build and release pipelines Agent gateway has been replaced by in-process Go agent; remove the obsolete Docker image matrix entry, Bun/UPX CI steps, and agent-binary build logic from the release script. * fix: preserve attachment filename, metadata, and container path through persistence - Add `name` column to `bot_history_message_assets` (migration 0034) to persist original filenames across page refreshes. - Add `metadata` JSONB column (migration 0035) to store source_path, source_url, and other context alongside each asset. - Update SQL queries, sqlc-generated code, and all Go types (MessageAsset, AssetRef, OutboundAssetRef, FileAttachment) to carry name and metadata through the full lifecycle. - Extract filenames from path/URL in AttachmentsResolver before clearing raw paths; enrich streaming event metadata with name, source_path, and source_url in both the WebSocket and channel inbound ingestion paths. - Implement `LinkAssets` on message service and `LinkOutboundAssets` on flow resolver so WebSocket-streamed bot attachments are persisted to the correct assistant message after streaming completes. - Frontend: update MessageAsset type with metadata field, pass metadata through to attachment items, and reorder attachment-block.vue template so container files (identified by metadata.source_path) open in the sidebar file manager instead of triggering a download. * refactor(agent): decouple built-in tools from MCP, load via ToolProvider interface Migrate all 13 built-in tool providers from internal/mcp/providers/ to internal/agent/tools/ using the twilight-ai sdk.Tool structure. The agent now loads tools through a ToolProvider interface instead of the MCP ToolGatewayService, which is simplified to only manage external federation sources. This enables selective tool loading and removes the coupling between business tools and the MCP protocol layer. * refactor(flow): split monolithic resolver.go into focused modules Break the 1959-line resolver.go into 12 files organized by concern: - resolver.go: core orchestration (Resolver struct, resolve, Chat, prepareRunConfig) - resolver_stream.go: streaming (StreamChat, StreamChatWS, tryStoreStream) - resolver_trigger.go: schedule/heartbeat triggers - resolver_attachments.go: attachment routing, inlining, encoding - resolver_history.go: message loading, deduplication, token trimming - resolver_store.go: persistence (storeRound, storeMessages, asset linking) - resolver_memory.go: memory provider integration - resolver_model_selection.go: model selection and candidate matching - resolver_identity.go: display name and channel identity resolution - resolver_settings.go: bot settings, loop detection, inbox - user_header.go: YAML front-matter formatting - resolver_util.go: shared utilities (sanitize, normalize, dedup, UUID) * fix(agent): enable Anthropic extended thinking by passing ReasoningConfig to provider Anthropic's thinking requires WithThinking() at provider creation time, unlike OpenAI which uses per-request ReasoningEffort. The config was never wired through, so Claude models could not trigger thinking. * refactor(agent): extract prompts into embedded markdown templates Move inline prompt strings from prompt.go into separate .md files under internal/agent/prompts/, using {{key}} placeholders and a simple render engine. Remove obsolete SystemPromptParams fields (Language, MaxContextLoadTime, Channels, CurrentChannel) and their call-site usage. * fix: lint	2026-03-19 13:31:54 +08:00
Acbox Liu	23d49a1c7b	feat: message abort and web socket support (#222) ... * feat: message abort and web socket support * fix(web): chat end * fix: lint * fix: lint	2026-03-09 23:27:50 +08:00
BBQ	bc374fe8cd	refactor: content-addressed assets, cross-channel multimodal, infra simplification (#63) ... * refactor(attachment): multimodal attachment refactor with snapshot schema and storage layer - Add snapshot schema migration (0008) and update init/versions/snapshots - Add internal/attachment and internal/channel normalize for unified attachment handling - Move containerfs provider from internal/media to internal/storage - Update agent types, channel adapters (Telegram/Feishu), inbound and handlers - Add containerd snapshot lineage and local_channel tests - Regenerate sqlc, swagger and SDK * refactor(media): content-addressed asset system with unified naming - Replace asset_id foreign key with content_hash as sole identifier for bot_history_message_assets (pure soft-link model) - Remove mime, size_bytes, storage_key from DB; derive at read time via media.Resolve from actual storage - Merge migrations 0008/0009 into single 0008; keep 0001 as canonical schema - Add Docker initdb script for deterministic migration execution order - Fix cross-channel real-time image display (Telegram → WebUI SSE) - Fix message disappearing on refresh (null assets fallback) - Fix file icon instead of image preview (mime derivation from storage) - Unify AssetID → ContentHash naming across Go, Agent, and Frontend - Change storage key prefix from 4-char to 2-char for directory sharding - Add server-entrypoint.sh for Docker deployment migration handling * refactor(infra): embedded migrations, Docker simplification, and config consolidation - Embed SQL migrations into Go binary, removing shell-based migration scripts - Consolidate config files into conf/ directory (app.example.toml, app.docker.toml, app.dev.toml) - Simplify Docker setup: remove initdb.d scripts, streamline nginx config and entrypoint - Remove legacy CLI, feishu-echo commands, and obsolete incremental migration files - Update install script and docs to require sudo for one-click install - Add mise tasks for dev environment orchestration * chore: recover migrations --------- Co-authored-by: Acbox <acbox0328@gmail.com>	2026-02-19 00:20:27 +08:00