The studio on a Mac

The same studio as on Windows, which also serves your other studios the way an agent does.

The whole studio runs on a Mac with Apple silicon: the same window, the same plugins and the same mail as on Windows, not a reduced version. A Mac with the studio is also a computer that other studios can reach, so you do not need the separate agent there as well. This page covers what is particular to the Mac. The download and the first steps are in Installing AigoPilot.

What it needs

  • A Mac with Apple silicon (M1 or newer) and macOS 13.3 or newer. There is no build for Intel Macs.
  • An active plan. The disk image is on your member profile under Download for Mac.
  • Claude Code, Codex or Grok on the Mac, or the studio installs them for you with each maker's own installer after you say yes. Signing in opens the tool's own sign-in in Terminal.

The app is signed by Doment Digital FZE LLC and notarized by Apple, so macOS opens it after the usual question about an app from the internet. Allow it to find devices on your local network when macOS asks, so your other computers and your phone can find the Mac. If you use voice typing, allow the microphone too.

If AigoPilot Agent is already on the Mac

Many people first used the Mac as an agent of a studio on a PC. The first time the studio opens, it takes over the agent's work:

  • It keeps the agent's data, its computer id and its pairings, so a studio on another computer that already reaches this Mac goes on reaching it, with no new pairing.
  • It stops the agent and makes sure the agent no longer starts by itself. If the agent started when you signed in, the studio now starts then instead.
  • It says once: "AigoPilot kept your agent's computer id and pairings and now does its work; the separate agent no longer starts."

If a session is still open in the agent, the studio does not interrupt it. It asks you to close those sessions and open the studio again, and takes over then. The agent's app stays in Applications; you can move it to the Trash. Opening the old agent afterwards does not start a second copy beside the studio.

A Mac studio that other studios reach

The Mac's studio runs its own sessions and also serves the studios of your other computers, the way an agent does. To pair one, open Settings, then Computers, on the Mac: it shows six digits, which you type on the other computer as described in Pairing two computers with six digits. A phone is paired from its own page. Sessions on the Mac show up in both studios.

A studio that reaches the Mac must hold a licence of its own. The Mac does not need to be signed in for that: even when its own studio shows only the account page, it still serves a paired studio that brings a valid licence, and its Computers page still offers pairing and the start-at-sign-in switch.

When the first studio pairs with the Mac, the studio is set to start when you sign in to the Mac, so it is there after a restart. If you turn that off in Computers, a later pairing does not turn it back on.

Window, menu bar and quitting

The window has the Mac's own buttons and menus, and shortcuts use Cmd. Closing the window, or Cmd+W, only hides it; the studio stays in the menu bar and the Dock, and its engine keeps working for sessions and paired studios. Quitting while a session works asks whether to stop the work or keep it going in the background. Keys and passwords are kept in the Mac's Keychain.

What differs from Windows

  • Updates: the Mac studio updates itself. It looks once a day and when you press its update button, checks the company's signature and Apple's notarization, waits until no session works, then replaces itself and opens again. See Updates.
  • Voice typing on the computer itself uses whisper.cpp from Homebrew. If Homebrew is missing, the setup says what to install first.
  • Programs a project needs, such as Node.js, are installed with Homebrew on your click when Homebrew is there; otherwise the studio shows the maker's download page. Nothing is installed without your click.
  • Background workers: pm2 programs and running project programs are listed. Windows' scheduled tasks do not exist on a Mac.
  • The graphics card's share per program is shown as unknown, because macOS gives it only to an administrator, and the studio never works as one.
  • A Mac with its lid closed sleeps, whatever the studio asks. Keep the lid open for long work.

Your data lives in ~/Library/Application Support/com.aigopilot.studio. To remove the studio, quit it and move it from Applications to the Trash; to remove your data too, delete that folder.

Small tips

Close the Mac window without stopping your sessions

Cmd+W or the red button only hides the studio. It stays in the menu bar and the Dock, and sessions and paired studios keep working.

Questions

Do I still need AigoPilot Agent on a Mac that has the studio?

No. The studio does the agent's work too: other studios pair with it and run sessions there. If the agent is already installed, the studio takes over its id and pairings the first time it opens.

Does the Mac studio run on an Intel Mac?

No. It needs Apple silicon and macOS 13.3 or newer. An Intel Mac can still be a computer of your studio through AigoPilot Agent, which needs macOS 11 or later.

KEEP READING

Something missing or out of date? Write to [email protected] or use the chat on this page. All guide articles