This example gives an Agent the right files for a client brief without exposing every file in the organization.

​
What you will set up

A project folder, a small set of source notes, a final brief saved in Library, and a backup you can inspect.

​
Before you start

Prepare the repository or folder where the Agent may work, the source notes it needs, and the result you expect. Keep credentials and private unrelated files outside the selected context.

​
Set up the project

  1. Open the project and add its repository or folder as a workspace.
  2. Make it the primary workspace if project-linked Runs should use it by default.
  3. Add durable source notes to Library.
  4. Add only the notes needed for this brief as project resources. Describe why each resource matters.
  5. Ask the Agent to create the brief. Open the Run and confirm it used the intended workspace and selected resources.
  6. Save the accepted brief in the project’s Library folder.
  7. Link the brief from its Chat or review Issue.
  8. Open the file in the Side Panel for a quick preview, or choose Open in Library for the full file view.
  9. Create a manual workspace backup and inspect one file in the saved version.

​
Check the result

The project should show one intended primary workspace and only the resources you selected. The final brief should open from Library and from the task that produced it. The backup should appear as a version you can inspect.

​
If files are missing or out of date

  • If the mapped organization folder is missing, restore the original folder or use a backup. Do not create an empty replacement.
  • If Markdown changed while you were editing, compare your draft with the latest version before choosing which one to keep.
  • Inspect a backup before restoring it. Rudder creates a safety backup first.
  • Close or move open Issues that still depend on a Run workspace before archiving it.
See Workspace boundaries for exact locations.