Haruno prepares the whole folder a chat works in, so it refuses folders that are far too broad, such as a whole drive or the user folder, and asks first about very large ones.
Mac appNot availableThe Mac's check applied to the one open folder, which Projects replaced. A folder linked to a project is not checked.
Windows appAvailableAdding a folder to a project as a source does not check its size.
Haruno prepares the whole folder before a chat can answer in it. A small folder costs nothing. A very large one makes every chat slow to start. The user folder, or a whole drive, would be far too much. So Haruno has two limits.
The limits
Kind of folder
What Haruno does
Too broad: a whole drive, the user folder, AppData, Windows, or Program Files, or a folder that holds one of them
Refuses it. No size makes these appropriate.
Very large: at least 200,000 files and folders, or too many to count in 5 seconds
Says what it will cost and asks you to decide.
The folder the Portfolio's books were moved to, or a folder that holds it or sits inside it
Refuses it, so a chat can never write over the books.
An ordinary project folder, even a big software checkout, is well under the large limit. A folder with all its downloaded packages can go over it.
What you see
Too broad. A message titled That folder is too broad says: "Haruno can't use (the folder's path) as a project folder. Open the folder of a single project instead — not a whole drive, your user folder, AppData, Windows or Program Files."
Very large. A message titled That's a very large folder says the folder holds at least that many files and folders, and explains: "Haruno prepares the whole folder every time a chat starts, so each chat would spend a minute or more getting ready before it answers, and the file and source-control views would be slow. Opening a smaller folder — one project rather than everything above it — avoids all of that. Use this folder anyway?" You can cancel, or choose Use it anyway.
The books. A message titled This folder holds the books says the folder holds Haruno's books or is part of them, so it cannot be the project folder, and asks for another.
In a chat. If a chat is started in a folder that is too broad, it answers with: "This folder is too broad to use as a project folder: (the folder's path). Open the folder of a single project instead — not a whole drive, your user folder, AppData, Windows or Program Files."
Sharing a folder with a chat. When a chat in a project cannot reach a folder, it offers Share this folder…. Haruno shows the full path and says "The chat will be able to read and write this folder." A folder cannot be shared if it is too broad or very large, if it is outside the user folder, if its path has a folder whose name starts with a dot, if it is reached through a link, or if it is one of the places where programs keep their data. The chat then says "(the folder's path) can't be shared with a chat."
Adding a source does not check the size
When you add a folder to a project with Add source ▸ Choose folder, Haruno does not check how big it is and does not show these messages. A very large folder can be linked. The slowness shows later, when a chat uses it. Tell customers to link the folder of one piece of work, not a drive or their user folder. See Project sources.
Other places where size matters
The @ list in the message box looks at up to 20,000 files and folders. In a larger folder, a file may not be found by name.
The Source control view shows up to 10,000 changed files. Past that it says how many it is not showing: "Showing the first 10,000 changed files. 250 more are not listed, because this folder holds more changes than the panel can show at once." (the numbers are examples) See Source control.
What to tell a customer
Link the folder for one project. Do not link a drive, the user folder or AppData.
A folder with downloaded packages inside it (for example a software project with all its dependencies) can be very large. Link the part that matters.
If a chat will not start in a folder, the message names the folder and says what to open instead.