Skip to content

adr: Feishu as another agent surface #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jiahao6635 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

adr: Feishu as another agent surface #358

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions adrs/feishu.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Feishu as another way to talk to QM

My company uses Feishu for day-to-day communication, so Slack isn't where we'd
actually use QM. We'd like to add QM to our existing Feishu chats instead of asking
everyone to move to another tool.

A useful first version for us would be pretty small: DMs, mentioning the bot in a
group, replies in the same thread, and scheduled updates back to that chat. Text is
enough to start; files and interactive cards can come later.

Feishu has an official Node SDK and a WebSocket event mode, which sounds close to
the way QM connects to Slack without needing a public callback URL. I'm happy to
test this in our real Feishu tenant.

Would Feishu be in scope as another agent surface? If so, would you rather keep it
as its own deployment plugin or support it alongside Slack in the main project?