Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

AgentKit shutdown bypasses FeishuChannelExtension in-flight message draining

Open
#901 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start at create_agentkit_app(root_agent, enable_feishu=True) and trace the AgentKit background thread and reconnect loop that call the Feishu SDK Channel directly. Compare that path with FeishuChannelExtension.start() and shutdown(). Done means application shutdown invokes the extension lifecycle, drains in-flight messages, emits the expected shutdown logs, and delivers the final Feishu reply.

Written by the indexing model from the issue text.

Description

Description

AgentKit applications created with:

create_agentkit_app(root_agent, enable_feishu=True)

do not actually use the lifecycle implemented by FeishuChannelExtension. AgentKit currently maintains a separate background thread and reconnect loop that calls the underlying Feishu SDK Channel's start() and stop() methods directly.

As a result, FeishuChannelExtension.start() and FeishuChannelExtension.shutdown() are bypassed. During application shutdown, in-flight Feishu messages are not drained before the process exits.

Current Behaviour:
Image

The following expected logs are absent:

GRACEFUL_TEST_TOOL_COMPLETED
Shutting down Feishu channel: closing WebSocket and draining 1 in-flight message(s)...
Feishu channel drained; shutdown complete.

And the user will not receive the final Feishu reply.

Dominant language
Python
Stars
344
Forks
98
Avg merge
8h 17m
Merged PRs (30d)
152

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from volcengine/veadk-python

All issues in volcengine/veadk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.