Deploying Maxiful across your organisation

A note for IT teams rolling Maxiful out to Windows PCs and Macs: how it installs on each, how to push it with Intune, Jamf Pro or a silent install, what it puts on a computer and starts, the network hosts to allow, how security tools see it, the settings you can set centrally, and how it updates and comes off again.

Checked against Maxiful 0.9.60 for Windows and Mac, and Keep this computer available for your team against 0.9.70, the release that brings it. Where Windows and the Mac differ, each section has a part for each.

Larger firms in Sweden can join as design partners too, with their first three months free. Apply as a design partner

How it installs

On both platforms Maxiful is a desktop app that each person sets up for themselves. On its first start it sets up the assistants' runtime for that person: OpenClaw, the open-source agent runtime, on a copy of Node.js that Maxiful installs for that person. A background process of that runtime, the gateway, runs the assistants, and it starts again each time the person signs in to the computer.

On Windows

Per person, with no administrator rights. The installer, Maxiful-x64-setup.exe, runs as the person signed in to Windows and installs into that person's %LOCALAPPDATA%\Maxiful. It is listed under that person's installed apps, so each person who uses Maxiful on a computer has an install of their own.

Windows 10 or later, 64-bit. Maxiful's window is drawn by Microsoft Edge WebView2. If the WebView2 Runtime is missing, the installer downloads Microsoft's own WebView2 installer from go.microsoft.com and runs it silently.

On a Mac

One app in /Applications, set up per person. Maxiful for Mac comes as a disk image, Maxiful-arm64.dmg, with Maxiful.app inside, signed with an Apple Developer ID and notarized by Apple (the signature's details are under Mac: Intune and Jamf Pro). Copied into /Applications, by a person or by your device management, it is one app for everyone on the Mac; each person who opens it signs in and gets an install of their own, with their assistants and data in their own home folder.

macOS 13 or later, on Apple silicon or Intel. The app is one build for both.

Windows: silent install

Maxiful-x64-setup.exe /S
SwitchWhat it does
/SSilent: no installer window and no questions from the installer. Adds a Start menu and a desktop shortcut.
/PPassive: a progress bar and no questions. Maxiful's own updates run this way.
/NSNo Start menu or desktop shortcut.
/ROpens Maxiful when the install finishes (with /S or /P).
/DEFENDER=managedYour own Defender policy adds Maxiful's working folders (below), so the install does not ask Windows about them.
/DEFENDER=offYou want Defender to scan those folders, so the install does not ask Windows to let Defender skip them.

Exit codes. 0 means the install finished, and any other code means it did not. A 2 can have more than one cause; one is another program keeping one of Maxiful's files in use for 30 seconds, and then nothing was changed. The installer ends the person's own running Maxiful before it writes.

Over an installed copy. Running a newer installer the same way updates it in place, and the person's assistants and data stay. We measured this on our Windows test PC on 26 October 2026, from 0.9.54 to the signed 0.9.58.

Microsoft Defender's folders

Maxiful's own working folders change thousands of files every time the team starts, so Maxiful asks Windows to let Microsoft Defender skip four of them. Without a /DEFENDER switch, the install asks after it writes its files: Windows shows its own permission prompt for this, and for a person without administrator rights it asks for an administrator's sign-in. If nobody answers, Windows closes the prompt by itself after about two minutes and the install still finishes. Maxiful asks once more the next time it starts, and a second unanswered prompt counts as a no and is not asked again.

With /DEFENDER=managed or /DEFENDER=off (exactly these words), no install, update or start asks Windows, and Maxiful's settings say that your IT department manages Microsoft Defender on the computer. With the folders scanned, everything works, and the team starts more slowly. The person can still turn the exclusions on themselves later in Maxiful's settings, under Let Defender skip Maxiful's working folders, which asks Windows as above.

Folder Defender is asked to skip
%LOCALAPPDATA%\Lanoko\node-v24.22.2\node_modules\openclaw
%LOCALAPPDATA%\Lanoko\node-v24.22.2\openclaw-compile-cache
%USERPROFILE%\.openclaw-*\tmp\plugin-captures
%USERPROFILE%\.openclaw-*\agents\*\agent

Windows: Microsoft Intune (Win32 app)

We measured the silent install and the update over an installed copy on our own Windows test PC. This recipe follows Microsoft's Win32 app documentation and has not been run in an Intune tenant; if yours behaves differently, tell us at support@maxiful.ai.

  1. Make a package folder holding Maxiful-x64-setup.exe, downloaded from your Maxiful account and checked against its SHA-256, and a file uninstall.cmd, because Intune does not expand environment variables in an uninstall command:
    @echo off
    "%LOCALAPPDATA%\Maxiful\uninstall.exe" /S _?=%LOCALAPPDATA%\Maxiful
    set rc=%ERRORLEVEL%
    del /q "%LOCALAPPDATA%\Maxiful\uninstall.exe"
    rmdir "%LOCALAPPDATA%\Maxiful"
    exit /b %rc%
    _?= makes the uninstaller run in place and finish before the script goes on; the two lines after it remove the uninstaller itself and the empty folder. To remove the person's assistants and data too, write /S /REMOVEALL _?=%LOCALAPPDATA%\Maxiful on the first line instead (see Removal).
  2. Make the .intunewin file with Microsoft's Win32 Content Prep Tool:
    IntuneWinAppUtil.exe -c C:\maxiful-package -s Maxiful-x64-setup.exe -o C:\maxiful-intunewin -q
  3. Program: install command Maxiful-x64-setup.exe /S /DEFENDER=managed where your Defender policy adds the four folders above, or Maxiful-x64-setup.exe /S /DEFENDER=off to have them scanned; uninstall command uninstall.cmd; install behaviour User; device restart behaviour No specific action; the default return codes.
  4. Requirements: 64-bit, Windows 10 or later.
  5. Detection rule: File, path %LOCALAPPDATA%\Maxiful, file Maxiful.exe, method File or folder exists.
  6. Assignment: Required or Available, to user groups.

Intune expects an install that asks nothing. With a /DEFENDER switch, Maxiful's install asks nothing; without one, Windows' Defender prompt is the one question it can raise. Read First start before you assign it widely.

Mac: Microsoft Intune and Jamf Pro

Your device management installs the notarized Maxiful.app into /Applications, from the same disk image people download. These are the values it asks for.

For your MDMValue
Bundle identifierai.maxiful.desktop
Team ID467H9AXX55
The app's signatureDeveloper ID Application: Polytrader ltd (467H9AXX55), notarized by Apple.
Its code requirementidentifier "ai.maxiful.desktop" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "467H9AXX55"
VersionCFBundleShortVersionString in /Applications/Maxiful.app/Contents/Info.plist: the Maxiful version.
Where it installs/Applications/Maxiful.app
Managed preferences domainai.maxiful.desktop, the bundle identifier. Its keys are under Managed settings.

Microsoft Intune (macOS app (DMG))

  1. Apps, All Apps, Create; platform macOS, type macOS app (DMG); select Maxiful-arm64.dmg, downloaded from your Maxiful account and checked against its SHA-256. The Macs need Intune's management agent for macOS.
  2. App information: add a logo, so the app shows in Company Portal with its icon. Requirements: Minimum Operating System macOS 13.
  3. Detection rules: Included apps ai.maxiful.desktop and its version. Ignore app version No, so each version you upload installs. Set AutoUpdate to 0 as well (see Managed settings): you install every version through Intune, and Maxiful looks for none itself.
  4. Assignments: Required (installed to /Applications), Available in Company Portal, or Uninstall.

Intune needs full disk access to update or remove a DMG app, and asks for it on macOS 13 and later when the app is assigned. To roll out a new version, upload its disk image to the same app: Required assignments update by themselves, and with Available each person chooses Reinstall in Company Portal.

Jamf Pro

Jamf Pro deploys packages from its distribution points. Build one that holds /Applications/Maxiful.app with Jamf Composer:

  1. On a Mac, copy Maxiful.app from the disk image into /Applications. In Composer, drag /Applications/Maxiful.app from the Finder to the Sources list, so it keeps its place in /Applications, and build a package from that source.
  2. Add the package to a distribution point and to Jamf Pro.
  3. Under Computers, Policies, make a new policy. In General, set its trigger and execution frequency; in the Packages payload, add the package with the action Install and choose the distribution point.
  4. On the Scope tab, choose the computers; or make the policy available in Self Service.
  5. For each new version, build its package the same way and deploy it with a policy, and set AutoUpdate to 0 (see Managed settings) so Maxiful looks for none itself.

These steps follow Microsoft's and Jamf's documentation and have not been run in an Intune or Jamf tenant; if yours behaves differently, tell us at support@maxiful.ai.

The gateway's login item

The assistants' gateway runs as each person's own LaunchAgent, labelled ai.openclaw.<name>. On macOS 13 or later, a Service Management (managed login items) payload with the rule type Label prefix and the value ai.openclaw. approves it automatically.

First start: what each person does

A silent install, or your MDM's copy in /Applications, leaves Maxiful ready to open. The first start asks each person for these steps, on Windows and on a Mac alike; IT cannot complete them for a person.

  • Each person signs in with their own email address: Maxiful emails a sign-in link, and the link opens the app. Where the workspace's owner has set up single sign-on for your organisation's email domain, the person can choose Continue with your work account instead, which opens your identity provider's sign-in (Microsoft Entra ID, Google Workspace, Okta, another OpenID Connect provider or a SAML 2.0 provider) in their browser; with Enforce single sign-on on, an emailed link hands over to your provider too.
  • A person setting up a new workspace enters the setup code from their Maxiful account. A code works on the first computer that uses it.
  • A colleague invited to a workspace joins it instead, and so does a person of your verified domains who signs in through your provider while the owner's Add people to my workspace when they sign in is on. Each new device of a colleague waits until the workspace owner lets it in on the Team page, under People.

Setup then installs Node.js and the runtime for that person and starts the team. It needs the network hosts listed below.

On a Mac: the permissions macOS asks for

Maxiful asks macOS for a permission only when a feature first needs it, and macOS shows its own question:

  • Notifications, the first time Maxiful has one to show, such as a reply that arrives while its window is in the background.
  • Microphone and Speech Recognition, the first time a person dictates a message or talks with an assistant.
  • Accessibility, Screen Recording and Input Monitoring, when the owner first lets the assistants use the computer.

Where the team runs, and an always-on computer

The team runs on the owner's computer: the assistants, their memory and their conversations are in the owner's install there, and colleagues connect to it from their own devices. An office that wants the team answering around the clock runs the owner's install on a computer that stays on:

  • A Mac with the owner's macOS account signed in. The gateway is that account's own LaunchAgent and starts when the account logs in, so sign the account in again after every restart, or turn on automatic login, which macOS does not offer while FileVault is on.
  • A Windows PC that signs in to the owner's Windows account by itself (Windows' automatic sign-in). Maxiful starts the gateway when the account signs in; a start at boot needs an elevated install, which Maxiful never runs.

The account's AI models answer on one computer at a time. If the owner also uses Maxiful on a laptop and chooses Use Maxiful here there, the always-on computer's assistants stop answering until the owner chooses it again on that computer.

To install each update on that computer yourself, set AutoUpdate to 0 (see Managed settings). Maxiful's backups are archives it writes on the same computer, in the owner's home folder under <name>-shared/backups; copy them off the computer with your own backup tools.

Keep this computer available for your team. From Maxiful 0.9.70, the owner turns this on in Maxiful's settings on that computer, under Your install. While it is on, the computer does not go to sleep on its own, Maxiful opens each time the account signs in, an update Maxiful has downloaded installs between 02:00 and 05:00 on the computer's clock while no assistant is working (none where AutoUpdate is 0; a task running longer than an hour is not waited for), and Maxiful emails the owner when the computer has been unreachable for 15 minutes, at most once every 6 hours. Turning it off undoes each of these.

Maxiful opens through its own start item, which the switch adds and removes again when it is turned off: ~/Library/LaunchAgents/Maxiful.plist on a Mac, and the Maxiful value under HKCU\Software\Microsoft\Windows\CurrentVersion\Run on Windows. The switch does not sign the account in: after a restart, the team comes back once the account signs in, by a person or by automatic login, which macOS does not offer while FileVault is on. Closing a laptop's lid, choosing Sleep or a low battery still puts the computer to sleep.

What it puts on the computer

<name> below is the install's own short name.

On Windows

WhereWhat
%LOCALAPPDATA%\MaxifulThe app: Maxiful.exe, gateway-launcher.exe (starts each assistant command in its sandbox) and uninstall.exe.
%LOCALAPPDATA%\ai.maxiful.desktopThe app's own data: its WebView2 data, its logs (logs\Maxiful.log, logs\installer.log) and its record of the Defender question.
%LOCALAPPDATA%\LanokoNode.js 24.22.2 with the OpenClaw runtime installed in it, and npm's cache. The folder carries Maxiful's earlier name.
%USERPROFILE%\.openclaw-<name>The install itself: the runtime's configuration, the assistants, their workspaces and memory, the install's secrets, and the assistants' own browser.
%USERPROFILE%\.stommeMaxiful's own records for each install, such as its add-ons and the owner's decisions.
%USERPROFILE%\.lanoko-sandbox\<name>A plain-text description of what each assistant's sandbox grants. The gateway itself runs outside any container.
RegistryHKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\Maxiful (the installed-apps entry) and HKCU\Software\maxiful\Maxiful (the install folder).
Starts at sign-inA Scheduled Task for the gateway, the runtime's own (OpenClaw Gateway (<name>)) or Maxiful's own (ai.openclaw.gateway-<name>), or, where Windows refuses a task, OpenClaw Gateway (<name>).vbs in the person's Startup folder. Where the runtime's own Scheduled Task runs the gateway, Maxiful also adds a Scheduled Task, Maxiful team keeper (<name>), which looks at the team every two minutes; with the Startup-folder script there is none. Each of them starts the gateway when the person signs in, as that person; none starts it before anyone signs in. The runtime asks Windows for a task with S4U logon and a trigger at startup, which Windows registers only for an elevated install, and Maxiful never runs that install elevated: Windows refuses it, and the runtime then uses the Startup-folder script, or keeps a task an earlier version registered as it was, which starts at sign-in. schtasks /query /tn "OpenClaw Gateway (<name>)" /xml shows a computer's task.

Processes on Windows

ProcessWhat it is
Maxiful.exeThe app, signed (see below). Its window runs in Microsoft's msedgewebview2.exe.
node.exeFrom %LOCALAPPDATA%\Lanoko\node-v24.22.2: the OpenClaw gateway and the runtime's own commands. It is Maxiful's own build of Node.js 24.22.2, with a fix for Windows sandboxes, checked against a SHA-256 pinned in the app before it is used.
gateway-launcher.exeFrom the app folder: starts each assistant command inside its sandbox.
chrome.exeFrom %USERPROFILE%\.openclaw-<name>\browser\chromium\chrome-win64: the assistants' own browser, a Chrome for Testing build from Playwright's download server, checked against a pinned SHA-256. It never opens the person's own browser.
cmd.exe, wscript.exeStart the gateway: gateway.cmd, run by the gateway's Scheduled Task through gateway.vbs in the install's folder (a task from an earlier version) or directly, or by OpenClaw Gateway (<name>).vbs from the person's Startup folder.

Commands the assistants run (a shell, PowerShell, scripts) run as children of the gateway, in each assistant's own sandbox by default. The gateway listens on 127.0.0.1 at a port from 18800 up (18800 for the first install), and Maxiful.exe on further loopback ports; on our test PC nothing of Maxiful's listened on any other address.

On a Mac

WhereWhat
/Applications/Maxiful.appThe app, one copy for everyone on the Mac.
~/Library/Application Support/LanokoNode.js 24.22.2 with the OpenClaw runtime installed in it, npm's cache, and the gateway's working folder. The folder carries Maxiful's earlier name.
~/.openclaw-<name>The install itself: the runtime's configuration, the assistants, their workspaces and memory, the install's secrets, and the assistants' own browser.
~/.stommeMaxiful's own records for each install, such as its add-ons and the owner's decisions.
~/.lanoko-sandbox/<name>A macOS sandbox profile written for the install, gateway.sb. The gateway stays outside every profile; by default, each assistant's commands and file work run in a sandbox of its own.
~/Library/LaunchAgents/ai.openclaw.<name>.plistThe gateway's LaunchAgent: it starts the gateway when the person signs in, as that person, and starts it again if it stops.
~/Library/Logs/ai.maxiful.desktop/desktop.noindexThe app's log, Maxiful.log.
~/Library/Logs/Lanoko/gateway.noindexThe gateway's logs.
KeychainThe gateway's device key, Maxiful Gateway Device Key, in the person's keychain.

Processes on a Mac

ProcessWhat it is
MaxifulThe app, from /Applications/Maxiful.app, signed and notarized (see Mac: Intune and Jamf Pro).
nodeFrom ~/Library/Application Support/Lanoko/node-v24.22.2/bin/node: the OpenClaw gateway and the runtime's own commands, started by launchd, outside every sandbox profile. It is the official Node.js 24.22.2 for macOS from nodejs.org, checked against a SHA-256 pinned in the app before it is used.
Google Chrome for TestingFrom ~/.openclaw-<name>/browser/chromium: the assistants' own browser, a Chrome for Testing build from Playwright's download server, checked against a pinned SHA-256. It never opens the person's own browser.

The commands the assistants run are children of the gateway, in each assistant's own sandbox by default. The gateway listens on 127.0.0.1 at a port from 18800 up, as on Windows.

Network hosts to allow

Every connection is opened from the computer outward, over HTTPS (the relay also uses WSS). Nothing on our side can open a connection to the computer.

For setup and everyday use

HostUsed for
maxiful.aiSign-in, including the start and return of a sign-in with a work account, the account, the update feed, the add-on store and setup diagnostics.
lanoko.aiSetup codes, model access at setup, the welcome email and colleague memberships.
proxy.stomme.aiEvery cloud model call, and the apps connected under More work apps.
stomme-model-proxy.stomme-ai.workers.devThe list of models.
or-key-worker.stomme-ai.workers.devThe plan's allowance.
mc-cdn.lanoko.ai, mc-cdn.stomme.ai, mc-cdn.maxiful.aiThe add-on index and add-ons, Maxiful's Node.js build for Windows, the local memory-search model and voice models.
nodejs.orgNode.js, at setup.
registry.npmjs.orgThe OpenClaw runtime, at setup and when an update carries a newer runtime.
cdn.playwright.devThe assistants' browser, at setup.

Only when a feature is used

HostUsed for
relay.maxiful.aiThe relay (WSS): a paired phone, and a colleague's devices.
relay.lanoko.aiThe same relay under its earlier name, for installs and phones paired before 22 October 2026.
ingress.lanoko.aiChat platforms that deliver by webhook, such as Teams and Google Chat.
teamtailor.maxiful.aiThe Teamtailor connection.
openrouter.aiMemory search, on a computer that cannot run the local search index.
github.com, huggingface.coFallbacks for the local memory-search engine and model when our download server does not answer. github.com also serves the tool the Google Workspace connection uses.
clawhub.aiThe runtime's plugin catalogue.
connect.composio.dev, backend.composio.devOnly for the optional Composio card on our Integrations page.
go.microsoft.comOn Windows, the WebView2 Runtime, only when it is missing.
Connected servicesEach service a person connects (Google, Microsoft 365, Slack and others) at that service's own addresses.

How security tools see it

On Windows

Signer. Every installer we publish is signed by a certificate issued to Maxiful AB through Microsoft Artifact Signing (the certificate's subject reads CN=Maxiful AB), and so is the Maxiful.exe it installs. Read a file's signature with Get-AuthenticodeSignature, and compare a download with the checksum on your setup page (Help shows how).

Unsigned parts. The runtime's node.exe and the assistants' chrome.exe carry no Authenticode signature; Maxiful checks each against a pinned SHA-256 before it uses it. An allowlist for them goes by path.

What to allowlist: the processes %LOCALAPPDATA%\Maxiful\Maxiful.exe (signed) and gateway-launcher.exe, %LOCALAPPDATA%\Lanoko\node-v24.22.2\node.exe, and %USERPROFILE%\.openclaw-*\browser\chromium\chrome-win64\chrome.exe; the four Defender folders above; the network hosts above.

On a Mac

Signer. Maxiful.app is signed with the Developer ID of team 467H9AXX55 and notarized by Apple, so Gatekeeper opens it with no override; an allowlist can name it by its code requirement (under Mac: Intune and Jamf Pro). Read its signature with codesign -dvv /Applications/Maxiful.app.

The runtime's parts. The gateway's node is the official Node.js for macOS and the assistants' browser is Google's Chrome for Testing, each downloaded by Maxiful and checked against a pinned SHA-256 before it is used. An allowlist for them goes by path.

What to allowlist: /Applications/Maxiful.app (team 467H9AXX55), ~/Library/Application Support/Lanoko/node-v24.22.2/bin/node and the browser under ~/.openclaw-*/browser/chromium; the network hosts above.

On both

Behaviour. A per-user Node.js process starts at sign-in, makes outbound HTTPS calls, runs commands for the assistants, and copies its plugins' files at each start, so it writes many files under the install's folder.

CrowdStrike. CrowdStrike publishes an OpenClaw "Search & Removal" content pack for Falcon for IT. It looks for running OpenClaw processes, global npm installs, OpenClaw binaries in common paths, services, and state and configuration folders in home folders. Its removal workflow stops services and processes, uninstalls npm packages, deletes installation and configuration folders, and removes service registrations, Scheduled Tasks and launchd plists among them. Maxiful's gateway is a running OpenClaw process with its state in %USERPROFILE%\.openclaw-<name> on Windows and ~/.openclaw-<name> on a Mac, so that pack may find it. Run on a Maxiful computer, its removal could stop the team and delete the assistants' configuration and memory. Use its search to see where Maxiful runs, and keep its removal away from the computers where your organisation uses Maxiful.

Whether to allowlist is your security team's call. These processes run commands for the assistants, inside each assistant's sandbox by default, with the approvals described on our Security page.

Managed settings

Maxiful reads managed settings from version 0.9.60, on Windows and on a Mac; earlier versions do not read them.

An IT department can set a few of Maxiful's settings centrally: with Group Policy or Intune on Windows, and with a configuration profile from Jamf, Intune or another device-management tool on a Mac. Maxiful reads them each time it uses them; a change to one of the owner's switches reaches the assistants when Maxiful next starts, and its settings say so until then. A setting your organisation set shows as Set by your organisation in Maxiful's settings and cannot be changed there, and Maxiful's settings list everything you set at the top of Access. With no policy, Maxiful works as it does on a computer no IT department manages.

NameValueWhat it does
WorkspaceTextMaxiful on the computer opens only the workspace with this ID. The workspace's owner finds the ID in Maxiful's settings, at the top of Access, as The ID of this workspace. A person who is not a member of the workspace sees that your organisation set this and joins the workspace by invitation; their own workspace and any other workspace do not open on that computer.
AutoUpdate0 or 10: Maxiful does not look for, download or install updates, its settings say your organisation installs them, and you push each new installer yourself (see Updates). 1: Maxiful updates itself, as with no policy.
OwnerSwitches0 or 1, eachOne of the owner's switches below, by its name: 0 off, 1 on, whatever the owner chose. A switch you do not set stays the owner's to choose. When you take a value away, the owner's own choice is back, or Maxiful's own setting where the owner never chose; like a value you set, it reaches the assistants when Maxiful next starts.

The owner's switches

NameThe switch in MaxifulWhere it is
terminalOpen a terminal on this computerAccess (Mac only)
private-networkLet assistants open pages on this computer and my networkAccess
pane-reachLet assistants' panes run code and reach outside MaxifulAccess
claude-code-backgroundLet Claude Code keep long commands running in the backgroundAccess
session-reachAssistants can look through all conversations on this computer (so they learn from past work)Access
model-costsShow model costs in dollarsAdvanced
next-promptSuggest my next messageAdvanced
checkin-whole-conversationCheck-ins read the whole conversationAdvanced
voice-notesTranscribe voice notesVoice and audio

Besides a number, Maxiful reads the text 0, 1, true and false as 0 or 1. A value it cannot read, such as other text where 0 or 1 goes, another registry type (REG_QWORD, REG_EXPAND_SZ, REG_BINARY), or a name under OwnerSwitches it does not know, is not applied, and Maxiful's settings name it under Set by your organisation. On Windows that holds for every value under the policy key and its subkey, under HKLM and HKCU alike.

On Windows

Maxiful reads HKLM\SOFTWARE\Policies\Maxiful, then HKCU\SOFTWARE\Policies\Maxiful; a value under HKLM wins over the same value under HKCU. Workspace is a REG_SZ and AutoUpdate a REG_DWORD; each owner's switch is a REG_DWORD under the OwnerSwitches subkey, named as in the table. This ADMX and ADML pair writes exactly these values: save them as maxiful.admx and en-US\maxiful.adml in your policy definitions store, or import them into Intune as imported administrative templates.

maxiful.admx
<?xml version="1.0" encoding="utf-8"?>
<policyDefinitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" revision="1.0" schemaVersion="1.0" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
  <policyNamespaces>
    <target prefix="maxiful" namespace="Maxiful.Policies" />
  </policyNamespaces>
  <resources minRequiredRevision="1.0" />
  <supportedOn>
    <definitions>
      <definition name="SUPPORTED_Maxiful" displayName="$(string.SUPPORTED_Maxiful)" />
    </definitions>
  </supportedOn>
  <categories>
    <category name="Maxiful" displayName="$(string.Maxiful)" />
    <category name="OwnerSwitches" displayName="$(string.OwnerSwitches)">
      <parentCategory ref="Maxiful" />
    </category>
  </categories>
  <policies>
    <policy name="Workspace" class="Both" displayName="$(string.Workspace)" explainText="$(string.Workspace_Explain)" presentation="$(presentation.Workspace)" key="SOFTWARE\Policies\Maxiful">
      <parentCategory ref="Maxiful" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <elements>
        <text id="Workspace" valueName="Workspace" maxLength="128" required="true" />
      </elements>
    </policy>
    <policy name="AutoUpdate" class="Both" displayName="$(string.AutoUpdate)" explainText="$(string.AutoUpdate_Explain)" key="SOFTWARE\Policies\Maxiful" valueName="AutoUpdate">
      <parentCategory ref="Maxiful" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_PrivateNetwork" class="Both" displayName="$(string.OwnerSwitch_PrivateNetwork)" explainText="$(string.OwnerSwitch_PrivateNetwork_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="private-network">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_PaneReach" class="Both" displayName="$(string.OwnerSwitch_PaneReach)" explainText="$(string.OwnerSwitch_PaneReach_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="pane-reach">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_ClaudeCodeBackground" class="Both" displayName="$(string.OwnerSwitch_ClaudeCodeBackground)" explainText="$(string.OwnerSwitch_ClaudeCodeBackground_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="claude-code-background">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_SessionReach" class="Both" displayName="$(string.OwnerSwitch_SessionReach)" explainText="$(string.OwnerSwitch_SessionReach_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="session-reach">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_ModelCosts" class="Both" displayName="$(string.OwnerSwitch_ModelCosts)" explainText="$(string.OwnerSwitch_ModelCosts_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="model-costs">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_NextPrompt" class="Both" displayName="$(string.OwnerSwitch_NextPrompt)" explainText="$(string.OwnerSwitch_NextPrompt_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="next-prompt">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_CheckinWholeConversation" class="Both" displayName="$(string.OwnerSwitch_CheckinWholeConversation)" explainText="$(string.OwnerSwitch_CheckinWholeConversation_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="checkin-whole-conversation">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
    <policy name="OwnerSwitch_VoiceNotes" class="Both" displayName="$(string.OwnerSwitch_VoiceNotes)" explainText="$(string.OwnerSwitch_VoiceNotes_Explain)" key="SOFTWARE\Policies\Maxiful\OwnerSwitches" valueName="voice-notes">
      <parentCategory ref="OwnerSwitches" />
      <supportedOn ref="SUPPORTED_Maxiful" />
      <enabledValue><decimal value="1" /></enabledValue>
      <disabledValue><decimal value="0" /></disabledValue>
    </policy>
  </policies>
</policyDefinitions>
en-US\maxiful.adml
<?xml version="1.0" encoding="utf-8"?>
<policyDefinitionResources xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" revision="1.0" schemaVersion="1.0" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
  <displayName>Maxiful</displayName>
  <description>The settings an IT department sets for Maxiful.</description>
  <resources>
    <stringTable>
      <string id="Maxiful">Maxiful</string>
      <string id="OwnerSwitches">The owner's switches</string>
      <string id="SUPPORTED_Maxiful">Maxiful for Windows</string>
      <string id="Workspace">Open only this workspace</string>
      <string id="Workspace_Explain">Maxiful on this computer opens only the workspace with this ID. The workspace's owner finds the ID in Maxiful's settings, under Access. A person who is not a member of the workspace is asked to join it by invitation, and no other workspace opens on this computer.</string>
      <string id="AutoUpdate">Let Maxiful update itself</string>
      <string id="AutoUpdate_Explain">Disabled: Maxiful does not look for, download or install updates, and you install each new version yourself. Enabled or not configured: Maxiful updates itself.</string>
      <string id="OwnerSwitch_PrivateNetwork">Let assistants open pages on this computer and my network</string>
      <string id="OwnerSwitch_PrivateNetwork_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Access.</string>
      <string id="OwnerSwitch_PaneReach">Let assistants' panes run code and reach outside Maxiful</string>
      <string id="OwnerSwitch_PaneReach_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Access.</string>
      <string id="OwnerSwitch_ClaudeCodeBackground">Let Claude Code keep long commands running in the background</string>
      <string id="OwnerSwitch_ClaudeCodeBackground_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Access.</string>
      <string id="OwnerSwitch_SessionReach">Assistants can look through all conversations on this computer (so they learn from past work)</string>
      <string id="OwnerSwitch_SessionReach_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Access.</string>
      <string id="OwnerSwitch_ModelCosts">Show model costs in dollars</string>
      <string id="OwnerSwitch_ModelCosts_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Advanced.</string>
      <string id="OwnerSwitch_NextPrompt">Suggest my next message</string>
      <string id="OwnerSwitch_NextPrompt_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Advanced.</string>
      <string id="OwnerSwitch_CheckinWholeConversation">Check-ins read the whole conversation</string>
      <string id="OwnerSwitch_CheckinWholeConversation_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Advanced.</string>
      <string id="OwnerSwitch_VoiceNotes">Transcribe voice notes</string>
      <string id="OwnerSwitch_VoiceNotes_Explain">Enabled: on. Disabled: off. Not configured: the owner decides, in Maxiful's settings under Voice and audio.</string>
    </stringTable>
    <presentationTable>
      <presentation id="Workspace">
        <textBox refId="Workspace">
          <label>Workspace ID</label>
        </textBox>
      </presentation>
    </presentationTable>
  </resources>
</policyDefinitionResources>

On a Mac

Maxiful reads the managed preferences of its own domain, ai.maxiful.desktop, which a configuration profile installs as forced settings (Apple's managed preferences payload, com.apple.ManagedClient.preferences). Only a value the profile sets counts: one written any other way, such as with defaults write, is not read. Workspace is a string, AutoUpdate an integer (or a boolean), and OwnerSwitches a dictionary of the names in the table. This example profile keeps the computer to one workspace, leaves updates to you, turns the terminal and private-network switches off and shows model costs; replace the workspace ID, and the identifiers and UUIDs with your own.

maxiful.mobileconfig
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>PayloadType</key><string>Configuration</string>
  <key>PayloadVersion</key><integer>1</integer>
  <key>PayloadIdentifier</key><string>com.example.maxiful</string>
  <key>PayloadUUID</key><string>00000000-0000-0000-0000-000000000001</string>
  <key>PayloadDisplayName</key><string>Maxiful</string>
  <key>PayloadScope</key><string>System</string>
  <key>PayloadContent</key>
  <array>
    <dict>
      <key>PayloadType</key><string>com.apple.ManagedClient.preferences</string>
      <key>PayloadVersion</key><integer>1</integer>
      <key>PayloadIdentifier</key><string>com.example.maxiful.settings</string>
      <key>PayloadUUID</key><string>00000000-0000-0000-0000-000000000002</string>
      <key>PayloadDisplayName</key><string>Maxiful settings</string>
      <key>PayloadContent</key>
      <dict>
        <key>ai.maxiful.desktop</key>
        <dict>
          <key>Forced</key>
          <array>
            <dict>
              <key>mcx_preference_settings</key>
              <dict>
                <key>Workspace</key><string>YOUR-WORKSPACE-ID</string>
                <key>AutoUpdate</key><integer>0</integer>
                <key>OwnerSwitches</key>
                <dict>
                  <key>terminal</key><false/>
                  <key>private-network</key><false/>
                  <key>model-costs</key><true/>
                </dict>
              </dict>
            </dict>
          </array>
        </dict>
      </dict>
    </dict>
  </array>
</dict>
</plist>

Updates

Maxiful looks for a new version on maxiful.ai when it starts and every six hours. The person chooses Update and restart or Later. A new Maxiful version can carry a newer OpenClaw runtime; Maxiful then updates the runtime for that person with npm, from registry.npmjs.org.

To install every new version yourself and have Maxiful look for none, on Windows or on a Mac, set AutoUpdate to 0 (see Managed settings): Maxiful then says that your organisation installs its updates.

On Windows

A new version is a signed installer, checked against a key built into the app before it runs, and the update runs the installer in passive mode. You can also push each new installer yourself with /S, as above.

On a Mac

A new version is a signed archive of the app, checked against a key built into the app before it is used, and it replaces the app in place where the person's account can change that copy.

A copy the person cannot change. Where /Applications/Maxiful.app belongs to the system (its owner is root) and the person's account cannot change it, Maxiful does not update it itself: it downloads nothing, never asks for an administrator's password, offers no Update and restart, and says, where it shows updates, that a newer version is available and that your organisation installs updates for this Mac. Push each new version with your MDM: in Intune, upload its disk image to the same app; in Jamf Pro, build its package with Composer and deploy it as above. A copy that an administrator's account can change updates itself for that account as on any Mac.

Removing Maxiful

Everything, by the person: in Maxiful's settings, Remove Maxiful from this computer. It stops the background process and what starts it at sign-in (its scheduled tasks on Windows, its LaunchAgent on a Mac), deletes the install's data and credentials, and removes the Node.js runtime it installed unless another install on the computer still uses it. On Windows it then starts the uninstaller when Maxiful quits; on a Mac it moves the app to the Trash where the person's account can. The person's own documents are not touched.

On Windows

Everything, silently: %LOCALAPPDATA%\Maxiful\uninstall.exe /S /REMOVEALL runs Remove Maxiful from this computer for the person whose install it is, with nobody at the screen, and then removes the app. It cannot be undone. What it removed, and anything it could not, is in removal-report.json in %LOCALAPPDATA%\ai.maxiful.desktop\logs.

Without /REMOVEALL: %LOCALAPPDATA%\Maxiful\uninstall.exe /S, which the Intune recipe above runs, removes the app, its shortcuts, the team keeper task and the Defender exclusions Maxiful added (Windows may show its prompt again for those). It also stops the assistants' background process and removes what starts it at sign-in, and keeps the runtime and the install's data. installer.log, beside the app's other logs, says whether anything was left running.

On a Mac

Run Remove Maxiful from this computer for each person first: removing only the app leaves that person's background gateway running with everything it holds. Then remove /Applications/Maxiful.app with your MDM, for example with an Intune Uninstall assignment.