Choose files and context

Before you begin

• A local project you can access and an Agent for this task.
• Permission to share the particular information you select with the disclosed processing provider.
• Current connector context if the task refers to a native model.

Follow the steps

1. Link only the local project you need

   Create or link an explicitly chosen local folder. Linking a root grants scoped access; it does not recursively index or upload that folder. UNC/network roots are unsupported.

   Checkpoint: The intended local project root is visible and accessible.

2. Select task-specific attachments

   Attach only the needed text, text-bearing PDF or images. The design permits at most eight selected files and 50 MiB total.

   Checkpoint: Each chosen item appears explicitly; unrelated descendants and another Agent's history have not been silently included.

3. Check each format and size

   Use UTF-8 txt/md/csv/JSON up to 5 MiB each; text-bearing PDF up to 20 MiB and 200 pages; PNG/JPEG/WebP up to 10 MiB and 16 megapixels each. Read extraction errors.

   Checkpoint: Unsupported, encrypted, scanned-only or oversized required content is resolved before dispatch; no OCR or hidden embedded action is promised.

4. Use CAD through the selected connector

   For a CAD model, choose the current host/document metadata reference and bounded inspection. Do not treat a .3dm or .rvt file as an attachment for raw model upload.

   Checkpoint: The context identifies the intended native document with a fresh binding.

5. Review included and excluded content

   Open context review. Inspect selected files, instructions, available history, omitted material, provider/model profile and estimate. Remove anything unnecessary.

   Checkpoint: The preview makes data leaving the device explicit; removing an attachment changes the request without deleting the original file.

6. Refresh changes before sending

   If a selected file changed, moved or lost permission, refresh that item or remove it intentionally. Review the new snapshot before Send.

   Checkpoint: The dispatched snapshot is frozen with source identities. Later edits affect future requests, not a payload already sent.

Check the result

• The next request uses a reviewed finite snapshot with disclosed included/excluded information.
• No folder index, cross-Agent memory, OCR or full CAD upload is implied. Lower model input/token ceilings can further limit accepted content.

If something goes wrong

• A removable drive or selected file is unavailable.

  Reconnect the intended drive or relink the known root without deleting the project. Resolve the required item before a charged run.

  Resume from: Accessible intended root and refreshed item.

• Extraction fails or history exceeds the budget.

  Read the stated omission. Supply permitted text or reduce the selection; any model summary must be disclosed rather than treated as hidden free processing.

  Resume from: Reviewed included/excluded preview.

• A file changes after review.

  Refresh and review a new snapshot. Do not assume the changed bytes are the ones already dispatched.

  Resume from: New versioned snapshot.

Continue with a related guide

• Choose a mode
• Choose native context
• Data boundaries
• Diagnostics are a separate selection