* docs: rewrite getting started documentation
- Overhauled getting started guide to align with current frontend UI and logic.
- Split getting started documentation into modular chapters covering providers, models, bots, containers, files, skills, MCP, channels, memory, subagents, heartbeats, and search/email providers.
- Updated sidebar and index page to reflect the new documentation structure.
Made-with: Cursor
* docs: fix lint error in en.ts
Made-with: Cursor
* docs: add Channels documentation category
- Created a new top-level documentation category 'Channels'.
- Added detailed configuration guides for Telegram, Feishu (Lark), and Discord.
- Included official documentation references for bot creation on each platform.
- Updated 'Getting Started' channel page and main index with links to the new guides.
Made-with: Cursor
* refactor: docs to v0.2
* docs: add Scheduled Tasks chapter to getting started
- Created schedule.md covering cron-based automation, fields, pattern reference, and execution flow.
- Added comparison table between Schedule and Heartbeat features.
- Updated sidebar navigation to include the new chapter.
Made-with: Cursor
- docker-compose.yml now defaults to ./config.toml instead of
conf/app.docker.toml, enforcing explicit configuration for
production deployments (dev environment still uses conf/ directly)
- Update DEPLOYMENT.md and docs with clear instructions to copy
config template before starting
- Update config-toml.md: add registry/cni fields, remove obsolete
[brave] section (search providers are now managed via web UI),
fix default values
- Add China mainland mirror documentation
Split business executors from federation sources and migrate unified tool/federation transports to the official go-sdk for stricter MCP compliance and safer session lifecycle handling. Add targeted regression tests for accept compatibility, initialization retries, pending cleanup, and include updated swagger artifacts.
Align channel identity and bind flow across backend and app-facing layers, including generated swagger artifacts and package lock updates while excluding docs content changes.
- Refactor channel manager with support for Sender/Receiver interfaces and hot-swappable adapters.
- Implement identity routing and pre-authentication logic for inbound messages.
- Update database schema to support bot pre-auth keys and extended channel session metadata.
- Add Telegram and Feishu channel configuration and adapter enhancements.
- Update Swagger documentation and internal handlers for channel management.
Co-authored-by: Cursor <cursoragent@cursor.com>
Major changes:
1. Core Architecture: Decoupled Bots from Users. Bots now have independent lifecycles, member management (bot_members), and dedicated configurations.
2. Channel Gateway:
- Implemented a unified Channel Manager supporting Feishu, Telegram, and Local (Web/CLI) adapters.
- Added message processing pipeline to normalize interactions across different platforms.
- Introduced a Contact system for identity binding and guest access policies.
3. Database & Tooling:
- Consolidated all migrations into 0001_init with updated schema for bots, channels, and contacts.
- Optimized sqlc.yaml to automatically track the migrations directory.
4. Agent Enhancements:
- Introduced ToolContext to provide Agents with platform-aware execution capabilities (e.g., messaging, contact lookups).
- Added tool logging and fallback mechanisms for toolChoice execution.
5. UI & Docs: Updated frontend stores, UI components, and Swagger documentation to align with the new Bot-centric model.