类型
bug
你遇到的问题 / 你想做什么
After creating a Feishu app through WebSetup QR onboarding, the app works during the same daemon session. After restarting the machine or codex-remote daemon, the same app remains configured and connected, but WebSetup treats it as a manually added bot and refuses to auto-send test messages.
The app was created through the QR onboarding flow, not by manually entering App ID / App Secret.
你希望最后变成什么样
A Feishu app created through WebSetup QR onboarding should remain recognized as WebSetup-created after daemon restart.
If WebSetup cannot persist enough metadata to auto-send the test message after restart, the UI should avoid saying the bot was manually added when it was actually created by QR onboarding.
相关证据
Original daemon logs show QR onboarding metadata was present at creation time:
feishu onboarding ready: session=... app_id=cli_xxx installer_id_present=true
feishu onboarding completed: session=... gateway=... app_id=cli_xxx
After restart, the app is still connected and basic messaging works, but WebSetup shows:
手动添加的机器人无法自动发送测试消息，请直接在飞书后台继续手动配置。
Persisted config appears to keep only fields like appId, appSecret, enabled, and verifiedAt for the Feishu app; I could not find persisted onboarding / installer metadata.
已知约束 / 担心点
Basic Feishu text messaging still works after restart, so this seems limited to WebSetup state restoration / test-message UX rather than the runtime gateway.
补充说明
No response
类型
bug
你遇到的问题 / 你想做什么
After creating a Feishu app through WebSetup QR onboarding, the app works during the same daemon session. After restarting the machine or codex-remote daemon, the same app remains configured and connected, but WebSetup treats it as a manually added bot and refuses to auto-send test messages.
The app was created through the QR onboarding flow, not by manually entering App ID / App Secret.
你希望最后变成什么样
A Feishu app created through WebSetup QR onboarding should remain recognized as WebSetup-created after daemon restart.
If WebSetup cannot persist enough metadata to auto-send the test message after restart, the UI should avoid saying the bot was manually added when it was actually created by QR onboarding.
相关证据
Original daemon logs show QR onboarding metadata was present at creation time:
After restart, the app is still connected and basic messaging works, but WebSetup shows:
Persisted config appears to keep only fields like
appId,appSecret,enabled, andverifiedAtfor the Feishu app; I could not find persisted onboarding / installer metadata.已知约束 / 担心点
Basic Feishu text messaging still works after restart, so this seems limited to WebSetup state restoration / test-message UX rather than the runtime gateway.
补充说明
No response