Work with files on your Mac

When Local files is available for your workspace, a supported version of d5s for macOS lets an agent work with folders you explicitly authorize. Use the Desktop app to configure access and start these conversations. Local operations require the app to be running and connected. Browser messages, scheduled work, and messages from connected channels cannot use these personal grants.

Choose folders

1. Open Settings → Desktop.
2. Under Local folders, choose Add folder and select a folder with the macOS picker.
3. Add other folders as needed.

You can select a folder your macOS account can access, including a project folder, Documents, or an external drive. macOS permissions still apply. Adding a folder makes it available for granting access; it does not give agents permission automatically.

Choose an agent's permissions

Open Manage agent → Local files, choose a folder, and select one access mode:

Access	What the agent can do
Read only	List and read files without changing them.
Write only	Create files or replace contents at a specified path without listing or reading existing files.
Both	List, read, create, and edit files.

Review the agent, workspace, folder, and permission in the native confirmation dialog. Cancelling leaves access unchanged. You can grant different permissions for different folders. Deletion is not supported.

Reading sends file content to d5s and the model used for the conversation. Content retained in the conversation follows its sharing permissions. Sharing an agent does not give collaborators access to your local folder grants.

Ask for a local operation

Be explicit about the folder and intended action. For example:

• “Read the invoices in Reports and summarize the overdue amounts.”
• “Create a new weekly summary in Reports.”
• “Read project-notes.md, update the next steps, and save the changes.”

Presenting a file in the conversation does not automatically save it to your Mac. The agent must use a local-file operation. This is not folder mirroring: changing a cloud artifact does not automatically update a local file.

Each local file read or write supports up to 16 MiB, including binary files such as documents, spreadsheets, and images. Larger files must be reduced or split before transfer.

Creating a file at an existing path returns a collision rather than silently overwriting it. Replacing contents is a separate, explicit operation. Content-aware edits need Both permissions and a recent read; a detected conflict requires reading the current file again. Avoid editing the same file simultaneously in another application.

Check results and connection

Recent operations shows the action, relative path, and result. A completed write confirms the local operation. An unknown outcome means confirmation was lost; check the file before asking the agent to repeat a write.

An offline Mac cannot execute a new local operation. Reconnect d5s Desktop, then ask the agent to try again. Local writes do not wait in an automatic delivery queue. Closing the window does not necessarily quit d5s on macOS.

Pause or revoke

Use Pause all access in Desktop settings to block new operations on this Mac, or Revoke beside a folder in the agent's settings to remove that grant. You can revoke locally while offline. Removing an authorized folder also removes the local grants for it.

These actions do not delete saved files or undo completed operations. Signing out stops local access. If a folder moves or macOS permissions change, select it again and review access.

Review earlier delivery access

The previous automatic-delivery feature is replaced by explicit file operations. Earlier create-only grants do not gain read or replacement access automatically. Review each folder's permissions and confirm them in Desktop.

Already saved files remain in place. Previous deliveries retains completed and cancelled delivery history. Pending legacy deliveries are cancelled rather than converted into new file operations.