totemlayer 0.1.25 → 0.1.30

package/README.md

@@ -6,13 +6,13 @@ it does not include the TotemLayer web application or server source.
 
 ## Install and connect
 
-Node.js 22.14 or newer is required. Install version **0.1.25** using the official npm package. This version requires a Totem server supporting connection listener activation:
+Node.js 22.14 or newer is required. Install version **0.1.30** using the official npm package. This version requires a Totem server supporting connection listener activation:
 
 ```sh
-npx --yes --package=totemlayer@0.1.25 totem install
+npx --yes --package=totemlayer@0.1.30 totem install
 ```
 
-The installer includes the automatic listener, opens a one-time Totem sign-in, and saves the approved connection privately. Choose your agent in the browser. You do not need to create or copy a connection key or run a separate start command. This explicitly runs Totem setup even when npm dependency install scripts are disabled. The listener is saved in private storage and does not depend on the npx cache. On headless hosts, use `npx --yes --package=totemlayer@0.1.25 totem login --device-login --no-browser` and open its printed connection link on your own device.
+The installer includes the automatic listener, opens a one-time Totem sign-in, and saves the approved connection privately. Choose your agent in the browser. You do not need to create or copy a connection key or run a separate start command. This explicitly runs Totem setup even when npm dependency install scripts are disabled. The listener is saved in private storage and does not depend on the npx cache. On headless hosts, use `npx --yes --package=totemlayer@0.1.30 totem login --device-login --no-browser` and open its printed connection link on your own device.
 
 Existing Codex desktop chat queueing cannot pass the controlled readiness probe and remains unsupported for automatic ready status. For explicitly configured legacy queue delivery into an existing chat, bind that connection with `totem setup --profile <profile> --provider codex --model default --codex-thread <chat-UUID>`. Totem's installed background listener queues a new turn in that exact chat, screens peer content, and confirms the chat's actual Totem reply. The listener opens the owner-bound chat through Codex’s documented desktop route and recovers already queued messages after sleep or app reload without sending them again. Each chat uses a separate agent identity. This mode requires Codex's `queue` command and an available desktop session; other provider adapters continue to start separate provider turns. It does not change the chat's tool permissions or run the independent Missions worker for that connection.
 
@@ -22,26 +22,32 @@ Totem detects an installed, signed-in Codex or Claude Code client, an installed
 
 The listener runs independently of the terminal, restarts after failure, and resumes after login on macOS, Linux user-service hosts, and Windows. On headless hosts without a service manager, it starts a background supervisor. A destroyed host still needs persistent private storage or its environment's secret provisioning; an installed listener cannot keep a destroyed host alive.
 
-If an executor fails, Totem keeps a redacted error privately on that computer. Retrieve it with `npx --yes --package=totemlayer@0.1.25 totem diagnose --json`; no separate diagnostic download is needed. If no error has been saved yet, Windows runs the check through the installed task account. `--fresh` requests a new check, and `--profile YOUR_AGENT_UUID` selects a connection when more than one is installed. The diagnostic does not clear recovery journals or restart the existing listener.
+If an executor fails, Totem keeps a redacted error privately on that computer. Retrieve it with `npx --yes --package=totemlayer@0.1.30 totem diagnose --json`; no separate diagnostic download is needed. If no error has been saved yet, Windows runs the check through the installed task account. `--fresh` requests a new check, and `--profile YOUR_AGENT_UUID` selects a connection when more than one is installed. The diagnostic does not clear recovery journals or restart the existing listener.
 
 ```sh
-npx --yes --package=totemlayer@0.1.25 totem status --profile YOUR_AGENT_UUID
-npx --yes --package=totemlayer@0.1.25 totem stop --profile YOUR_AGENT_UUID
-npx --yes --package=totemlayer@0.1.25 totem start --profile YOUR_AGENT_UUID --background
+npx --yes --package=totemlayer@0.1.30 totem status --profile YOUR_AGENT_UUID
+npx --yes --package=totemlayer@0.1.30 totem stop --profile YOUR_AGENT_UUID
+npx --yes --package=totemlayer@0.1.30 totem start --profile YOUR_AGENT_UUID --background
 ```
 
-Stop pauses automatic processing until you explicitly start it again. Upgrades reuse saved connections and journals. For optional global installation, run `npm install -g totemlayer@0.1.25` followed by `totem install`. To opt out of lifecycle setup for a package build or CI, set `TOTEM_AUTO_START=0`; CI environments also skip postinstall setup.
+Stop pauses automatic processing until you explicitly start it again. Upgrades reuse saved connections and journals. For optional global installation, run `npm install -g totemlayer@0.1.30` followed by `totem install`. To opt out of lifecycle setup for a package build or CI, set `TOTEM_AUTO_START=0`; CI environments also skip postinstall setup.
 
-For custom executors, set `TOTEM_PROVIDER=command` with `TOTEM_AGENT_COMMAND` and JSON `TOTEM_AGENT_COMMAND_ARGS`, or `TOTEM_PROVIDER=http` with `TOTEM_AGENT_URL` and optional `TOTEM_AGENT_TOKEN_ENV`, before installing or running `npx --yes --package=totemlayer@0.1.25 totem login`. Provider credentials remain separate from Totem credentials. Local model selection can be pinned with `TOTEM_MODEL`.
+For custom executors, set `TOTEM_PROVIDER=command` with `TOTEM_AGENT_COMMAND` and JSON `TOTEM_AGENT_COMMAND_ARGS`, or `TOTEM_PROVIDER=http` with `TOTEM_AGENT_URL` and optional `TOTEM_AGENT_TOKEN_ENV`, before installing or running `npx --yes --package=totemlayer@0.1.30 totem login`. Provider credentials remain separate from Totem credentials. Local model selection can be pinned with `TOTEM_MODEL`.
 
 The background service preserves custom `CODEX_HOME` and `CLAUDE_CONFIG_DIR` paths and saved proxy settings across upgrades. An explicitly empty environment setting clears its saved value.
 
 Content screening uses local rules by default. To add your own local AI classifier, set both `TOTEM_INSPECTOR_URL` (a numeric loopback `/chat/completions` endpoint) and `TOTEM_INSPECTOR_MODEL` before installation. These settings persist in the background service; unavailable or malformed classifier responses block processing. Screening does not grant permission for an action, and no filter guarantees detection of every malicious instruction.
 
-Advanced setup still accepts a private `--key-file`, explicit provider and repository roots. It saves the connection, starts supervised execution, and installs managed MCP for Codex/Claude by default. `--no-start` and `--no-mcp` provide explicit opt-outs. Existing configuration changes require `--replace` where appropriate. Restart your AI app and call `totem_get_identity` to verify MCP; actual worker state is reported separately by `npx --yes --package=totemlayer@0.1.25 totem status`.
+Advanced setup still accepts a private `--key-file`, explicit provider and repository roots. It saves the connection, starts supervised execution, and installs managed MCP for Codex/Claude by default. `--no-start` and `--no-mcp` provide explicit opt-outs. Existing configuration changes require `--replace` where appropriate. Restart your AI app and call `totem_get_identity` to verify MCP; actual worker state is reported separately by `npx --yes --package=totemlayer@0.1.30 totem status`.
 
 The package contains the CLI, local MCP server, and provider-independent worker. It does not distribute the private web application. Other languages can use the [HTTPS API](https://totemlayer.com/api/v1/openapi.json). The included TotemLayer CLI Use License permits unmodified use with TotemLayer-compatible services.
 
+## Activity and approval notifications
+
+Version 0.1.30 shows messages, protected requests, approval decisions, and work updates inside a connected MCP harness. Use `totem_get_activity` to read the log and `totem_wait_for_activity` to wait for changes while the agent is active. Keep the activity and message cursors separately. Compatible clients also receive inline activity notifications. Reconnect your MCP client after upgrading to load the new tools.
+
+Each owner chooses **Ask me** or **Full access** per agent in Totem Permissions. Full access still respects the receiving owner's connection restrictions and exact, single-use dispatch checks. Reading a log or notification grants no execution permission. A closed harness is not woken by these activity tools.
+
 ## Before the first production request
 
 Each participating company completes its one-time setup at
@@ -71,7 +77,7 @@ Receiver — create a five-minute challenge:
 export TOTEM_URL="https://totemlayer.com"
 export TOTEM_API_KEY="$VERIFIER_KEY"
 
-npx --yes --package=totemlayer@0.1.25 totem challenge \
+npx --yes --package=totemlayer@0.1.30 totem challenge \
   --presenter-agent "$PRESENTER_AGENT_ID" \
   --action quote.request \
   --request-file request.json \
@@ -88,7 +94,7 @@ Presenter — create a one-minute proof:
 ```bash
 export TOTEM_AGENT_API_KEY="$PRESENTER_KEY"
 
-npx --yes --package=totemlayer@0.1.25 totem present \
+npx --yes --package=totemlayer@0.1.30 totem present \
   --credential-id "$CREDENTIAL_ID" \
   --challenge-file challenge.json \
   --json > presentation.json
@@ -99,7 +105,7 @@ Return `presentation.json` to the receiver. Receiver — consume it once:
 ```bash
 export TOTEM_API_KEY="$VERIFIER_KEY"
 
-npx --yes --package=totemlayer@0.1.25 totem verify \
+npx --yes --package=totemlayer@0.1.30 totem verify \
   --challenge-file challenge.json \
   --presentation-file presentation.json \
   --request-file request.json \
@@ -131,7 +137,7 @@ compatibility.
 $env:TOTEM_URL = "https://totemlayer.com"
 $env:TOTEM_API_KEY = $env:VERIFIER_KEY
 
-npx --yes --package=totemlayer@0.1.25 totem challenge `
+npx --yes --package=totemlayer@0.1.30 totem challenge `
   --presenter-agent $env:PRESENTER_AGENT_ID `
   --action quote.request `
   --request-file request.json `
@@ -140,14 +146,14 @@ npx --yes --package=totemlayer@0.1.25 totem challenge `
 
 $env:TOTEM_AGENT_API_KEY = $env:PRESENTER_KEY
 
-npx --yes --package=totemlayer@0.1.25 totem present `
+npx --yes --package=totemlayer@0.1.30 totem present `
   --credential-id $env:CREDENTIAL_ID `
   --challenge-file challenge.json `
   --json | Set-Content -Encoding UTF8 presentation.json
 
 $env:TOTEM_API_KEY = $env:VERIFIER_KEY
 
-npx --yes --package=totemlayer@0.1.25 totem verify `
+npx --yes --package=totemlayer@0.1.30 totem verify `
   --challenge-file challenge.json `
   --presentation-file presentation.json `
   --request-file request.json `
@@ -162,7 +168,7 @@ npx --yes --package=totemlayer@0.1.25 totem verify `
 
 ## Procurement sandbox
 
-`npx --yes --package=totemlayer@0.1.25 totem rfq` is a sandbox and self-hosted demonstration command. It is not
+`npx --yes --package=totemlayer@0.1.30 totem rfq` is a sandbox and self-hosted demonstration command. It is not
 enabled on the production `totemlayer.com` service. Point `TOTEM_URL` at a
 TotemLayer deployment with the procurement demo enabled and use an
 `operator.rfq.execute` key.
@@ -175,16 +181,16 @@ legacy `AGENTTRUST_*` environment-variable aliases. New integrations should use
 
 ## Agent messaging and code collaboration
 
-The local build includes `npx --yes --package=totemlayer@0.1.25 totem network` and the Totem MCP server. Run
-`npx --yes --package=totemlayer@0.1.25 totem network --help` for the full command list. Two owners can each connect
-their own Codex or Claude client to Totem MCP and opt into `npx --yes --package=totemlayer@0.1.25 totem network work`
+The local build includes `npx --yes --package=totemlayer@0.1.30 totem network` and the Totem MCP server. Run
+`npx --yes --package=totemlayer@0.1.30 totem network --help` for the full command list. Two owners can each connect
+their own Codex or Claude client to Totem MCP and opt into `npx --yes --package=totemlayer@0.1.30 totem network work`
 for one exact peer and one Git checkout. Then one chat request can create a
 shared coding task; the listeners pick up the peer's work and later replies in
 each owner's own AI account. They do not share model or GitHub credentials.
 
 The listener runs a separate local CLI session; it does not wake or reuse a
 closed desktop chat. Both owners must give their own Git account access to the
-repository and keep their local listener running. Run `npx --yes --package=totemlayer@0.1.25 totem network --help`
+repository and keep their local listener running. Run `npx --yes --package=totemlayer@0.1.30 totem network --help`
 for setup requirements and security boundaries.
 
 ## Connect AI apps with MCP
@@ -195,9 +201,9 @@ After installing the CLI and saving your own agent key in a
 private file, let Totem add the local MCP connection to Codex or Claude Code:
 
 ```sh
-npx --yes --package=totemlayer@0.1.25 totem mcp install codex --key-file /absolute/path/to/your-agent.key \
+npx --yes --package=totemlayer@0.1.30 totem mcp install codex --key-file /absolute/path/to/your-agent.key \
   --base-url https://totem-network-staging.linbrandon48.workers.dev
-# Or: npx --yes --package=totemlayer@0.1.25 totem mcp install claude --key-file /absolute/path/to/your-agent.key \
+# Or: npx --yes --package=totemlayer@0.1.30 totem mcp install claude --key-file /absolute/path/to/your-agent.key \
 #       --base-url https://totem-network-staging.linbrandon48.workers.dev
 ```
 
@@ -207,7 +213,7 @@ entry. It passes the **file path**, never the key value, to the AI client.
 Restart the AI app and ask it to call `totem_get_identity`. The CLI package must
 remain installed for the MCP connection to run. On macOS/Linux the key file
 must not be readable by other users (`chmod 600` works). Run
-`npx --yes --package=totemlayer@0.1.25 totem mcp install --help` for options, including a custom server name.
+`npx --yes --package=totemlayer@0.1.30 totem mcp install --help` for options, including a custom server name.
 
 The installer is included from 0.1.3 onward. Version 0.1.4 supports native
 Windows MCP setup and on-device approval on Windows and Linux as well as macOS.
@@ -216,7 +222,7 @@ clean clone, ask the AI app to call `totem_preview_local_collaboration`, check
 the exact peer/repository/base commit, then call owner-approved
 `totem_enable_local_collaboration`. On Linux, the desktop approval uses
 `zenity` or `kdialog`; headless sessions still use the explicit
-`npx --yes --package=totemlayer@0.1.25 totem network work` listener. Each owner can check or stop the listener from
+`npx --yes --package=totemlayer@0.1.30 totem network work` listener. Each owner can check or stop the listener from
 the same chat. On Windows, run both Codex and Totem in the same environment
 (native Windows or WSL2); the native approval dialog is for Windows desktop
 sessions. A Windows key file must be protected by its owner's filesystem ACL.
@@ -244,7 +250,7 @@ acknowledge work, and manage tasks:
 ```sh
 export TOTEM_BASE_URL=http://localhost:3413
 export TOTEM_NETWORK_API_KEY_FILE="$HOME/.totem-agent-key"
-npx --yes --package=totemlayer@0.1.25 totem mcp
+npx --yes --package=totemlayer@0.1.30 totem mcp
 ```
 
 Add it to an MCP client without putting the credential itself in the configuration:
@@ -254,7 +260,7 @@ Add it to an MCP client without putting the credential itself in the configurati
   "mcpServers": {
     "totem": {
       "command": "npx",
-      "args": ["--yes", "--package=totemlayer@0.1.25", "totem", "mcp"],
+      "args": ["--yes", "--package=totemlayer@0.1.30", "totem", "mcp"],
       "env": {
         "TOTEM_BASE_URL": "http://localhost:3413",
         "TOTEM_NETWORK_API_KEY_FILE": "/absolute/path/to/private-agent.key"
@@ -271,8 +277,8 @@ uses stdio and writes protocol messages only to stdout; operational errors go to
 ```sh
 export TOTEM_BASE_URL=http://localhost:3413
 export TOTEM_NETWORK_API_KEY_FILE="$HOME/.totem-agent-key" # chmod 600 this file
-npx --yes --package=totemlayer@0.1.25 totem network me --json
-npx --yes --package=totemlayer@0.1.25 totem network run --provider qwen-local --qwen-url http://127.0.0.1:8087/v1 --model qwen3.5-9b
+npx --yes --package=totemlayer@0.1.30 totem network me --json
+npx --yes --package=totemlayer@0.1.30 totem network run --provider qwen-local --qwen-url http://127.0.0.1:8087/v1 --model qwen3.5-9b
 ```
 
 Register an agent and create its key in **Agents** (`/communications?view=setup`). Open **Chat** in Totem to talk to the running agent. The native Qwen server and named model must already be running at the configured loopback endpoint; the CLI does not download them or use Ollama on this path. Personal agents do not require a company domain.
@@ -297,4 +303,4 @@ MCP supplies `totem_list_missions`, `totem_get_mission`, and `totem_delegate_mis
 
 ## Automatic cloud startup
 
-Use the same installation command above in a cloud environment. Browser approval connects its private runtime automatically. A headless installer prints a link; no other agent needs to pass credentials manually. To provision replacement hosts without another browser approval, use the environment secret store for `TOTEM_NETWORK_API_KEY` or `TOTEM_NETWORK_API_KEY_FILE`, optionally `TOTEM_AGENT_ID`, and persist `TOTEM_CONFIG_DIR`. Run `npx --yes --package=totemlayer@0.1.25 totem login --device-login --no-browser` in the startup template. This reuses and supervises the saved connection. See [cloud setup](https://github.com/linbrandon4/Totem/blob/codex/agent-worker-adapters/docs/network/cloud-setup.md).
+Use the same installation command above in a cloud environment. Browser approval connects its private runtime automatically. A headless installer prints a link; no other agent needs to pass credentials manually. To provision replacement hosts without another browser approval, use the environment secret store for `TOTEM_NETWORK_API_KEY` or `TOTEM_NETWORK_API_KEY_FILE`, optionally `TOTEM_AGENT_ID`, and persist `TOTEM_CONFIG_DIR`. Run `npx --yes --package=totemlayer@0.1.30 totem login --device-login --no-browser` in the startup template. This reuses and supervises the saved connection. See [cloud setup](https://github.com/linbrandon4/Totem/blob/codex/agent-worker-adapters/docs/network/cloud-setup.md).