1. Unix socket permissions: 0o660 → 0o600 (owner-only access), preventing
other processes in the same group from injecting messages via the API.
2. Telegram bot token redaction: when file downloads fail, the bot token
embedded in the Telegram API URL is now replaced with [REDACTED] in
error messages to prevent token leakage in logs.
3. Startup warning for open allow_from: all platforms now log a WARN-level
message when allow_from is not configured, making it obvious that the
deployment permits all users. This surfaces the fail-open default so
operators can make an informed decision.
Ref #60
This commit introduces a new relay system for bot-to-bot communication, including:
- New `relay` command with send/bind functionality
- RelayManager for coordinating messages between engines
- API endpoints for relay operations
- Interactive `/bind` command for chat group binding
- Session handling and message forwarding
- CLI documentation and help messages
- Internationalization support for relay messages
- Stream preview improvements for relay messages
generated by llmgit
Co-Authored-By: Claude <noreply@anthropic.com>
- Store http.Server instance in APIServer struct for better resource management
- Enhance provider listing with current provider marker and remove bold formatting
- Update i18n strings for provider list titles
generated by llmgit
Co-Authored-By: Claude <noreply@anthropic.com>
Add multimodal image support to Claude sessions by saving attachments to temp files and sending as base64-encoded content. Implement new CLI `send` command and Unix socket API server for external tools to send messages to active sessions. Image support added across all platforms (Discord, Feishu, Line, Slack, Telegram, WeCom).
generated by llmgit
Co-Authored-By: Claude <noreply@anthropic.com>
Shawn