Help CenterGetting startedWhere to start
Where to start
Getting started

Where to start

First time with QU Studio: install the app, connect a repo, hand off your first job.

Q is the default name; you can rename it on its page, and the app uses the new name everywhere.

1. Install QU Studio

  1. Download QU-Studio-<version>-arm64.dmg from the QU Studio releases page on GitHub. Only Macs with Apple silicon are supported for now.
  2. Open the dmg, drag QU Studio into Applications, and open it from Applications. If you open it straight from the dmg, it can't update itself later.
  3. New versions download automatically; a card at the bottom left offers Restart and install.

2. First run

The first time you open it, a few short steps walk you through, and all of them can be skipped. The board, computers and settings in the sidebar are open to look around at any time.

First, get Q up and running: QU Studio checks whether Claude Code or Codex is installed on this computer and signed in. Any one is enough.

  • "Not found": install it following the official guide; see Install & sign in to agents.
  • "Not signed in": run claude auth login or codex login in a terminal and sign in with your own account.
  • Once it's installed and signed in, click "Check again".

The check only looks at whether these programs are installed and signed in. It never reads or saves your account files.

Meet Q: Q is your project assistant. He asks a few things: what to call you, what you usually build, and how proactive he should be. All optional; he'll pick things up as you chat, and you can always see and edit what he remembers.

Where to start: this version starts from a repo you already have, or from simply talking to Q.

3. Connect a repo

  1. In the sidebar, click Add project → Open a folder on a computer, or Clone from Git.
  2. Pick a code repository folder (ideally a git repo). The project name comes from the folder name and can be changed.
  3. The project appears in the sidebar. Its ⋯ menu lets you rename it, change its icon, pin it, or change the task ID prefix.

4. Hand off your first job

Click the "+" next to the project to open a New conversation, and first choose who looks after it:

Hand to Q (recommended for anything with several steps): say what you want, e.g. "add a dark mode toggle to the home page". Q opens a topic on this project, splits the work into tasks, puts them on the board and opens sessions to do them, calling you when there's something to decide. You can also click Q at the top of the sidebar and tell him directly.

I'll look after it (recommended for small jobs): say what to do and press Enter. You talk to the session directly, just as you'd use an agent like Claude Code or Codex on its own. You don't need a task; it closes when done and stays off the board.

Create it on the board: Sidebar → Task board → New task; write a title and description. It's noted as an idea in To do. Open the task and click "Let Q plan it", or "I'll do it".

Once a session is open, it's listed under the project in the sidebar; you can open it and chime in any time.

5. Accept the work

  • When a session is done, the task moves to Waiting on you, marked "Done · waiting for you to accept", and Q's chat gets a one-line note.
  • Open the task: the top of it is the acceptance view, with screenshots, tests and size of change; if Q has given it a first check, the suggestion is there too. Happy? Click Done. Not happy? Click Send back, say what's wrong, and the session keeps going.
  • For a session you look after yourself, you can also click Done or Won't do at the top of the session.
  • Q never decides on his own about things like deploys that write to the outside world and can't be taken back; he always asks you first. A deploy you hand to a session runs with the permissions you gave that session, and whether a session asks before running commands follows those same permissions.

Next