​
Completed state

At the end of this guide, a client-brief project has a primary project workspace, a small set of curated resources, a durable brief in Library, a link from its review Issue, and a workspace backup that the operator can inspect.

​
Prerequisites

Prepare the project’s repository or folder, the source notes that should be eligible for project-linked runs, and the expected final output. Use Workspace boundaries to decide what belongs in Library, a project workspace, an Agent home, or temporary storage.

​
Set up the client brief

  1. Open the project workspace settings and add the repository or folder. Make it primary if project-linked runs should use it by default.
  2. Add the durable source notes to Library. Do not place Agent instructions, managed Skills, caches, credentials, or scratch output in ordinary Library paths.
  3. Attach only the notes needed for this brief as project resources. Add a role or note that tells the Agent why each resource is relevant.
  4. Run the client-brief Issue. Confirm the Agent Run resolves the project workspace and curated resource references rather than every organization file.
  5. Save the accepted brief in the project’s Library folder and link it from the review Issue as the produced output.
  6. Open the file from Chat, Messenger, or the Issue. Use the Side Panel for supported inline previews and Markdown editing, or Open in Library for the full work surface.
  7. Create a manual workspace backup and open the resulting version to inspect a file before relying on it for recovery.
On Desktop, file-open and containing-directory actions use validated local bridges. They are conveniences for the operator and do not broaden the Agent’s workspace or expose local apps to a browser deployment.

​
Success signal

The project shows one intended primary workspace and only the selected starting resources. The final brief opens from Library and from the review Issue, while the Agent Run records its workspace context. The manual backup appears as a concrete inspectable version.

​
Recovery

If a mapped organization folder is missing, stop and restore the recorded folder or use a workspace backup. Do not create an empty replacement at the mapped path. If a Markdown edit reports a stale-write conflict, keep the local draft while comparing it with the latest server content; choose Keep mine or Use latest deliberately. Before restoring a backup, inspect the selected version and understand which files will change. Rudder creates a pre-restore safety backup. A Run workspace cannot be archived while open Issues still depend on it; close or move those dependencies first.