Managing Bohm — for IT teams

Values

Bohm reads administrator policy from the registry key HKLM\SOFTWARE\Policies\iyulab\Bohm. Set the values with Group Policy (Preferences › Registry), Intune or an install script — people without administrator rights cannot change them. A value that is absent leaves the default in place. Bohm reads the AI server values when it starts; the on/off switches are read again each time they apply, so changing one takes effect without a restart.

ValueEffect
CompanyModels
REG_SZ
The AI servers and models on your network that people choose from — one line of JSON, up to 16 KiB (see below). Takes precedence over the two values below. When absent: People connect a server themselves.
CompanyModelEndpoint
CompanyModel
REG_SZ
One AI server: its OpenAI-compatible base address (http://ai.example:8000/v1) and the model name it serves. Both are needed — one alone is ignored. When absent: People connect a server themselves.
RemotePageReadingAllowed
REG_DWORD
0: when an online AI service someone connected answers in the chat, it reads no web page at all. A server on your network and a model on the PC still read pages. Nor does it read a page for an app that has the AI fill in its columns. When absent: Only the sites below and addresses inside your network are held back.
RemotePageExcludedSites
REG_MULTI_SZ
Sites never sent to an online AI service, one per line — a host name (covers its subdomains), *.example.com or an IP address. Private addresses and single-label or .local names are held back without being listed. When absent: Only addresses inside your network are held back.
AgentActLevel
REG_DWORD
The widest step people may choose for letting the AI act on web pages. 0: the AI never opens, clicks or types on a site by itself — it only reads and answers about the tabs people opened · 1 “Read only — never click or type” · 2 “Ask before important steps” · 3 “Ask only before payments, deletions and the like”. People choose only up to it, and the setting says the organization sets the widest choice. When absent: No ceiling.
AgentBlockedSites
REG_MULTI_SZ
Sites the AI never opens or acts on, one per line — written as for RemotePageExcludedSites (a host name covers its subdomains). Neither an “Always” a person gave nor a direct request lifts it; people can still open the site themselves. Reading a page to answer a question is governed by RemotePageExcludedSites. When absent: None.
DiagnosticsAllowed
REG_DWORD
0: no crash and error reports and no daily “started” note are recorded or sent. When absent: Sent.
UsageSharingAllowed
REG_DWORD
0: the “Send usage to improve Bohm” choice is not offered — the usage record can only be saved to a file. 1: people can send the weekly usage record but not the quality data (a summary of how each chat question went — counts and set names only). When absent: People choose among don't send, usage record, and usage record + quality data (off by default).
FeedbackAllowed
REG_DWORD
0: “Tell us” (report a problem, get news) is not shown. When absent: Shown.
ExternalAiHandoffAllowed
REG_DWORD
0: when no AI is set up for making or changing an app, Bohm does not offer to copy the request — with the app's code, when changing one — for an AI service the person uses elsewhere. Bohm sends nothing on this path — the person pastes. When absent: Offered. The copied text holds the request and, when changing, the app's code — never the data entered in an app.
UpdateCheckAllowed
REG_DWORD
0: Bohm neither checks for nor downloads new versions — it stays at the version IT installed. When absent: Checked when Bohm starts and every 6 hours; a new version is downloaded, its signature checked, and installed on restart or when Bohm closes.
ModelDownloadAllowed
REG_DWORD
0: Bohm does not offer to get an AI model (a chat model or the speech-to-text model) from the internet for this PC — people can still choose a model file that is already on the PC or on a shared folder. When absent: Offered; a model is downloaded only when someone presses Get, after being shown its size and licence.
McpAllowed
REG_DWORD
0: people cannot give the AI MCP servers — programs on the PC that Bohm would start, or addresses it would reach. None is listed, started or offered to the AI, and none can be added in Settings or in the chat. When absent: People add servers themselves, in Settings or by approving one the chat proposes; every use of a server's tool while making or changing an app is asked first, or allowed by the person for the rest of that one task. A chat answer can use a server's tool too, and every such use is asked first.
RemoteProvidersAllowed
REG_DWORD
0: the AI answers only from the company AI servers in CompanyModels (or the older two values) and the AI model on this PC. Online AI services and servers people add themselves are not offered, cannot be added or connected with a key, and an app's call to an online AI service is answered by a company server or this PC's model instead, or refused — nothing is sent to that service. When absent: People may connect an AI service key or add an AI server of their own.
SmartScreenAllowed
REG_DWORD
0: web tabs open with Microsoft Defender SmartScreen off — the addresses people visit are not checked with Microsoft. When absent: Web tabs check addresses with SmartScreen, as Microsoft Edge does; Bohm's own screens and apps never do. Windows only.
PasswordSaveAllowed
REG_DWORD
0: Bohm does not offer to save passwords on websites, and the Settings line for it is not shown. Passwords saved before are still filled in, and can still be removed in Settings. When absent: Offered; passwords are kept by the WebView2 password manager, encrypted on the PC, filled in only on the site they were saved for, and never sent anywhere by Bohm. On a Mac Bohm does not save passwords, so this value has no effect there.
Registries
REG_MULTI_SZ
App registries — folder paths (\\server\share\apps, D:\apps), one per line. Their apps are always listed under “Team apps” on a new tab, and people cannot remove them. When absent: People add folders themselves.
AllowedRegistries
REG_MULTI_SZ
Folders, one per line. When set, the registries people add themselves must be one of these folders or inside one; others are refused, and ones added before are hidden. When absent: Any folder.

To keep anything from going to iyulab, set FeedbackAllowed, DiagnosticsAllowed and UsageSharingAllowed to 0.

The installer installs for the current Windows user and registers .bohm app packages to open with Bohm under HKCU — no administrator rights and nothing machine-wide.

Making Bohm the default browser

The installer also registers Bohm as a web browser for the current user (it then appears in Windows Settings › Default apps, and links open in a new Bohm tab). Windows does not let an app make itself the default: when Bohm starts and is not the default, it asks once whether to open Default apps for it, and people can ask again from its settings. To make Bohm the default for everyone, use the standard Windows group policy Set a default associations configuration file (Computer Configuration › Administrative Templates › Windows Components › File Explorer) with a file like this — it applies when people sign in:

<?xml version="1.0" encoding="UTF-8"?>
<DefaultAssociations>
  <Association Identifier="http" ProgId="BohmHTML" ApplicationName="Bohm" />
  <Association Identifier="https" ProgId="BohmHTML" ApplicationName="Bohm" />
</DefaultAssociations>

The model list

{"providers": {
  "gpu": {"baseUrl": "http://ai.example:8000/v1", "api": "openai-completions",
          "models": [{"id": "qwen3-32b", "name": "Qwen3 32B", "contextWindow": 32768, "maxTokens": 8192, "reasoning": true},
                     {"id": "qwen3-8b", "name": "Qwen3 8B", "contextWindow": 32768, "maxTokens": 4096}]},
  "vision": {"baseUrl": "http://vision.example:8000/v1",
             "models": [{"id": "qwen2.5-vl", "input": ["text", "image"]}]}
}}
  • Server names (gpu, vision) are up to 64 characters, without /. People choose among the listed models; the first model of the first server is the default.
  • baseUrl is the OpenAI-compatible base address. api may be left out, or be openai-completions, openai-compatible or openai — a server with any other value is skipped.
  • Each model needs id (the name the server uses). name is shown to people; contextWindow and maxTokens are in tokens; reasoning: true marks a model that thinks first; input lists text and image.
  • Without contextWindow, Bohm reads the value the server reports in its model list (vLLM's max_model_len) once, the first time the model is used. If the server reports none, Bohm shortens a request the server turns down as too long and asks again.
  • Do not put keys in the registry — every user of the PC can read it, and Bohm ignores an apiKey. If a server needs a key, people enter it in Bohm's settings, where it is kept in the Windows credential store.
  • Anything unusable (a malformed address, a model without id, a repeated name) is skipped and the rest is used. If nothing is usable, Bohm starts without the policy.

On a Mac

On macOS, Bohm reads the same values from the managed preferences of its app domain app.bohm.browser — what a configuration profile installed by your device management (Jamf, Intune, Kandji or any other MDM) enforces. Only enforced values count: a value someone writes with defaults is not a policy. The names and meanings are the ones in the table above; a REG_DWORD value is an integer (or a boolean), a REG_SZ value a string, and a REG_MULTI_SZ value an array of strings. Registries are folder paths on the Mac (/Volumes/apps). A profile like this one sets four of them:

<?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.bohm-policy</string>
  <key>PayloadUUID</key><string>6E1A2B9C-0F3D-4C2E-9B1A-5D7E8F901234</string>
  <key>PayloadDisplayName</key><string>Bohm policy</string>
  <key>PayloadScope</key><string>System</string>
  <key>PayloadContent</key>
  <array>
    <dict>
      <key>PayloadType</key><string>app.bohm.browser</string>
      <key>PayloadVersion</key><integer>1</integer>
      <key>PayloadIdentifier</key><string>com.example.bohm-policy.values</string>
      <key>PayloadUUID</key><string>0B4C6D8E-2A1F-4E3D-8C5B-7A9F1E2D3C4B</string>
      <key>UpdateCheckAllowed</key><integer>0</integer>
      <key>DiagnosticsAllowed</key><integer>0</integer>
      <key>CompanyModelEndpoint</key><string>http://ai.example:8000/v1</string>
      <key>CompanyModel</key><string>qwen3-32b</string>
      <key>Registries</key>
      <array><string>/Volumes/apps</string></array>
    </dict>
  </array>
</dict>
</plist>

Most device management tools take the inner payload alone, as custom settings for the domain app.bohm.browser.

What Bohm itself connects to

Address (HTTPS)ForTurned off by
*.in.applicationinsights.azure.comDiagnostics, and the usage record if someone turns it onDiagnosticsAllowed, UsageSharingAllowed
api.iyulab.com“Tell us”, only when someone presses SendFeedbackAllowed
github.com, release-assets.githubusercontent.comThe number of the newest public release, when Bohm starts and every 6 hours — and, when there is a newer one, its installer (about 270 MB, from GitHub's release storage)UpdateCheckAllowed
huggingface.co, *.huggingface.co, *.hf.coAn AI model for this PC, only when someone presses Get (its size first, then the files)ModelDownloadAllowed
The CDNs an app loads code from (cdn.jsdelivr.net, unpkg.com, cdnjs.cloudflare.com and the like)The code libraries an app names, fetched once when it is brought in or a new version is applied, then kept on the PC; a library that could not be reached then is fetched again when the network comes back or the app is opened (at most every five minutes per app) — the app itself never reaches out— (blocked, the app runs without those libraries and may look incomplete)
The search engine people choose, duckduckgo.com, and the sites the chat opensThe chat's web search and the pages it opens for someone. When the chosen engine's robots.txt keeps AI out, the search goes to DuckDuckGo; before opening a site it chose itself, the AI reads that site's robots.txt— (people's own browsing)
config.edge.skype.com, edge.microsoft.com and other Microsoft addressesOpened by Microsoft WebView2 — the Edge engine Bohm shows web pages with — for its own settings and updates, not by Bohm's codeMicrosoft Edge WebView2 policies; blocking them does not stop Bohm

Blocking any of them at the firewall does not stop a feature: reports wait — up to 50, for seven days — and older ones are dropped, a message that cannot be sent can be mailed or copied instead, and the update check simply skips that day. The only thing Bohm downloads and installs by itself is its own new version, signed by iyulab — turn that off withUpdateCheckAllowed to roll out versions yourself.

Beyond these, Bohm reaches only what people set up themselves: an AI service or server they connect, and the MCP servers they add, a program on the PC or an address of their choosing. Turn MCP servers off with McpAllowed, and AI services and servers other than the company's with RemoteProvidersAllowed.

A person can also have an app read its web page again on a schedule they pick (every minute at the most often) while Bohm is open — the same page they allowed the app to read, from this PC, with their own sign-ins, and no AI. Bohm reads that site's robots.txt (once a day per site) and keeps to the Crawl-delayit asks for, and waits as long as a busy site asks (Retry-After). When the site asks automated visitors to stay out of that page, Bohm tells the person before turning the schedule on and turns it on only if they choose to.

Before the AI opens a site it chose itself, Bohm asks the person. Always keeps only that site's origin (scheme, host and port — no path, no content) in the settings file on that PC; the person takes it back in settings under What you allowed. It is never sent anywhere and is not part of a diagnostic report. No policy value turns the question off.

Older versions

The sections above describe the current version. On a PC still running an older one, these differ:

  • From 0.11.0: with an online AI service connected, a page is not sent to an app when RemotePageReadingAllowed is 0, and the person is asked first for a page under RemotePageExcludedSites.
  • From 0.12.6: MCP servers, and McpAllowed. From 0.12.7 a server can be allowed for one task; from 0.12.14 the chat can use servers too.
  • From 0.12.13: reading an app's page on a schedule. Before 0.13.0 it was not turned on for a page whose site asks automated visitors to stay out.
  • From 0.13.0: saving passwords, and PasswordSaveAllowed.
  • From 0.13.1: a library that could not be reached is fetched again when the network comes back.
  • From 0.14.0: the installer registers Bohm as a browser (so it can be made the default), and the quality-data choice with the value 1 of UsageSharingAllowed (usage record only). An older version has only the usage record, so 1 allows it there too.
  • From 0.16.0: Bohm asks before the AI opens a site it chose itself, with an Always answer kept in the settings file. Earlier versions open such a site without asking.
  • From 0.17.1: RemoteProvidersAllowed. An earlier version ignores it, so people there can still connect an AI service.
  • From 0.17.4: SmartScreen in web tabs, and SmartScreenAllowed. Earlier versions open web tabs with SmartScreen off.
  • Until 0.17.5: sending a page to an app (the two page-reading values above applied to it). From 0.17.6 an app reads the page itself, and the two values apply when the AI fills in its columns.
  • From 0.17.8: an app reads a page without a table on a schedule and has the AI fill in its columns (the person allows it for each page) — the two page-reading values above apply to that reading too. Earlier versions do not read such a page on a schedule.