# A Mac of the agent's own: what changed in v1.2.0, sgit.ai > The changes to the article "A Mac of the agent's own" in v1.2.0, paragraph by paragraph. *Source: · site v0.7.38 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [A Mac of the agent's own](../../a-mac-of-the-agents-own.md) / [Versions](../a-mac-of-the-agents-own.md) / v1.2.0 # A Mac of the agent's own: what changed in v1.2.0 From v1.1.0 (2026-10-10, `2592327fb`) to v1.2.0 (2026-10-10, `ed8f0cd7f`), paragraph by paragraph. 10 paragraphs added, 0 removed, 0 changed in place, 70 unchanged. About 596 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [← v1.1.0](v1.1.0.md) · [all versions](../a-mac-of-the-agents-own.md) 68 unchanged paragraphs, under In short, The next dedicated resource, Why a Mac… ## One Mac, many agents: what changes when you queue them *Added on 10 October 2026, after a question from the plan's author.* The obvious next question: if a leased Mac must be held for at least 24 hours, can one customer fill that day with many agents, one at a time, cleaning up after each? The cleaning-up part is easy. With the bootstrap above, everything an agent touched comes from vaults and goes back to vaults, so wiping between runs is a deletion, not a project. And the agents in our own team already run on a schedule, several times a day. The licence, read again with that question, cares about two things that queueing does not change: **what the Mac is used for**, and **who is using macOS**. [figure ad-queue.webp] Six scenarios against the clauses that decide them. Queueing satisfies "one user at a time"; the purpose of a lease, and who the user is, decide the rest. A reading of Apple's text, not legal advice. **Purpose.** A lease is valid only "for the sole purpose of providing Permitted Developer Services", which Apple defines as "continuous integration services, including but not limited to software development, building software from source, automated testing during software development, and running necessary developer tools to support such activities." So a queue of coding agents on a leased Mac fits: it is what a continuous integration runner already does, many jobs for one customer in a row. A queue of office agents, working in mail, a browser and desktop apps, is outside the lease however carefully it is scheduled. **Who.** If my agents, with my credentials, do the work and my customers buy the result, I am the user of macOS. That holds for developer work on a lease even when the work is for clients: a consultancy's build machine. If my customers' own agents, with their own credentials, get slots on my Mac, my customers are using macOS in turn, which is the "service bureau, time-sharing" the licence excludes "whether such services are being provided within your own organization or to third parties", and each of them would need a lease of their own of at least 24 hours. **The case worth a lawyer's hour.** On a Mac you own, Section 2B(ii) lets a business run macOS "by multiple individuals on a single shared Mac Computer that you own or control", alongside "only one user may use the Apple Software at a time". A queue of your own agents on your own Mac, wiped between runs, is the closest fit for office agents. Two words decide it: whether automated agents are "individuals", and whether rotating them is time-sharing "within your own organization". **What would need Apple's written terms.** Two cases: office agents on a leased Mac, and customers' agents sharing one Mac. The macOS 27 licence adds "except as otherwise provided in writing, signed, or issued by an authorized representative of Apple" to the virtualisation and leasing clauses, which is the route. The narrow ask is easier than the broad one: one organisation, a lease of 24 hours or more, sole use, one agent at a time, wiped between runs, for non-developer work. It keeps every condition Apple already sets except the purpose. So the plan's shapes hold, with one refinement. The dedicated Mac per customer (shape B) is needed whenever the agents are the customer's. When the agents are the operator's, doing work the customer buys, one Mac can serve many of them in turn, and for developer work that is already within the licence. 2 unchanged paragraphs [← v1.1.0](v1.1.0.md) · [all versions](../a-mac-of-the-agents-own.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://sgit.ai/articles/versions/a-mac-of-the-agents-own/v1.2.0.html)*