Summary
Currently, the file upload component in the openclaw-control-ui interface is restricted to image formats (MIME type image/*). This limitation restricts the efficiency of users who need to transmit documents, code snippets, or logs directly through the web console.
Problem to solve
Allowing users to upload documents (PDF, DOCX) and code files (TS, PY, SH) directly in the web console would significantly improve the workflow efficiency for troubleshooting and collaborative development without requiring third-party messaging integrations.
Proposed solution
Update the accept attribute of the file input component in openclaw-control-ui to allow broader MIME types (e.g., / or a defined list of common document/archive formats).
Ensure the backend gateway service is configured to safely receive, validate, and store generic file types, including appropriate virus scanning and filename sanitization.
Alternatives considered
No response
Impact
This request stems from current limitations where users are forced to utilize auxiliary channels (like whats app or external cloud drives) for file exchange, which creates unnecessary friction in the control console workflow.
Evidence/examples
No response
Additional information
No response
Summary
Currently, the file upload component in the openclaw-control-ui interface is restricted to image formats (MIME type image/*). This limitation restricts the efficiency of users who need to transmit documents, code snippets, or logs directly through the web console.
Problem to solve
Allowing users to upload documents (PDF, DOCX) and code files (TS, PY, SH) directly in the web console would significantly improve the workflow efficiency for troubleshooting and collaborative development without requiring third-party messaging integrations.
Proposed solution
Update the accept attribute of the file input component in openclaw-control-ui to allow broader MIME types (e.g., / or a defined list of common document/archive formats).
Ensure the backend gateway service is configured to safely receive, validate, and store generic file types, including appropriate virus scanning and filename sanitization.
Alternatives considered
No response
Impact
This request stems from current limitations where users are forced to utilize auxiliary channels (like whats app or external cloud drives) for file exchange, which creates unnecessary friction in the control console workflow.
Evidence/examples
No response
Additional information
No response