Files, Library, and Workspaces

Rudder uses a few file locations because source material, working files, and finished output need different treatment.

​

Where files belong

Project resources are a curated starting set, not permission to read every file in the organization.

​

Example: prepare a client brief

Keep the client’s approved source notes in Library and add only the relevant ones to the project. Let the Agent work in the project repository. Save the accepted brief back to Library and link it from the Chat or review Issue. The next Agent can now find the approved result without inheriting every scratch file from the first attempt.

​

A simple rule

• Input you want to reuse: Library or project resources
• Files the Agent may change: project or Run workspace
• Final result: keep it linked to its Chat, Issue, Run, or project
• Temporary scratch files: do not promote them to Library by default

On a standard local Desktop setup, organization files live in a mapped folder under ~/Documents/Rudder.

​

Safe recovery

Agent instructions, managed Skills, credentials, and cache folders are not ordinary Library files. If a mapped organization folder disappears, restore it or use a backup; do not create an empty replacement and assume the data is safe. Inspect a backup before restoring it. Rudder creates a safety backup first. Open work can prevent a Run workspace from being archived until its dependent Issues are closed or moved. For exact locations and platform behavior, see Workspace boundaries.