Location lookup
| Location | Purpose | Typical content |
|---|---|---|
| Library | Durable files people and future Agents should find | briefs, notes, accepted reports |
| Project resources | Selected starting context for project Runs | a few relevant Library files or links |
| Project workspace | Folder or repository where project work happens | source code, website, working documents |
| Run workspace | Exact filesystem/branch used by one Run | that Run’s changes |
| Agent home | Managed state for one Agent | instructions, memory, Skills |
| Workspace backup | Saved organization workspace version | files for inspection or restore |
| Temporary storage | Short-lived scratch data | downloads, caches, intermediate files |
~/Documents/Rudder. Renaming the organization does not silently move its
folder.
Rules that prevent accidental context leaks
- A project Run receives selected project resources, not every Library file.
- Agent instructions, Skills, credentials, and caches are not ordinary Library content.
- A produced file should remain linked to its Chat, Issue, Run, or project.
- Browser and server deployments cannot use Desktop file-open actions to gain arbitrary local application access.
Restore and archive safely
- A missing mapped organization folder is a recovery problem. Restore it or use a backup; do not replace it with an empty folder.
- Inspect the chosen backup before restore. Rudder creates a safety backup first.
- A Run workspace cannot be archived while open Issues still depend on it.
- When editing a file reports a stale version, compare both versions before choosing which one to keep.
Examples
- Put approved customer notes in Library; select only the notes needed for the current project.
- Let a coding Agent modify the project workspace, and keep its branch or isolated folder on the Run.
- Link the final report from the review Issue instead of leaving it only inside the transcript.