Haruno Knowledge base

Which files Haruno can reach

A chat can use its own folder, the folders added to its project, and a scratch area. Anything else in your user folder is out of reach, and Haruno says so instead of asking.

  • Mac appAvailable
  • Windows appAvailable

A chat can work only with the files it was given. This page says what those are, what happens when Haruno reaches for something else, and why a chat sometimes refuses to start on a folder.

What a chat can reach

  • The folder the chat works in. For a chat in a project, that is the project's folder. For a chat outside a project, it is a folder of its own.
  • Folders added to a project. A project chat can use the folders added as sources.
  • A scratch area. It is private to the chat. Haruno uses it for temporary files and can write there without asking.
  • The books, in some chats. A chat outside a project that is offered the books tools can read the Portfolio's books as files. It can change only the mapping files of a company.

Your other documents stay out of reach. A card cannot change that, because the access is set when the chat starts.

When Haruno reaches for a folder it was not given

Haruno does not show an approval card, because answering yes could not make it work. It is refused right away, and the chat says so.

  • In a project chat: This chat can't reach the folder. You can share that folder with it. A button, Share this folder…, is under the message.
  • Outside a project: A chat outside a project can only use its own folder. To give a chat more folders, add them in a project's settings. There is no button.

Sharing the folder

  1. Press Share this folder…

    A question opens. It shows the full path and says The chat will be able to read and write this folder. The default button is Cancel.

  2. Choose Share folder

    The chat says is now shared with this chat. The folder joins the project as a source, and the chat uses it from the next message.

The offer is narrow on purpose:

  • It names only the folder that holds the file Haruno tried to open.
  • It never offers your whole user folder, a hidden folder, or a folder where programs keep their own data.
  • If a folder is not allowed, the chat says can't be shared with a chat, and there is no button.
  • The same folder is offered once per message.

A chat that will not start

Before a chat starts, Haruno checks every folder the chat will use. This happens once when the chat starts, not for each message. It refuses to start if it finds something it cannot vouch for. The reason appears in the chat, and it is always in English.

What it foundWhat the message asks for
A link to somewhere else in a place Haruno ownsRemove the link and try again.
A file that has more than one name (a hard link) and the other name is outside the folderRemove the extra name, or open a project folder without it.
More than about 1.5 million files and foldersOpen a smaller project folder.
More than 1,024 links in the folderOpen a project folder with fewer links.

A hard link means one file that shows up under two names in two places. A link means a shortcut that leads to a different folder.

An ordinary code or documents folder is well inside these limits, built folders included.

A big folder can take a moment

While Haruno checks a very large folder, the chat shows its usual sending state. There is no separate progress message.

What to tell a customer

Keep each chat on the folder it needs. If a chat says it cannot reach a folder, add that folder to the project instead of copying files around.

Last updated · PR #2944 · View this version on GitHub

History (1 version)
  1. Internal knowledge base for staff: site, reader keys, assistant, 197 pages and the PR rule (#2944)
    What changed
    @@ -0,0 +1,69 @@
    +---
    +title: Which files Haruno can reach
    +summary: A chat can use its own folder, the folders added to its project, and a scratch area. Anything else in your user folder is out of reach, and Haruno says so instead of asking.
    +feature: sandbox-file-access
    +covers:
    +  - windows-client/docs/sandbox-approvals.md
    +  - windows-client/docs/sandbox-path-inspection.md
    +  - windows-client/Haruno.Desktop.Services/Sandbox/SandboxApprovalGate.cs
    +  - windows-client/Haruno.Desktop.Services/Sandbox/SandboxReparsePointPins.cs
    +---
    +
    +A chat can work only with the files it was given. This page says what those are, what happens when Haruno reaches for something else, and why a chat sometimes refuses to start on a folder.
    +
    +## What a chat can reach
    +
    +- **The folder the chat works in.** For a chat in a project, that is the project's folder. For a chat outside a project, it is a folder of its own.
    +- **Folders added to a project.** A project chat can use the folders added as sources.
    +- **A scratch area.** It is private to the chat. Haruno uses it for temporary files and can write there without asking.
    +- **The books, in some chats.** A chat outside a project that is offered the books tools can read the Portfolio's books as files. It can change only the mapping files of a company.
    +
    +Your other documents stay out of reach. A card cannot change that, because the access is set when the chat starts.
    +
    +## When Haruno reaches for a folder it was not given
    +
    +Haruno does not show an approval card, because answering yes could not make it work. It is refused right away, and the chat says so.
    +
    +- **In a project chat:** **This chat can't reach** the folder. **You can share that folder with it.** A button, **Share this folder…**, is under the message.
    +- **Outside a project:** **A chat outside a project can only use its own folder. To give a chat more folders, add them in a project's settings.** There is no button.
    +
    +### Sharing the folder
    +
    +<Steps>
    +<Step title="Press Share this folder…">
    +A question opens. It shows the full path and says **The chat will be able to read and write this folder.** The default button is Cancel.
    +</Step>
    +<Step title="Choose Share folder">
    +The chat says **is now shared with this chat.** The folder joins the project as a source, and the chat uses it from the next message.
    +</Step>
    +</Steps>
    +
    +The offer is narrow on purpose:
    +
    +- It names only the folder that holds the file Haruno tried to open.
    +- It never offers your whole user folder, a hidden folder, or a folder where programs keep their own data.
    +- If a folder is not allowed, the chat says **can't be shared with a chat**, and there is no button.
    +- The same folder is offered once per message.
    +
    +## A chat that will not start
    +
    +Before a chat starts, Haruno checks every folder the chat will use. This happens once when the chat starts, not for each message. It refuses to start if it finds something it cannot vouch for. The reason appears in the chat, and it is always in English.
    +
    +| What it found | What the message asks for |
    +|---|---|
    +| A **link to somewhere else** in a place Haruno owns | Remove the link and try again. |
    +| A file that has **more than one name** (a hard link) and the other name is outside the folder | **Remove the extra name, or open a project folder without it.** |
    +| More than about 1.5 million files and folders | **Open a smaller project folder.** |
    +| More than 1,024 links in the folder | **Open a project folder with fewer links.** |
    +
    +A hard link means one file that shows up under two names in two places. A link means a shortcut that leads to a different folder.
    +
    +An ordinary code or documents folder is well inside these limits, built folders included.
    +
    +<Callout variant="info" title="A big folder can take a moment">
    +While Haruno checks a very large folder, the chat shows its usual sending state. There is no separate progress message.
    +</Callout>
    +
    +<Callout variant="tip" title="What to tell a customer">
    +Keep each chat on the folder it needs. If a chat says it cannot reach a folder, add that folder to the project instead of copying files around.
    +</Callout>