Settings
What it is
QU Studio's settings are in three places:
| Where | What it covers |
|---|---|
| Project settings (the project's "⋯") | Each project has its own: flow, prototype, dev build, scheduled tasks, watch list… |
| Q › Settings (the last item in the row at the top of Q's page) | Q's name and look, proactivity, morning brief and weekly report, whether to ask you first, models, memory |
| App settings (⌘, or the bottom left) | Language and appearance, notifications, computers, agents, about |
This page also covers: adding projects, running with the window closed, updates, notifications, exporting data, and when something goes wrong.
When to use it
Most settings don't need touching; the defaults work. The ones people usually change:
- Connecting a prototype or registering a dev build for the first time: project settings. See Prototypes & acceptance.
- Q is too noisy or too quiet: Q › Settings.
- Changing models or adding presets: Settings › Agent. See Usage & quota.
How to use it
Adding a project
"Add project" in the left sidebar:
- Open a folder on a computer: pick a code repo folder (ideally a git repository). You can also drag the folder straight into the left sidebar.
- Clone from Git: clones with your own git and your own sign-in, without overwriting any existing folder.
The project is named after the folder, and you can rename it. "New project" and "Import a Qu Design prototype" aren't ready in this version yet.
The All projects page shows every project's status, its unfinished tasks, and which computer it's on, all on one page.
Project settings
In the project's "⋯" you can rename it, change its icon (it looks for the website icon in the code repo automatically), change the task number prefix, pin, archive, mark it as a client project, or "Pause this project" (set it aside for now: no new tasks are scheduled, and the watch list and watchdog stop). Archived projects can be restored in "All projects".
Project settings also has these:
| Item | What it covers |
|---|---|
| Rules | How requests flow, which steps Q and the prototype session can check for you, "Ships as soon as it's merged". See Prototypes & acceptance, Versions & releases |
| Q accepts | Accepts small changes for you when they're done and every condition holds. See Prototypes & acceptance |
| Prototype | Connect a prototype |
| Run & preview | Register the dev build's start command |
| Which machines | Which computers have their own copy of this project's code |
| Computers and agents to hand work to | Which "computer + agent" pairs this project can hand work to, and which is the default. See Multiple computers |
| Checks | Register checks like pnpm test; once approved, they run with one click in a task |
| Data sources | Register a local database on the project's computer (only SQLite for now), for agents on another computer to query read-only |
| Watch list | See Scheduled tasks & incoming work |
| Scheduled tasks | Same as above |
| Push each turn to the task branch | After every turn, push the existing commits to the remote, so another computer can carry on if this one goes offline |
| Link local env files like .env into workspaces | When a separate workspace is opened, link config files not in git, like .env, so the project can run; it only creates links and never reads the contents |
| Workspace auto-cleanup | When to clean up the code copies left by tasks that were merged. Before you turn it on, it lists how many it'll clean, how big they are, which are kept, and why |
| Write project conventions into the repo's AGENTS.md | See Memory |
When workspaces are cleaned up, files not in git that can't be regenerated (like .env.local, or handwritten notes) are kept. When you click "Clean up", it first lists what will be deleted along with it. Branches that haven't been merged are never deleted.
Q › Settings
Q's look, name, proactivity, morning brief and weekly report and Do Not Disturb, whether to ask you first, incoming work, models, memory, and the "Tell Q something" shortcut are all changed here. See Q.
App settings
| Section | What's in it |
|---|---|
| General | Language, appearance (light / dark / follow system), text size, chat width, what to open to, what you send while a session is running, process in sessions, carry on automatically when quota is back, how many times sessions can go back and forth after you say something, clean up a task's code copy when it's done, the "Tell Q something" shortcut |
| Notifications | Desktop notifications, notification sound, how approvals alert you, bypass Do Not Disturb for must-know-now alerts |
| Q | One line that takes you to "Q › Settings" |
| Memory & privacy | Keep client projects separate, don't remember health, politics or religion by default, tidy memory when idle, model for tidying memory, export data |
| Computers | After closing the window, start the background service at login, keep this computer awake while sessions run, let other computers open this one's terminal, relay servers |
| Agent | Model presets, the Claude Code / Codex detected, more agents, guess my next message, naming tasks automatically, and the models they use |
| About | Version, automatic updates, data folder, roll back to previous version, getting started, help, third-party licenses |
Running with the window closed
Sessions don't run in the window; they run in the QU background service on each computer.
- Closing the window or updating the app doesn't interrupt sessions.
- While the window is closed, QU in the menu bar shows running sessions, lets you handle approvals, and can "Pause all".
- When you quit the app, you're asked: "Just quit; sessions keep running", or stop this computer's sessions too.
- While sessions are running, the computer won't fall asleep by itself when idle; once all sessions stop, it sleeps as usual.
- Closing the lid or choosing Sleep still puts it to sleep. While asleep, sessions pause, and they carry on when it wakes. To keep work running with the lid closed, hand it to a computer that's always on. See Multiple computers.
(These options are under "Settings › Computers" and "Settings › General".)
Updates
- New versions are checked for automatically. Once one is downloaded, a card appears at the bottom left listing what's changed in this version, and you can "Restart and install". If you don't click it, it installs the next time you open the app.
- While sessions are running, you can see which ones are still running, and choose not to install yet.
- A backup is made automatically before upgrading. If something goes wrong after upgrading, you can "Roll back to previous version" under "Settings › About".
- Updates come from the
gavinguo521/qustudioreleases page on GitHub. If GitHub can't be reached, check your network or proxy; QU Studio never changes your network settings.
Notifications
- System notifications are sent by the app, and pop up even when the main window is closed. Clicking a notification opens the matching session, topic or Needs you.
- The "Needs you" count on the desktop, the small box in the screen corner, the board and the Dock icon is the same number.
- If there are too many notifications within an hour, the rest are held and shown together when you next speak up.
Exporting data
"Settings › Memory & privacy › Export data › Export…" packs memory, the board, session records and settings into one ZIP: JSON and Markdown inside, plus a readme. Work carries on as usual while it exports.
- Not exported: code (it's already in your code repo), and the agents' sign-in credentials (QU never reads them).
- Anything in conversations that looks like a key is masked (common keys, private keys, connection addresses with passwords, and the values after "password / token"). It goes by format, so anything written too loosely may not be caught; check it yourself before sending it to anyone.
- All data is on the main computer, so it can only be exported there.
Help
"Settings › About › Help": the Guide, Where to start, and installing and signing in to agents open in the browser; Keyboard shortcuts, What's new in this version, Run onboarding again, and Open logs folder open right in the app.
When something goes wrong
- Check the connection: on the "Computers" page, a computer that can't connect shows step by step where it breaks and what to do, with "Copy diagnostics".
- Version info: click the version number under "Settings › About" to copy the full version info, and paste it in when you report a problem.
- Logs: in the
logsfolder of the data folder, usually~/Library/Application Support/QuStudio/logs. "Settings › About › Help › Open logs folder" opens it directly.
FAQ
Where is my data stored? The board, memory and conversations are all stored on your own main computer, not on our servers. Code is in your own code repo.
Can I roll back to the previous version? Yes, under "Settings › About".
What if I change a setting by mistake? Most settings can be changed back any time. Project rules Q changed for you show who changed them and when, and can be undone.