---
id: MAC-4
title: Files on this Mac
group: On the Mac
summary: Keep your setup as plain files in a folder you choose, so any agent on your Mac can read and edit it safely
keywords: [files, folder, mirror, claude code, agent, streamliner folder, disk, edit, json, agents.md]
---

Your streamlines, themes and settings can also live as ordinary files in a folder you choose, such as **Streamliner** in your home folder. Any agent on your Mac (Claude Code too) can read them and edit them; the app watches the folder and checks every edit. It is off until you turn it on.

## Turning it on

Open **Settings → General → Files on this Mac** (or answer the Concierge's offer) and choose **Keep Files in ~/Streamliner (Recommended)**. The folder panel opens at your home folder: if *Streamliner* is already there it is chosen for you, so click **Choose**; if not, click **New Folder**, name it *Streamliner*, then **Choose**. macOS asks for that one click so the app may write there. **Choose Another Folder…** picks any other place. The app never keeps these files in its own container, where other tools would have to ask macOS for permission. **Show in Finder** opens the folder; **Turn Off** stops writing there (the files stay).

## What is in the folder

- *personal/*: one file per streamline (name.streamline.json), *settings.json*, *themes.json* and *order.json* (the order of your streamlines in the sidebar). *status.json* lists which servers you are signed in to and whether a model key exists, never the key itself.

- *AGENTS.md*: what the folder is and the rules, for agents. *CHANGES.md*: anything waiting for you.

- *.streamliner/*: the app's own copies of the guide and schemas agents need, and the history of saved changes.

- A folder per organization you own or administer, once you have staged something there: the staged files, a *CHANGES.md* listing them, and, on a device an owner approved for publishing, the organization's private setup under *private/* (kept out of Spotlight). When the organization changed a file you also changed, its version sits beside yours with *.server* before the extension; delete it to keep yours. These are copies to read: change the organization's setup in the Library, and publish it from there (see Publishing from the app, AD-5).

There are never keys in these files.

## When something edits a file

- A change to names, welcome text, cards, quick phrases, colors or settings is applied within a second.

- A change that widens access waits for your tap: a new server address, a tool that would run without asking, a tool no longer hidden, a new image host, a new or removed streamline. A card in the corner of the window shows what would change; **Apply** or **Keep as it was** (the file is put back).

- A file with a mistake is not applied: the last good version stays and a note says what is wrong.

- A file containing something that looks like a key is never applied. Remove it, and rotate that key where it came from.