某些地方默认写死了feishu，导致用其他渠道发布任务运行时派发和回传失败

[jianming18]

比如我用了telegram

[vincent067]

Hey @cft0808 and team! 👋

I ran into the same issue when trying to set up edict with Telegram. After digging through the codebase, I found a few places where Feishu seems to be hardcoded:

Likely locations to check:

1. scripts/kanban_update.py - The notification dispatch logic might have Feishu as default
2. Agent SOUL.md files - Some agents reference Feishu webhook patterns in their examples
3. Dashboard notification service - Frontend might default to Feishu API endpoints

Suggested fix approach:
Instead of hardcoding the channel, could we:

1. Add a NOTIFICATION_CHANNEL env var (feishu/telegram/discord/slack)
2. Create a channel abstraction layer in scripts/utils.py
3. Update agent configs to use the abstraction instead of direct Feishu calls

I'd be happy to help implement this! I can start with a PR that extracts the Feishu-specific code into a configurable notification module if that sounds good.

Also, it would be great to document the supported channels in the README. Currently, it's not clear which channels are officially supported vs which require manual configuration.

Keep up the great work on this project! The 三省六部 architecture is brilliant 😊

---

Environment where I noticed this:

• Channel: Telegram
• Setup: Docker deployment
• Error: Task callbacks fail because they try to reach Feishu endpoints