oracle

To bundle repository files with a prompt for code investigation, specify file selection patterns like globs and includes to attach high-signal code directly to your question. This provides context-rich, one-shot answers by ensuring the model reasons using real repository context.

Diagnosing failing tests using repository context is best achieved by bundling your diagnostic prompt with the exact source files needed. Use file globs to include relevant code and exclude tests, reducing missing context back-and-forth for a direct, one-shot analysis.

Yes, you can preview token spend and file attachments before sending a large codebase by using a dry-run preview. This feature safely handles large files by showing exactly what will be bundled, ensuring token spend awareness before generating the final prompt.

Prompt bundling supports reattaching to long-running browser sessions for codebase summaries. It stores browser sessions so you can reattach to previous investigative contexts instead of re-running the entire file selection and bundling process from scratch.

To exclude files when attaching repository context to a prompt, use negated file glob patterns alongside standard includes. The system respects .gitignore rules and applies deterministic file attachment rules, allowing you to attach only the highest-signal files for your investigation.