Fabricator

Files and folders

Where Fabricator keeps your projects, app data, chat history, Advisor reports, logs and caches on Windows and macOS.

Fabricator keeps app state separate from your Rayfin project files. Project folders are the code you build. App data is Fabricator's local state, logs, cache, and saved UI data.

App data folder

OSApp data folder
Windows%APPDATA%\Rayfin Fabricator
macOS~/Library/Application Support/Rayfin Fabricator

Fabricator creates this folder when it needs to save app-owned files.

What is in app data

PathWhat it containsSafe to delete?
studio.jsonSettings, the workspace folder path, recent projects, active project, and team workspace list.Yes, but Fabricator forgets settings and project lists. It does not delete the project folders.
chats/Saved chat history, one JSON file per project.Yes, if you no longer need chat history.
advisor/Saved Advisor reports and Advisor UI state for projects.Yes, if you are comfortable losing saved findings, dismissals, and baselines.
suggestions/Cached starter suggestion sets for projects.Yes. Fabricator can recreate suggestions.
logs/Diagnostics JSONL files, exported diagnostics bundles, and crash or hang logs.Yes, if you no longer need them for bug reports.
fabric-accounts.json, fabric-accounts/The Fabric accounts you added after the first, each in its own Rayfin CLI config folder, and which one is in use.Only to sign out of those accounts. Use Accounts instead; see Manage your accounts.

Diagnostics files older than the retention window are pruned at startup.

Workspace folder

New Rayfin projects are created in the workspace folder. The default is RayfinProjects in your home directory.

Change it from Settings → Workspace folder → Change…. Changing the workspace folder affects new projects. It does not move existing project folders or delete anything.

Your workspace folder contains the actual app source code, git repository, Rayfin files, package files, and any app assets. Do not delete a project folder unless you mean to delete that app's local working copy.

Temporary screenshots

Fabricator stores temporary screenshot attachments under the operating system temp folder in a rayfin-fabricator-shots directory. It deletes the screenshot files it owns after they are no longer needed.

Credentials

Fabricator does not store Copilot, Azure, or Rayfin credentials in studio.json. Those credentials are owned by the tools and services that sign you in, such as the bundled Copilot engine, Azure CLI, GitHub CLI, Rayfin CLI, and platform credential stores.

What to keep for bug reports

If you are reporting a problem, keep the logs/ folder until after you export diagnostics or attach the requested files. If Full diagnostics was enabled, review the export before sharing it because it can include prompts, responses, and tool output.

Something wrong on this page?Edit this pageReport an issue with this page

Fabricator is a personal project by Sachin Patney. It is not a Microsoft product and is not affiliated with, endorsed by, sponsored by, or supported by Microsoft.

GitHubMIT LicenseReleasesYouTubeDocumented for Fabricator 1.20.1

On this page