--- title: "Work with local files" description: "Let Bearly read, create, edit, and run files on your computer from a folder you choose." canonical: "https://bearly.ai/docs/features/work-locally/" markdown: "https://bearly.ai/docs/features/work-locally.md" --- # Work with local files HTML: [https://bearly.ai/docs/features/work-locally/](https://bearly.ai/docs/features/work-locally/) > Let Bearly read, create, edit, and run files on your computer from a folder you choose. **Work locally** lets Bearly work with files and commands on your computer while you remain in control of each kind of access. It is available in the Bearly desktop app for macOS, Windows, and Linux. On the web, **Work locally** opens the desktop-app handoff. The control is not shown on mobile. Chats that used local files remain readable on other devices, but Bearly cannot inspect, refresh, or change those files until you return to the same chat in the desktop app. > **Caution — Local commands are not confined to the selected folder** > The selected folder gives Bearly a working location; it is not a security sandbox. A command you approve can reach other files that your operating-system account can access. Review the command, path, reason, and overwrite details before allowing an action. ## Complete a task in a local folder 1. **Open the chat in Bearly desktop** Start a new chat or return to the chat that owns the work. The **Work locally** control appears in the context strip attached to the chat input after the chat finishes loading. 2. **Choose where Bearly should work** Select **Work locally**, then choose **Choose folder…** and select the folder for the task. Bearly shows the folder name on the control. Previously selected folders may appear in the same menu, with their full paths, so you can return to one without opening the system picker. If you do not choose a folder, **Auto** can use a private work area for this chat. Choose a folder when the task should read or change an existing local project, or when you want the finished files placed somewhere specific. 3. **Describe the result and boundaries** Name the relevant files, the desired result, and anything Bearly must not change. Relative filenames refer to the current working folder. ```text copy Read the CSV files in this folder, create a monthly summary workbook, and add the finished workbook to this chat. Do not change the source files. ``` 4. **Review each permission request** Bearly pauses before reading, writing, editing, saving a chat file locally, or running a local command unless an applicable permission is already active. Adding a local file from outside the working folder also requires review. The card names the action and explains why it is needed. Select **Details** to inspect the file, command, working folder, overwrite choice, or other relevant information. - **Allow** approves only the action in front of you. - **Deny** blocks that action and lets Bearly continue without it when possible. - **Allow for…** lets you choose **This reply**, **This session**, or **This chat**. Read the expanded warning, then use the confirmation button to grant that duration. Read-only grants use labels such as **Allow reads this reply**. A broader local-tools grant can also cover writes, edits, file transfers, and commands. **Auto** makes local work available to Bearly; it does not approve these requests for you. 5. **Inspect the result** Bearly reports what it read, changed, created, or ran. Ask it to verify important output—for example, reopen a generated file, summarize changes, or run a relevant check. For a finished file you want to keep with the conversation, ask Bearly to “add it to this chat.” The file then appears as a normal chat file you can open or download later. 6. **Stop or revoke access** Select the chat's **Stop** control to stop the current response. If a local command is running, Bearly also stops that command. When a session- or chat-length grant is active, the context strip shows **Local reads allowed** or **Local tools allowed**. Select its **Revoke** control to remove the active session and chat permissions. Bearly will ask again before another protected action. ## Change folders or turn local work off Select the current folder name or **Work locally** to reopen its menu. - Choose another recent folder to make it the working folder for this chat. - Select **Choose folder…** to browse somewhere else. - Select **Clear folder** to return to the chat's private work area. - Select **Off for this chat** to remove local file and command access from Bearly's available tools. - When it is off, select **Turn on for this chat** to restore **Auto** mode. The selected folder and chat-length permissions belong to this chat on this device. Opening a different chat does not silently give it the same working folder or permissions. ## Move files between the computer and chat Work locally can bridge the two places when you ask clearly: - “Add `final-report.pdf` to this chat” publishes a local result as a chat file. A file outside the working folder requires review before its contents are uploaded. - “Save the attached workbook as `inputs/source.xlsx` in this folder” copies a chat file into the working folder after you approve the write. - “Update the local draft, then add the revised copy to the chat” changes the local file first and publishes the result separately. Local file contents you approve for reading may be sent to the AI model working on the reply. A local file you add to the chat is stored with that conversation like other chat files. ## Work safely - Use a narrowly scoped folder that contains only what the task needs. - Ask Bearly to stop before overwriting, deleting, installing, sending, or publishing anything consequential. - Check **Overwrite** in permission details. A write can replace an existing file. - Prefer **Allow** for one action until you understand the flow. Use **This reply**, **This session**, or **This chat** only when repeated prompts would obstruct work you have already reviewed. - Revoke a broad grant as soon as the task is finished. For work in visible applications rather than files and commands, see [Use your computer with Bearly](https://bearly.ai/docs/features/computer-use.md). ## If local work is unavailable or fails | What you see | What to do | | --- | --- | | **Work locally** opens **Get the app** | Install or open the Bearly desktop app, then return to the same chat. | | The control does not appear in Bearly desktop | Update Bearly, reopen the app, and let the chat finish loading. Older desktop builds may not support all local actions. | | A recent folder no longer works | The folder may have moved, been renamed, or been removed. Select **Choose folder…** and choose its current location. | | Bearly cannot read or write a protected folder | Choose a folder your account can access, or grant Bearly the relevant operating-system file permission and retry. | | You selected **Deny** by mistake | Ask Bearly to try the action again, review the new card, and select **Allow**. | | A command fails or times out | Open **Details**, check the command and working folder, then ask Bearly to retry with a narrower step. Confirm that any program the task needs is available on your computer. | | A file is too large to read directly | Ask Bearly to inspect only the relevant rows, pages, or text range, or work from a smaller copy. | | Local work is blocked for your team | Ask an administrator to review **Teams** → team name → **Policies** → policy name → **Code & Automation** → **Disable Local Exec**. | ## Continue through the documentation - [Documentation index](https://bearly.ai/docs.md): Browse every Bearly guide. - [Previous: Use your computer with Bearly](https://bearly.ai/docs/features/computer-use.md) - [Next: Add files to a project](https://bearly.ai/docs/projects/documents.md)