Help CenterFeaturesQ
Q
Features

Q

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

What it is

Q is your project assistant. Q is the only one in QU Studio.

  • You tell Q what you want. Q creates tasks, puts them in order, and opens sessions to do them.
  • When a session finishes, Q looks it over for you first, then calls you to accept it.
  • For things that need your call, Q screens them first: Q decides what it can, and comes to you with a suggestion for what it can't.

Q doesn't run commands or change files itself. This is fixed by the system; all the work goes to working sessions.

When to use it

  • Something takes several steps, or belongs on the board, or should be written down: hand it to Q.
  • You want to know how things are going, or what needs you today: ask Q.
  • You have several projects going at once: see them all in one place with Q.

For changing a line or two, or asking a question, it's quicker to open a session yourself and just say it. See Sessions.

How to use it

Tell Q about something

Click "Q" at the top of the left sidebar to go to the main chat, and say what you want. For example:

What to say

"Show order times in the order list in local time, like 'Nov 21, 16:30'. Both the list and the details page should be right."

Q creates the task (one item on the board) and opens a session to do it. For a specific piece of work, Q opens a separate topic to follow it. See Topics.

When you say it:

  • Start with the result you want, then say how you'll know it's done (this is called acceptance criteria).
  • You usually don't need to say how to build it; leave that to the session.
  • If you have something to go on, include it: paste screenshots straight in; send web pages, tweets or video links straight over, and Q reads them. Q can't read pages that need logging in, and will say so; paste the text or a screenshot instead. For videos, Q only reads the title, description, cover image and subtitles; it can't see the picture or hear the sound.

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, without switching back to QU. You can paste screenshots. Esc hides the box, and anything you didn't send is still there next time. (You can change the key combination under Settings › General › Tell Q something.)

How Q splits up and hands out work

  • Small jobs get done directly, without splitting.
  • Anything that changes the UI gets a prototype first. Once you finalize it, it goes to a session to build. See Prototypes & acceptance.
  • Big jobs are split into several tasks, in order. When one is done, the next starts automatically.
  • Finding a bug, reviewing a PR (code changes someone else submitted), and a CI failure (the repo's automatic checks didn't pass): for these three, Q includes how to go about it. For a bug, when the cause isn't clear or the change is big, the session hands you a plan first. A PR review posts no comments on GitHub without your OK. A CI failure first works out whether the code is broken, the test is flaky, or it's the environment, and only fixes it once you agree.
  • Who gets it and which model: Q picks by the "When to use" line written for each "Model preset": a cheap one for text changes, a strong one for big changes. See Usage & quota.

If you say "do it now", Q hands it out right away, without you clicking again. If it can't be handed out (say, that computer can't be reached), Q tells you why on the spot.

Looking work over for you first

When a session finishes, Q checks it first: whether all acceptance criteria are met, whether tests passed, and how much changed. Q writes "suggests accepting" or "suggests sending back" on the task, with the reason. Q doesn't accept for you; it only suggests.

(This is called "Check work when it's handed in", and you turn it on or off in Q › Settings.)

When you want to send something back, you can just tell Q: "Send QS-13 back, the button should be at the bottom right." (QS-13 is a task number; every task has one.) Q passes your notes to the original session to keep working. If you only say "suggest sending it back", Q only notes the suggestion and doesn't actually send it back.

Needs you

Everything you need to approve, answer or accept is gathered on the "Needs you" page (⌘J).

  • At the top is one line of advice, like "2 of these 5 are blocking others, handle those first; 3 can be accepted together".
  • Below, they're grouped: blocking others, can be accepted together, has a deadline, not urgent.
  • The ones Q suggests accepting can be accepted together, all in one click.
  • "One by one" shows one item per screen, with the keyboard: A approve, R send back, → skip.
  • You're only asked about the same thing once at a time. If a session carries on by itself and no longer needs your answer, the item is cleared automatically with the reason.

Things you need to approve also pop up as a small box at the bottom right of the screen ("Q needs you"). Click "Allow / Decline" or pick an option, without switching back to QU.

  • Several items share one box; when you finish one, the next appears. You can also click "Later".
  • The box doesn't take the keyboard, and Return can't approve anything, so you don't approve by accident.
  • Deploying, deleting data and spending money are marked red, and "Allow" needs two clicks.
  • It doesn't pop up while you're watching that session in QU, or when you've been away from the computer for a while; you get a notification instead.
  • With several computers connected, it pops up on the one you're using.

(Change where it pops up, and whether it does, under Settings › Notifications › How approvals alert you.)

Morning brief and weekly report

  • A morning brief at 08:30 on weekdays: what's blocking others, projects with progress, and what needs you; what got done overnight is listed separately at the start. A weekly report at 17:00 on Fridays: what got done last week, and this week's focus.
  • Both go in Q's "Morning & weekly briefs" topic.
  • If the computer was asleep and missed one, it's sent when it wakes, saying what time it was due and why it's late.
  • To change the time, just tell Q "move the morning brief to nine".

Each brief and report is an extra round for Q, using your own account.

Quiet: only calls you when it should

  • Proactivity has three levels: Quiet (only comes to you when you need to decide, no morning brief or weekly report), Balanced (default), and Proactive (also flags risks and offers suggestions).
  • Do not disturb: 22:00–08:00 by default. No notifications pop up during that time; they're combined into one when it ends. Production errors, failed deploys, possible data loss and possibly leaked keys still reach you.
  • When you come back after being away from the computer for a while, you see a recap: who finished, who stopped with an error, and what's waiting for you.

(Change proactivity and the times in Q › Settings.)

Letting go bit by bit: "Things you don't need to ask me"

At first you're asked about everything. Once you're comfortable with a kind of thing, you can let Q decide it for you from then on:

  • Say "don't ask me about these", or agree several times in a row, and Q offers to note it down.
  • Each item noted says where it came from and how many times it's been let through for you, and you can revoke it any time. (In Q › Settings › Ask you first?.)

Commands sessions run can also be opened up one kind at a time. There are these kinds: looking at files, installing dependencies from the lockfile, running tests, running builds, formatting and linting, and starting a local preview. Once you've allowed a kind once in a project, the next approval card has an extra checkbox: "Don't ask me about this kind again". You can also tell Q "don't ask me about running tests in this project".

  • Commands with other things chained in, that go online, that reach outside the project folder, or whose config was changed are still asked about.
  • Opening up running tests or running builds means letting the test and build code the session writes run on your computer. Think it through before you tick it.
  • When a session has "Allow everything" on, it asks nothing, and these rules don't apply.

A few kinds always need your OK, and Q can't let them through for you: usage, security and credentials, deploying, spending money, deleting data, acceptance, and anything sent out that can't be taken back (like posting a comment on GitHub).

Everything Q does on your behalf (accepting for you, closing tasks, changing rules) has to quote your own words, typed by you, and leaves a line in the chat that you can undo.

Other things

  • Changing the name and look: at the top of Q's page you can give Q a name and pick a look, or upload your own picture.
  • Sorting saved-up ideas once a week: when ideas pile up in "To do" on the board, Q sorts them for you once a week: which to do first, which can be merged, which to put aside. Nothing changes until you agree.
  • Tidying up old sessions for you: sessions whose work is all accepted and that haven't been touched for over a day are collected in the morning brief, and Q asks whether to close them. Running sessions, and ones with uncommitted changes, are left alone.
  • Q's own quota runs out: you can wait until it resets, or switch to the other agent and keep chatting. The conversation and memory carry over, and you can switch back later.

FAQ

Can Q change code directly? No. Q only coordinates; all the work goes to sessions. This split is fixed by the system, not by instructions.

Will Q ship or deploy on its own? No. Shipping only starts when you say something like "ship 0.5.0"; deploying, spending money and deleting data are always asked about first.

What if Q asks too much? Set proactivity to "Quiet"; once you're comfortable with a kind of thing, say "don't ask me about these".

What if Q misreads what I said? Correct it right in the chat. The preferences Q noted can be changed or deleted in "Memory". See Memory.