Help CenterFeaturesGuide (overview)
Guide (overview)
Features

Guide (overview)

This page first explains what QU Studio is and what it looks like, then lists every help page by feature.

New here? Start with Where to start. For habits that make it easier to use, and how to tell Q about specific things, see Best practices.

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

What QU Studio is

QU Studio is a workbench on your own Mac. It has AI coding assistants (agents, like Claude Code or Codex) write code for you.

You only look after three things: saying what you want, making the calls, and accepting the work. Splitting up the work, starting it, keeping track, chasing, retrying and merging code are left to the system and Q.

The work is done by agents you installed and signed in to yourself on your computer, and usage counts against your own account. QU Studio has no built-in model, doesn't install agents for you, and never handles your account. See Install & sign in to agents.

A few words first

WordIn one sentence
QYour project assistant. You tell Q what you want; Q turns it into tasks, hands them out, keeps track, and calls you when you need to decide. Q doesn't write code itself.
SessionA conversation with an agent. Sessions are what actually write code and change files. A session usually does one thing.
TopicA place to talk with Q about one thing. For example, open a topic for "build the login page", and the whole story of that work stays in it.
Discussion topicA topic for talking only, not building. While an idea isn't settled, talk it through here first, then build once you've reached a conclusion.
TaskOne item on the board: what to do and how to tell it's done. Q or you create it; a session does it.
AcceptanceWhen a session finishes, you take a look to see if it's right. If it is, click "Done"; if not, click "Send back" and say what's wrong.
PrototypeWhat the UI should look like, drawn first and built only after you approve it. The finished work is compared against it; when accepting, you look at side-by-side screenshots.
VersionA batch of changes collected and shipped together, like 0.5.0. Common for projects that have to be packaged and released, like apps.

A few more words come up in these pages:

  • Main (mainline): the "official" copy of the project's code (usually called main). Changes only go into main once the task is accepted.
  • Workspace: a separate copy of the code made for one task, so several tasks can run at once without getting in each other's way.
  • Main computer: the computer where Q lives. The board, memory and project list are stored on it. If you only have one computer, it's that one.

The window at a glance

  • Left sidebar: at the top are "Q", "Task board · all projects" and "Versions"; below are your projects, with their sessions and topics listed under each. Running sessions have a spinner; ones waiting for you have a yellow badge. The "+" next to a project opens a new conversation. Computers, usage and settings are at the bottom left.
  • Middle: the session, board or page you're looking at.
  • Right panel: this project's prototype (⌘\ opens and closes it).
  • Search: ⌘K searches sessions, tasks and projects, and can also jump straight to the task board, Needs you, or Settings.
  • Tell Q something: press ⌃⇧Q in any app, and a small box pops up at the top of the screen. Type a sentence and press Return to send it to Q.
  • Approve things from the corner of the screen: when a session needs your OK or your call, a small box pops up at the bottom right of the screen; one click is enough. See Q.
  • Common shortcuts: ⌘N new conversation, ⌘J Needs you, ⌘B collapse the sidebar, ⌘, Settings. The full list is under Settings › About › Help › Keyboard shortcuts.

Two ways to work: hand it to Q, or look after it yourself

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

  • Hand to Q: opens a topic. Q splits up the work, opens sessions and keeps track. Good for things that take several steps and belong on the board.
  • I'll look after it: opens a session that you talk to directly, just like using Claude Code or Codex on their own. Close it when the small job is done; it doesn't go on the board.

You can switch either way at any time: in a session you're looking after, just say "hand this to Q"; in a session handed to Q, click "Take it back" and it's yours.

How each part works

PageWhat it covers
QTelling Q things, how Q splits and hands out work, checking work when it's handed in, Needs you, morning brief and weekly report, letting go
Board & tasksThe four-column board, creating tasks, handing them out, taking them back, dependencies, what you can see in a task
TopicsWhen to use the main chat, topics and discussion topics; how to branch off, merge back and end topics
SessionsOpening a session, choosing model and permissions, chiming in while it runs, seeing changes, forking and rewinding, taking over in a terminal, Done
Helpers & subagentsSessions bringing in helpers to work in parallel, a second check from another agent, read-only reviews, helpers on another computer
Sessions working togetherSessions messaging and waiting for each other, working together across projects and computers
Prototypes & acceptanceConnecting, changing and finalizing prototypes, the prototype-first flow, how to accept work
Versions & releasesThe versions page, version branches, changelog drafts, shipping with one sentence
Usage & quotaHow much quota is left, where it went, model presets, picking a model for the job, what to do when quota runs out
Multiple computersConnecting other computers, which one the work lands on, what happens when a computer sleeps
MemoryWhat Q remembers, how to see it, how to forget it, writing it into the repo
Scheduled tasks & incoming workHaving Q do things on a schedule, watching places like GitHub for new activity
SettingsProject settings, app settings, running with the window closed, updates, exporting data, when something goes wrong

Also: Install & sign in to agents, Self-hosted relay.