@tempr/cli 0.9.23 → 0.9.25

package/README.md

@@ -20,7 +20,7 @@ curl -fsSL https://temprhq.io/cli/install.sh | sh
 irm https://temprhq.io/cli/install.ps1 | iex
 ```
 
-Or download an archive for your platform from https://temprhq.io/cli#downloads (the current release
+Or download an archive for your platform from https://temprhq.io/download#cli (the current release
 is always at `https://temprhq.io/cli/latest/tempr-<rid>.zip` or `.tar.gz`, for `win-x64`,
 `win-arm64`, `osx-arm64`, `osx-x64`, `linux-x64` and `linux-arm64`) and put `tempr` on your `PATH`;
 each one ships with a `.sha256` next to it. `tempr update` checks for a newer release and tells you
@@ -283,9 +283,20 @@ Lists (rules, hooks, directories) combine; for a single value the file higher up
   server off, and `enabledMcpjsonServers` / `enableAllProjectMcpServers` in your own or managed
   settings start them without the folder's OK.
 - **Managed settings** also take `allowManagedPermissionRulesOnly`, `allowManagedHooksOnly` and
-  `disableAllHooks`, and the sandbox's `network.allowUnixSockets` and `allowAllUnixSockets`. Keys
-  Tempr doesn't apply yet (such as `availableModels`, the other `sandbox` keys or `managed-mcp.json`)
-  get one warning at the start of a session.
+  `disableAllHooks`, and Claude Code's managed-only restrictions, which win over every other file and
+  over the flags: `availableModels`, `availableModelsMatch`, `deniedModels` and `allowedProviders`
+  (pickers, `--model`, `config set-model` and every turn); `managed-mcp.json` and
+  `managedMcpServers`; `strictKnownMarketplaces`, `blockedMarketplaces`,
+  `disableCommandPluginSources`, `disableSideloadFlags` (`--plugin-dir`) and
+  `strictPluginOnlyCustomization`; `sshHostAllowlist` (`--env ssh:`); the `permissions` blocks
+  `blockReadsOutsideWorkingDirectories`, `blockWritesOutsideWorkingDirectories` and
+  `denyInsteadOfPrompting`; and the `sandbox` keys that map onto Tempr's sandbox (`enabled`,
+  `failIfUnavailable`, `allowUnsandboxedCommands`, `autoAllowBashIfSandboxed`,
+  `network.allowManagedDomainsOnly` with no domains listed, `network.allowUnixSockets`,
+  `allowAllUnixSockets`, `filesystem.allowWrite`, `denyRead`, `denyWrite`). `tempr doctor` lists what's
+  locked. The keys Tempr doesn't apply (`forceLoginMethod`, `forceLoginOrgUUID`, `policyHelper`,
+  `channelsEnabled`, and the `sandbox` keys with no equivalent) get one warning at the start of a
+  session. See [Managed settings](https://temprhq.io/docs/cli-config#managed).
 
 A folder's hooks, allow rules, additional directories, `env` variables, its entries in
 `allowedMcpServers`, `allowedHttpHookUrls` and `httpHookAllowedEnvVars`, and its `.mcp.json` servers

package/package.json

@@ -1,17 +1,17 @@
 {
     "name": "@tempr/cli",
-    "version": "0.9.23",
+    "version": "0.9.25",
     "description": "Sign in, chat, and run agentic coding tasks against your Tempr license from the terminal.",
     "homepage": "https://temprhq.io",
     "license": "SEE LICENSE IN README.md",
     "bin": { "tempr": "bin/tempr.js" },
     "files": ["bin/"],
     "optionalDependencies": {
-        "@tempr/cli-win32-x64": "0.9.23",
-        "@tempr/cli-win32-arm64": "0.9.23",
-        "@tempr/cli-linux-x64": "0.9.23",
-        "@tempr/cli-linux-arm64": "0.9.23",
-        "@tempr/cli-darwin-x64": "0.9.23",
-        "@tempr/cli-darwin-arm64": "0.9.23"
+        "@tempr/cli-win32-x64": "0.9.25",
+        "@tempr/cli-win32-arm64": "0.9.25",
+        "@tempr/cli-linux-x64": "0.9.25",
+        "@tempr/cli-linux-arm64": "0.9.25",
+        "@tempr/cli-darwin-x64": "0.9.25",
+        "@tempr/cli-darwin-arm64": "0.9.25"
     }
 }