Just tell Q what you want.

QU Studio turns the coding agents you already use into a team.Q, your project assistant, plans the work, hands it out, keeps watch, and only calls you to decide and sign off.

Download for macOS
macOS · Apple siliconWindowsComing soonLinuxComing sooniOSComing soonAndroidComing soon

For indie developers, small teams, and anyone with something to build · Your own agents and account

One person. 10 days. 50+ releases.

QU Studio is builtwith QU Studio.

One person, with Q leading Claude Code and Codex, from the first line of code to the launch of this site:

Accepted in 4 days409tasksQ broke them down, handed them out and checked them.
On a typical day100tasksAbout this many accepted, day after day.
Two Macs, at once11sessionsUp to 11 agent sessions running at once; you make the calls.
On average, per day5releasesCounted from the very first version.
Tasks accepted per day
60Nov 18
108Nov 19
105Nov 20
126Nov 21

3,238 commits, 88% with an AI co-author credit
Figures from QU Studio’s own board and repo, as of Nov 2026.

Works with the agents you already use

Claude CodeCodexAgoragenticAmpGoogle AntigravityAuggie CLIAutohand CodeBobClineCodebuddy CodeCortex CodeCorust Agentcrow-cliCursorDeepAgentsDevinDimCodeDiracFactory Droidfast-agentGemini CLIGitHub CopilotGLM Agent
gooseGrok BuildHarnJunieKiloKimchiKimi CLI (Legacy)Kimi CodeKiro CLIMiniMax CodeMinion CodeMistral VibeMuse CodeNovaOpenCodeOpenCode V2pi ACPPoolsideQoder CLIQwen CodesiGit CodeStakpakVT Code

Meet Q, your project assistant.

One running example: in Café Orders, you say “add a category filter to the menu page.”

Say what you want
Make the calls
Sign off

Q and the system handle the rest: breaking the work down, scheduling, watching progress, chasing, retrying, merging code, and remembering who knows what.

One sentence in. A plan out.

  • One sentence becomes tasks.
  • Anything that changes the UI gets a prototype first.
  • Picks the computer with room and quota left.
  • Picks the model by the kind of work.

Q quotes your own words before acting for you, and everything it does can be undone.

Q never runs commands or edits files. It plans, delegates, and checks — the work happens in sessions you can open at any time.

Your agents, with a project assistant.

A coding agent on its own (Claude Code, Codex…)With QU Studio
Breaking down the workYou split it up and open each session yourselfSay one sentence; Q splits it and hands it out
Watching progressYou keep an eye on the terminalQ watches and tells you the moment something is stuck or done
Before you acceptYou check every result yourselfQ does a first pass and checks it against your own words
MemoryExplain it all again in every new sessionRemembers your preferences and rules; it gets easier the more you use it
Commands that need approvalWait in the terminal for you to press a keyApprove in the corner of the screen; stop being asked for that kind
Changing the UIDescribe it in wordsA prototype first, and the prototype is the spec
Several computersEach one on its ownNew tasks go to the one with room and quota to spare
While you’re awayIt stops and waits for youKeeps running with the window closed; a brief in the morning

Who it’s for

A team for anyone with something to build.

Indie developers

One person, run like a team.

  • Q splits the work and runs several sessions at once.
  • You keep the decisions; the agents do the typing.
  • A morning brief tells you what got done overnight.

Small teams

Several Macs, several agents, one board.

  • New tasks go to whichever Mac has room.
  • Mix Claude Code and Codex on the same project.
  • Each project picks which Macs and agents it may use.

People who don’t write code

Say what you want. Decide. Accept.

  • Talk to Q in plain words, no commands.
  • UI changes come as a prototype you can look at first.
  • You only sign off when it matches what you asked for.

Prototypes

The prototype is the spec.

  • The prototype sits in the right sidebar.
  • Select an element and point at what to change.
  • Hand-ins come with the prototype and the build side by side.
  • Accept on one screen.

Versions

Ship by version.

A changelog that writes itself

Each hand-in adds a line in English and Chinese, sorted into New, Improved and Fixed.

Trial merge before hand-in

Every hand-in is test-merged with the branch it goes into; conflicts are fixed on the spot.

“Ship 0.5.0”

It merges into main first, then hands the release to the Mac with the signing certificate. Publishing is still up to you.

Or ship as you go

Sites and the like can go live with every change instead of waiting for a version.

Your agents

Bring your own agents.

QU calls the agents you installed and signed in to, on your Mac. It never signs in for you or touches your login files, and usage counts on your own account.

Claude Code
Codex
AgoragenticAmpGoogle AntigravityAuggie CLIAutohand CodeBobClineCodebuddy CodeCortex CodeCorust Agentcrow-cliCursorDeepAgentsDevinDimCodeDiracFactory Droidfast-agentGemini CLIGitHub CopilotGLM AgentgooseGrok BuildHarnJunieKiloKimchiKimi CLI (Legacy)Kimi CodeKiro CLIMiniMax CodeMinion CodeMistral VibeMuse CodeNovaOpenCodeOpenCode V2pi ACPPoolsideQoder CLIQwen CodesiGit CodeStakpakVT Code

Switch mid-session

Halfway through with one agent? Hand the session to another. What you discussed comes along.

Mix them

Let one write the code and ask another to write tests or review it.

Out of quota? Keep going

When one runs out, switch to another and the work doesn’t stop.

Helpers

Every session can call in helpers.

Split the work, get a second opinion, keep going.

Split the work

A session breaks a job apart, calls in a few helpers to work on it at once, and merges their changes back.

A second opinion from another agent

Code written by Claude Code? Ask a Codex helper to write the tests or review it. It works the other way too.

Read-only reviewers

A review helper can only look. It finds problems and never touches your code.

Helpers on another computer

Need a key or a tool that only another Mac has? Call the helper in over there.

Sessions working together

Sessions talk to each other. Across projects and Macs.

Same Mac: sessions message each otherAcross Macs: through a relay, end-to-end encrypted

Find who’s doing what

Look sessions up by project, task or keyword.

Messages say who sent them

Sender, project and task are written by the system, so the other side knows how to answer and it can’t be faked.

Joins the turn in progress

A message slips into the other session’s current turn without stopping it.

Works across projects

Two projects line up an interface directly, and each changes its own side.

“Wake me when that’s done”

A session can wait on another task and get told the moment it finishes.

Works across Macs

Messages between Macs go through a relay, end-to-end encrypted.

Multiple Macs

All your Macs, one workspace.

New tasks go where there’s room and quota

Load balancing for your agents. When a new task comes in, Q checks which Mac still has a free slot and which agent has the most quota left, then sends it there.

  • Several Macs signed in to one account count as one quota, never twice.
  • Agents close to their limit go to the back; all full, and the task waits for whichever Mac frees up first.
  • Name a Mac or an agent yourself, or limit a project to the ones you choose.

The project stays on one Mac

  • Your code lives only on the project’s Mac.
  • The other Mac needs no copy of the repo: QU doesn’t clone it there or write your project files to its disk.
  • Its agent works over an encrypted connection, with per-task permission that expires and that you can take back any time.
  • Lose the connection and it picks up where it left off.

Even a rented machine can run your agents: your repo never has to live there. Access is granted per task, expires, and can be taken back any time.

Work moves to another Mac

  • A Mac sleeps or drops off? When it’s back, work picks up from that turn.
  • Can’t wait? Click “Move to another Mac” and it carries on there, task and conversation included.
  • Switch your main Mac or add a new one: the board and memory merge on their own, and settings that differ are asked one by one.

Safe to hand off

Hand it over without worrying.

Approve in place. Earn trust one kind at a time.

  • It never takes your keyboard.
  • Deploying, deleting data and spending money always ask.
  • It pops up on whichever Mac you’re sitting at.
Uncommitted changes are left aloneIf a task would touch them, it stops and asks you first.
Nothing irreplaceable is deletedFiles outside git that can’t be regenerated stay put; before any cleanup you see the list.
Every turn is pushedEach turn lands on the task branch, so another Mac can carry on.
Rollbacks can be undoneGo back a few turns, then change your mind.
Red-line commands are blockedSome commands are simply refused.
Outside text isn’t taken as ordersIssues and comments are read as material, not instructions.

While you’re away

Close the window. The work goes on.

  • Close the window and the work keeps going.
  • While agents are working, your Mac won’t doze off on its own.
  • Close the lid and it sleeps; work picks up when it wakes.
  • Out of quota? It continues when the quota resets.
  • Do not disturb, except for what’s urgent.
A watcher for work that goes quiet
No progress for a long timeNo outputThe same error again and againMuch longer than expectedStopped after one turn
A nudge firstThen another agent takes a read-only lookTruly stuck: taken back and handed out again

Model presets

The right model for each job.

Set up a few presets once. Q picks one per task: model and thinking effort follow the work.

A preset is a full setup

Which agent, which model, how much thinking effort, fast mode or not, plus one line on when to use it.

Q picks by “when to use”

Copy and styling get the light preset, pages and features the everyday one, designs and hard bugs the strongest.

Helpers too

A session calling in a helper picks a preset the same way.

Your call wins

Name a preset and that’s the one used. Change them any time.

Quota

See your quota. Spend it where it counts.

The right model per job

Presets match model and effort to the work (see Model presets above).

Background work doesn’t crowd you out

It stays below a quota line.

Running low? Switch

Move to another agent and bring the context along.

Ran out? It resumes on time

When the quota resets, the work carries on.

Under the hood

Built in Rust. Talks to your agents directly.

One layer less

The background service is a single Rust process that manages every session itself, with no Node or SDK host process wrapped around each one. Many sessions at once stay light.

Steady for hours

Close the window and the work keeps going. Close the lid and it sleeps; work picks up when it wakes. It doesn’t get slower or heavier over a full day.

Your own subscription

It calls the Claude Code and Codex you installed and signed in to, and usage counts on your own subscription or account. It’s the same agent you run in the terminal, unchanged.

Everything else you’d expect, and then some.

Board in four columnsIdeas, to do, in progress, waiting for you.
Run and previewRegister how your dev build starts once; sessions start it, look, and stop it.
Fork and roll backBranch a session from any turn, or roll back the code with it.
Take over in the terminalOpen any session in your own terminal and carry on.
Drafts before GitHubComments and new issues are saved as drafts; they post only after you click.
Scheduled tasksRun something every morning, or once at three.
Watches GitHubNew issues and comments come in as tasks to look at.
⌘L to quote anywhereQuote a passage and send it to any session.
Drop in a screen recordingKey frames are pulled out for the agent.
Plan viewDrag lines between tasks to set the order.
Export your dataTake everything with you, any time.
English and ChineseThe whole app, in either language.

How QU thinks.

01Talk to one personYou talk to Q. Q talks to everyone else.
02Roles are set by the systemWho plans, who builds and who checks is fixed, not left to chance.
03Pin down “what” firstWhat you want becomes something the result can be checked against.
04Accepting should be cheapEverything you need to say yes or no is on one screen.
05Quiet by defaultIt only interrupts you when you’re needed.
06Trust is earnedApprove a kind of action once, then let it through. Risky ones always ask.

Questions

Whose account does it use?

Yours. QU calls the agents you installed and signed in to, and never signs in for you.

Is my code or chat uploaded?

Your projects and sessions stay on your Mac. Between your Macs, traffic is end-to-end encrypted; the relay can’t see the content.

Which agents does it support?

Claude Code and Codex are built in, and Q hands work to them. 44 more agents in the ACP registry, such as Gemini CLI, Cursor and OpenCode, can run sessions too.

Do I need to write code?

No. You can just say what you want, look at the prototype, and accept the result. Developers can open any session and take over.

How is Q different from using an agent directly?

An agent does the work in one session. Q plans it, hands it to several sessions, watches them and checks the results, so you only decide and sign off.

Is there a Windows or Linux version?

Windows and Linux versions are coming soon. Right now QU Studio is macOS only, on Apple silicon.

If I close my laptop, does the work keep going?

Closing the lid puts it to sleep, and work picks up when it wakes. To run overnight, send the work to a Mac that stays on, like a Mac mini.

Will it use more of my quota?

Q picks the model and effort by the kind of work, so small jobs use lighter models. Background work keeps below a quota line so it doesn’t eat into yours, and when one agent runs low, work moves to another.

Will it delete my stuff?

It doesn’t touch changes you haven’t committed; it stops and asks. Files outside git that can’t be regenerated are never deleted, and you see the list before any cleanup. Rollbacks can be undone, and commands that cross a red line are blocked.

Say what you want. Q takes it from there.

Download for macOS
WindowsComing soonLinuxComing sooniOSComing soonAndroidComing soon

macOS on Apple silicon only for now.