The Lot — Terms and Licence

What you may do with it, and what you take responsibility for.

Last updated: October 3, 2026 · build 0.55.1

1. What this covers

This agreement is between you and Wigley Studios LLC ("we", "us"), and governs The Lot — the Windows application, its embedded orchestrator, and the optional components that ship with it (together, "the Software"). Installing or running it means you accept these terms. If you don't, don't install it; if you already have, uninstall it.

Wigley Studios' general Terms of Service apply to everything not specifically addressed here — including governing law, dispute resolution and the class action waiver — and this page takes precedence where the two differ about the Software. Data handling is covered separately and in detail by The Lot's privacy policy.

The Lot Privacy Terms Notices

2. This is a private playtest

The Software is pre-release and distributed by invitation to a small group. That is not a disclaimer decorating a finished product; it is a description of what you are getting.

  • It will have defects, including ones that lose work or require reinstalling.
  • Features appear, change and disappear between builds without notice.
  • Saved state, configuration and world layouts may not survive an update.
  • There is no service level, no uptime commitment and no support obligation, though in practice reports get answered.

The build and its download password are for you. Please don't republish either, or pass them to someone who wasn't invited. If you'd like somebody added, ask — that is a cheerful yes far more often than not.

3. Your licence

We grant you a personal, non-exclusive, non-transferable, revocable licence to install and use the Software on machines you control, for your own use, for as long as the playtest runs. That licence is free of charge and comes with no purchase, subscription or payment obligation.

You may not sell, rent, sublicense or redistribute the Software; remove or alter its notices; or present it as your own. You may not reverse-engineer it except to the extent that applicable law says you may regardless of this sentence, or that the licence of a third-party component inside it grants you — several components are LGPL-licensed (edge-tts, and inside the Python runtime FFmpeg, LAME, GNU libiconv and libsndfile), which entitles you to reverse-engineer them to debug your own modifications, and two are GPL-licensed (the x264 and x265 encoders inside PyAV), whose licence gives you its full rights in them; nothing here takes either away. Third-party components inside it carry their own licences, which govern those components — they are listed in the third-party notices.

Everything the Software creates for you — your worlds, layouts, configuration, notes and the output of your own AI accounts — is yours. We claim nothing in it.

That carve-out is not boilerplate. LGPLv3 grants a right to reverse-engineer the LGPL portion for debugging, and that grant is contractual rather than statutory — so a blanket "except where the law requires" would not have reached it. The components in question are named in the third-party notices.

4. Your accounts are yours, and so are their rules

The Software supplies no AI accounts and no credits. It runs on your own logged-in Claude session, or on API keys you paste in yourself for Anthropic, OpenRouter and ElevenLabs, or add to orchestrator\.env yourself for Brave Search and Cursor. If the Cursor command-line agent is installed, the secretary can drive it under your Cursor account. Nothing is metered by us and nothing is resold by us.

That means your use of those providers stays governed by your agreement with each of them, and, through OpenRouter, the companies whose models it routes to, and you are responsible for complying with it — including any terms about automated access, acceptable use, and how a subscription may be driven. If a provider limits, suspends or bills your account, that is between you and them. We have no visibility into it and cannot appeal it for you.

Any charges your usage incurs with a provider are yours. The Software will happily do exactly what you tell it to, repeatedly, and a key with a budget attached is a key you should give a budget. Some calls happen without a fresh instruction: with an OpenRouter key the residents remark every few minutes while the world is open, and the secretary greets you on return, checks in when a job finishes and writes a handoff note at shutdown and 4 a.m. Those use your accounts and credits too.

Keep your keys to yourself. They sit in one plain file on your own disk (orchestrator\.env) and are sent only to the provider each one belongs to. Anyone with access to that machine has access to those keys — the same as any other tool that stores credentials locally.

5. What you are authorising on your machine

By installing and running the Software you are knowingly permitting it to do the things listed in the privacy policy's section 2: read the pixels of windows you name, hold three global hotkeys, capture the microphone while you hold a key, take the foreground and move your mouse and windows when you sit at a screen, launch programs listed in your own config, start the Claude Code and Cursor command-line agents for coding jobs, run agents that read and write your files, load web pages in a built-in browser (including the default screens at startup), download images from web addresses you place, and keep a local connection between the world and its Python brain on 127.0.0.1, alongside the built-in browser's debugging port.

These are the product, not side effects, and each one is limited in the way that section describes. They are also, individually, capabilities a security tool may flag. You should install this on a machine where that is your call to make — not on an employer's device without permission, and not on a machine subject to rules you would be breaking.

6. Agents act as you — you are the operator

The secretary and the residents can run instructions against your real applications and your real files. File edits inside the agent's working folder are pre-approved; anything it would have to ask permission for is refused, and refusals are shown rather than hidden. That is a safety rail, not a guarantee, and it is you who decides what to open.

  • An agent acting on your machine is acting as you, with your permissions, under your accounts.
  • You are responsible for what you instruct it to do and for what you grant it access to.
  • Keep backups of anything you cannot afford to lose. This is pre-release software driving real tools; that combination deserves a backup on general principle.
  • Don't point it at systems you are not authorised to touch.

AI output can be confidently wrong. Nothing the Software or its residents produce is professional, legal, financial, or medical advice, and none of it should be relied on without checking. Verify before you act on it, especially where the action is hard to undo.

7. The optional display driver

The Software can install a virtual display driver, which adds a monitor that exists only in software. It is a third-party, MIT-licensed, Microsoft-signed component (Virtual Display Driver), shipped unmodified and credited in the notices.

  • It installs only if you accept the offer, behind one Windows administrator prompt. Declining costs you nothing but that feature.
  • It ships with its own uninstall script, and the app runs fine without it.
  • It is a display driver: it is not our code, and it is provided under its own licence, without warranty from us.

8. Feedback and bug reports

When you send a report, or the app sends an automatic error report you switched on, you give us permission to use it to diagnose and fix the Software, and to build on any suggestion it contains, without owing you payment or attribution. You keep ownership of anything you wrote; we just need to be able to act on it.

Please don't send anything confidential. The F11 form lists every attachment and lets you untick any before it sends; automatic reports have no form, and the privacy policy's section 5 lists exactly what they contain.

9. No warranty

The Software is provided "as is" and "as available", without warranty of any kind, express or implied, including the implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. We do not warrant that it will be uninterrupted, error-free, secure, or that it will not lose data, and no advice from us creates a warranty.

Some jurisdictions do not allow exclusion of implied warranties, in which case that exclusion applies only as far as the law permits.

10. Limitation of liability

To the fullest extent the law allows, Wigley Studios LLC is not liable for indirect, incidental, special, consequential or punitive damages, nor for lost profits, lost data, lost work, business interruption, or charges incurred with a third-party AI provider, arising from your use of the Software — whether or not we were told such damages were possible.

Our total aggregate liability arising out of or relating to the Software will not exceed one hundred United States dollars (US$100). The Software is supplied free of charge, and this limit reflects that.

Nothing here excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud.

11. Ending it

You can stop at any time by uninstalling. We can end the playtest, or your access to it, at any time and for any reason — including because the playtest itself has ended. Sections 8 through 10 survive.

Uninstalling removes the Software and its Logs folder. It deliberately leaves your config folder in place, so an upgrade does not throw away your room, and it also leaves your keys, the secretary's data, your screenshots, the app's folder in AppData\LocalLow and its registry settings; the privacy policy's section 7 lists where each lives. Delete them yourself if you want everything gone.

12. Law, changes and contact

Georgia, United States law governs this agreement, and the dispute resolution, arbitration and class action waiver provisions of the general Terms of Service apply to it.

These terms may change as the Software does. Material changes will be noted in the release notes rather than made silently, and the date and build number at the top of this page always say which version it was written against.

Questions, or a clause that reads wrong: support@wigleystudios.com.

The Lot Privacy policy Third-party notices