Description
When using openclaw message send --channel msteams --media <file> to send a file to a user, the file consent card appears in Teams but clicking "Allow" or "Decline" fails with "This card action is not supported by EVA."
Steps to Reproduce
- Create a file in the agent workspace
- Run:
openclaw message send --channel msteams --target "conversation:<convId>" --message "Here is a file" --media /home/node/.openclaw/workspace/test.csv
- Teams shows a consent card: "EVA needs permission to upload this file to your OneDrive"
- Click "Allow"
- Error: "This card action is not supported by EVA"
Expected Behavior
Clicking "Allow" should upload the file to the user OneDrive and show a file card with download link.
Actual Behavior
The consent card appears, but the fileConsent/invoke callback with action "accept" fails because the file was not registered in the provider pendingUploads store before sending the consent card. The CLI message send --media path does not pre-register the file.
Workaround
Upload files to the user OneDrive via Microsoft Graph API directly, then send a Teams message with the file link. This bypasses the consent flow entirely.
Environment
- OpenClaw version: 2026.3.22
- Docker image: ghcr.io/openclaw/openclaw:latest
- Channel: msteams (Bot Framework, single tenant)
- manifest.json: supportsFiles true
Description
When using
openclaw message send --channel msteams --media <file>to send a file to a user, the file consent card appears in Teams but clicking "Allow" or "Decline" fails with "This card action is not supported by EVA."Steps to Reproduce
openclaw message send --channel msteams --target "conversation:<convId>" --message "Here is a file" --media /home/node/.openclaw/workspace/test.csvExpected Behavior
Clicking "Allow" should upload the file to the user OneDrive and show a file card with download link.
Actual Behavior
The consent card appears, but the fileConsent/invoke callback with action "accept" fails because the file was not registered in the provider pendingUploads store before sending the consent card. The CLI message send --media path does not pre-register the file.
Workaround
Upload files to the user OneDrive via Microsoft Graph API directly, then send a Teams message with the file link. This bypasses the consent flow entirely.
Environment