Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Control UI regression: drag-and-drop file to chat no longer works / old 'drop to local file path' workflow is gone [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#54854•Fetched 2026-04-08 01:35:13
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
XinGaoSHXinGaoSH
Participants
XinGaoSHXinGaoSH

After updating to OpenClaw 3.24, the Web UI / Control UI chat no longer supports the old drag-and-drop file workflow.

Previously, I could drag a local file directly into the chat input, and it would turn into a usable local file path/reference in the message. That workflow was much faster and more practical for local desktop usage.

Now in 3.24:

  • dragging files into the chat does nothing
  • I cannot attach files from the chat input
  • the previous “drop file -> get path/reference -> send to agent” workflow appears to be gone

This feels like a regression in usability, not just a missing minor feature.

Error Message

TypeError: resolvePreferredOpenClawTmpDir is not a function

Root Cause

For local OpenClaw users, files already exist on the same machine as the agent workspace. The old “drop to path/reference” interaction was more natural and efficient than a web-style upload model.

The old dialog/UI was more usable for this reason.

Code Example

TypeError: resolvePreferredOpenClawTmpDir is not a function
RAW_BUFFERClick to expand / collapse

Summary

After updating to OpenClaw 3.24, the Web UI / Control UI chat no longer supports the old drag-and-drop file workflow.

Previously, I could drag a local file directly into the chat input, and it would turn into a usable local file path/reference in the message. That workflow was much faster and more practical for local desktop usage.

Now in 3.24:

  • dragging files into the chat does nothing
  • I cannot attach files from the chat input
  • the previous “drop file -> get path/reference -> send to agent” workflow appears to be gone

This feels like a regression in usability, not just a missing minor feature.

Expected behavior

For local / desktop OpenClaw usage, dragging a file into the chat should work again.

Ideal behavior:

  • drag a local file into the chat input
  • OpenClaw converts it into a usable local file path or attachment reference
  • send directly to the agent without extra upload friction

This old workflow was significantly better than a traditional “upload attachment” flow.

Actual behavior

In Control UI / Web UI on 3.24:

  • drag-and-drop does not work
  • no usable file path/reference is inserted into the chat
  • file attach behavior appears broken or unavailable

Why this matters

For local OpenClaw users, files already exist on the same machine as the agent workspace. The old “drop to path/reference” interaction was more natural and efficient than a web-style upload model.

The old dialog/UI was more usable for this reason.

Environment

  • OpenClaw version: 3.24
  • Surface: Control UI / Web UI
  • Platform: macOS
  • Usage mode: local desktop usage

Additional note

After upgrading, I also noticed at least one plugin compatibility issue in my environment (openclaw-weixin load failure), though I’m not sure whether that is related to this drag-and-drop regression.

Error seen:

TypeError: resolvePreferredOpenClawTmpDir is not a function

This may be unrelated, but mentioning it in case it helps with upgrade/regression investigation.

Request

Please confirm whether:

  1. drag-and-drop file to chat is intentionally removed
  2. this is a regression/bug in 3.24
  3. the old “drop local file -> path/reference” workflow can be restored

If possible, I strongly recommend restoring the old behavior, because it was much better for local agent workflows.

extent analysis

Fix Plan

To restore the old drag-and-drop file workflow, we need to modify the OpenClaw code to handle file drops in the chat input.

Here are the steps:

  • Update the chat-input component to listen for dragover and drop events.
  • Use the DataTransfer API to get the dropped file and convert it into a usable local file path or attachment reference.
  • Send the file path or attachment reference to the agent without extra upload friction.

Example code:

// chat-input.component.js
import React, { useState, useEffect } from 'react';

const ChatInput = () => {
  const [droppedFile, setDroppedFile] = useState(null);

  const handleDragOver = (e) => {
    e.preventDefault();
  };

  const handleDrop = (e) => {
    e.preventDefault();
    const file = e.dataTransfer.files[0];
    setDroppedFile(file);
    // Convert file to usable local file path or attachment reference
    const filePath = URL.createObjectURL(file);
    // Send file path or attachment reference to agent
    sendFileToAgent(filePath);
  };

  return (
    <div
      onDragOver={handleDragOver}
      onDrop={handleDrop}
    >
      <input type="text" />
    </div>
  );
};

export default ChatInput;

Verification

To verify that the fix worked, try dragging a local file into the chat input. The file should be converted into a usable local file path or attachment reference and sent to the agent without extra upload friction.

Extra Tips

  • Make sure to handle errors and edge cases, such as multiple file drops or invalid file types.
  • Consider adding a loading indicator or feedback to the user while the file is being processed.
  • If you're using a plugin like openclaw-weixin, make sure to check for compatibility issues and update the plugin if necessary.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

For local / desktop OpenClaw usage, dragging a file into the chat should work again.

Ideal behavior:

  • drag a local file into the chat input
  • OpenClaw converts it into a usable local file path or attachment reference
  • send directly to the agent without extra upload friction

This old workflow was significantly better than a traditional “upload attachment” flow.

#installation#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING