Why it matters
- Audit work is usually repeated across days, fixes, and follow-up questions.
- Project presets reduce setup time and make context generation more consistent.
- Saved selections help consultants and small teams keep review scope clear.
Workspaces
Workspaces preserve the setup around an audit or codebase so users can return to the same file selection, budget, output format, template, instructions, custom excludes, and explicit ignored-path includes.
How it works
- Save a workspace preset for a repository root.
- Store selected relative paths, output format, selected template, instructions, context budget, custom exclude patterns, and narrow include ignored paths patterns.
- Restore the preset when returning to the same audit or review stream.
- Update the preset as scope changes.
Example workflow
- Create a workspace for a product or client repository.
- Select core source files, tests, docs, and review notes.
- Set the output format, model budget, and audit template.
- Add custom excludes for local files that should not enter LLM context.
- Add include ignored paths only for dependency folders that the repository ignores but the review needs.
- Reuse the workspace for follow-up prompts or sponsor fixes.
Example workspace description
- Workspace: Client App Security Review
- Selected paths: src/core, src/integrations, test/invariants
- Output format: Markdown
- Template: Security review
- Budget: 64k
- Custom excludes: cache/, local-notes/
- Include ignored paths: vendor/reviewed-package/src/**
Limitations
- A workspace is a preset, not an access-control boundary.
- Missing or renamed files should be reviewed after repository changes.
- Include ignored paths can expose files hidden by ignore rules, so keep patterns narrow.
- Users should still inspect selections and scanner results before copy/export.
Build a repeatable context workflow.
Download the macOS app, review the docs, and contact support for Founder or Pro licensing during launch.