Article

How to share local files with Qwen Code Managed Agents

Teams running Qwen Code Managed Agents can connect a local folder. Check permissions, browser support, file limits and retained session content.

Editorial illustration for How to share local files with Qwen Code Managed Agents: a controlled task flows from input to output. Not documentary evidence.

Qwen Code v0.27.4, released on 15 November 2026, adds local-folder access for users of enabled Managed Agents deployments. To use it, open an active session in the Web Shell, select Local files, choose Connect and grant a folder read/write access. The browser must stay connected for file access to continue; text already returned to the session can remain in its stored history.

This guide is for teams operating Qwen Code Managed Agents and people using those deployments—not ordinary Qwen Chat users. The reference deployment is experimental and requires compatible server components, storage and a model endpoint. Updating the command-line app alone does not set up that service or enable folder access.

1. Have the operator enable local-file access

Ask the deployment operator to check the release’s compatibility manifest and existing configuration. Local-file access is off by default. The documented setting is qwen.managed-agent.client-files.enabled; set it to true in the deployment configuration, preserving the other settings. The configuration reference identifies this as a configuration-file property without a packaged environment-variable mapping.

2. Check the session and browser

The session must be active, advertise the clientFiles capability and allow you to execute work—not merely view it. If Local files is absent, have the operator check deployment enablement, compatible session-running software and session eligibility. Repeatedly changing browser permissions cannot enable a missing server capability.

Use a Chromium browser with the directory picker, such as Chrome, and open the Web Shell directly in a tab. The browser checks require a secure context, normally HTTPS for a remote deployment, and reject a frame embedded by a different website. Firefox and Safari are outside this feature’s supported design, even if they can display the rest of the Web Shell.

3. Connect one folder and review file actions

Open Local files in the Managed conversation header, choose Connect and select the intended folder. Confirm the folder name and available tools in the panel. A project-specific folder is a useful starting point: it keeps the grant aligned with the task rather than including unrelated files.

The browser grants access to one local folder; the session’s permission policy controls which file actions can proceed. The picker requests read/write permission, so asking the agent only to read does not turn the browser grant into read-only access.

The four local-file tools can list a directory, read text, search text and create or overwrite a text file. A write supplies the whole replacement file, not a partial edit. This bridge is not a PDF parser, media editor or local command shell.

Start with a bounded request, such as asking for a summary of a small README without changes. Review tool requests under the session’s configured approval policy; reads can require approval too. Full Access/yolo and saved permission decisions can change whether a person is prompted, so do not assume every write always waits for fresh confirmation.

For teams comparing coding assistants, the separate guide to GitHub Copilot’s approval controls explains the same planning question: what an agent can reach and who authorizes an action are different decisions. Copilot’s settings do not configure Qwen Code.

4. Keep requests within the message limits

The default relay limit is 60 KiB per request or response. That is 60 × 1,024 = 61,440 bytes for the complete serialized message, including protocol fields and text escaping—not a promise that a 60 KiB file fits. The session-running component also independently caps serialized tool results at 60 KiB, so raising the relay setting alone does not remove that result limit.

For an oversized result, narrow the directory listing or ask for fewer lines of a suitable text file. There is a separate constraint: the local reader rejects files above 1,000,000 bytes before selecting a line range. Requesting ten lines does not bypass that check. A very long single line can also exceed the message budget.

Edits need particular care: because writes replace the complete file, the full new text must fit in the request. There is no partial-edit or append tool here that makes a large replacement possible in smaller pieces.

Keep the browser connected throughout the task. The default registration lifetime is eight hours, but that is not a promise of eight hours’ access after closing the tab.

5. Disconnect without assuming history was deleted

Choose Disconnect when finished. In the tagged implementation, this stops the connection and clears its matching remembered folder handle. Closing the tab also ends live access, but can leave a browser-stored handle and permission available for later reuse. It does not necessarily force a new native permission prompt next time.

Disconnecting is not a history-deletion command. Qwen’s implementation notes say file content returned by browser tools follows the session’s normal stored tool-result policy. The temporary connection and relay queue therefore have a different lifetime from text already recorded in tool results or answers.

Before connecting company files, check the deployment’s retention settings and the terms of the model endpoint it uses. “Local files” does not mean offline model processing. The related guide to self-hosted Claude Managed Agents explains why hosting an agent service and choosing where model requests go are separate architecture decisions.

When a server Workspace is the better fit

The practical dividing line is whether you can keep the browser present. A short, attended review of text files fits this connection model. For work that must continue after your laptop disconnects, consider the deployment’s existing server Workspace storage, subject to its access and retention rules. The local-folder design neither copies files there automatically nor silently switches to Workspace files when the browser disappears.

Budget for the deployment separately. Qwen Code’s Apache-2.0 licence describes the software licence, not a free hosted-service entitlement. Hosting, database and storage, operations and the chosen model endpoint remain separate costs. The reference deployment guide does not establish a single local-files subscription price or a universal usage allowance.