@divergeai/cli 0.1.10 → 0.1.13

package/README.md

@@ -57,7 +57,7 @@ the gateway, keeping everything else in the file:
 | `claude` | `~/.claude/settings.json` (or `./.claude/settings.local.json` with `--scope project`): the gateway base URL and `diverge token` as the key helper; `--project-id` adds the project header, `--model-discovery` lets Claude Code list the gateway's models |
 | `opencode` | `~/.config/opencode/opencode.json`: a `divergent-<surface>` provider reading `DIVERGENT_TOKEN` |
 | `codex` | `~/.codex/config.toml`: a `divergent` provider block with `diverge token` as its auth command; `--print` shows it instead |
-| `dsh` | `$DSH_HOME/divergent-<surface>.yml`: a patch overlay with the models the gateway serves, dsh's DeepSeek adapter, telemetry upload and search turned off, and the platform's web search served over `diverge tools bridge` (row `mcp-divergent`) |
+| `dsh` | `$DSH_HOME/divergent-<surface>.yml`: a patch overlay with the models the gateway serves and dsh's DeepSeek adapter, telemetry upload and vendor search turned off; the Divergent agent preset; and your skills in `$DSH_HOME/skills`, through which the agent reaches every platform tool, web search included, from dsh's shell with `diverge tools` |
 
 `diverge agents run dsh` launches DeepSeek Harness on the overlay and keeps
 its token fresh in dsh's own credentials file until it exits. With nothing
@@ -77,27 +77,39 @@ Claude Code and Codex search through their model vendor's own server tool,
 which the gateway forwards unchanged when the organization's upstream is
 Anthropic or OpenAI. Every other model, dsh included, searches through the
 platform's `search_online` tool: one key on the platform, metered and audited
-per organization. The dsh overlay wires it in as `mcp__divergent__search_online`
-(dsh's DeepSeek-backed `web_search` needs a vendor key and is off; `web_fetch`
-stays). dsh's web profile composes the model's tools per agent preset, where a
-patch cannot reach, so `diverge agents setup dsh` and `run dsh` also derive a
-**Divergent** preset from the installed dsh's `standard` one, with the vendor
-search left out of the model's tools, under `$DSH_HOME/.agent-presets/`, and
-make it the default for new web sessions once in `settings.yaml` (a preset you
-pick yourself there stays picked). To give Claude Code or Codex the same tool
-for a non-native upstream, register the bridge once:
+per organization. In dsh the agent reaches it the way it reaches every
+platform tool, from the shell: `diverge tools call search_online`, which the
+installed `diverge` skill names. dsh's DeepSeek-backed `web_search` needs a
+vendor key and is off; `web_fetch` stays. To give Claude Code or Codex the
+same tool for a non-native upstream, the stdio bridge is the opt-in for a
+client that wants it as a native tool:
 
 ```bash
 claude mcp add --scope user divergent -- diverge tools bridge --tools search_online
 ```
 
-```toml
-# ~/.codex/config.toml
-[mcp_servers.divergent]
-command = "diverge"
-args = ["tools", "bridge", "--tools", "search_online"]
+## Skills
+
+A skill is a procedure over the tools it names, in the Agent Skills format
+every harness reads (`<name>/SKILL.md`). The organization authors its skills
+on the platform; you get the ones whose every named tool you can run, plus
+the CLI's own `diverge` skill, which tells an agent how to reach the platform's
+tools from a shell.
+
+```bash
+diverge skills list       # what the platform serves you
+diverge skills install    # into ~/.claude/skills, ~/.codex/skills and $DSH_HOME/skills
+diverge skills status     # what each folder holds against the platform
 ```
 
+`agents setup claude|codex|dsh` and `agents run dsh` install them as well, so
+a harness the CLI set up has the skills from its first session. A refresh
+replaces the CLI's own folders, retires the ones the organization retired, and
+never touches a skill you authored beside them. The skills are the tool
+surface: an agent reaches every platform tool from its shell with `diverge
+tools`, which costs nothing until a tool is called, and the `diverge` skill
+shows it how, file-based arguments and batches included.
+
 ## Platform tools
 
 Every command takes the scope it acts in: `--organization-id` (or
@@ -108,8 +120,16 @@ resource inside a project, `--project-id` (or `DIVERGENT_PROJECT_ID`).
 diverge tools list --filter rbac             # find candidates
 diverge tools describe rbac_assign_role      # one schema, on demand
 diverge tools call rbac_list_roles --args-json '{}'
+diverge tools call inventory_lookup_stock --args-file args.json   # or --args-json - to read stdin
+diverge tools run calls.json --wait          # several calls from one file, one JSON line of outcome each
 ```
 
+Put arguments in a file or on stdin when a shell may touch them: Windows
+PowerShell strips the double quotes inside an inline argument. `run` takes a
+JSON array of `{"tool": "...", "args": {...}}` (or one per line), runs them in
+order, and exits with the worst outcome: 1 failed, 4 rejected, 5 expired,
+3 pending, else 0.
+
 A write that needs a human is not refused: it is persisted as a pending
 invocation, decided in the platform's approval inbox, and read back here by
 id. Branch on the exit code, never on text:
@@ -152,6 +172,11 @@ on the binding when the endpoint is a tailnet or LAN address.
 ## Updating
 
 `diverge update` installs the latest release with the npm that installed it.
+Once a day, after a command finishes, the CLI asks the registry for the latest
+version in the background and caches the answer under `$DIVERGE_HOME`; the
+next command prints one line on stderr when a newer release exists. Nothing
+waits on the network for it, and it stays quiet in the bridge, in
+non-interactive shells, under `CI`, and with `DIVERGE_NO_UPDATE_CHECK=1`.
 
 ## Environment
 
@@ -162,6 +187,7 @@ on the binding when the endpoint is a tailnet or LAN address.
 | `DIVERGENT_ORG_ID`, `DIVERGENT_PROJECT_ID` | tool scope when the flags are omitted; without either, the login's organization |
 | `DIVERGENT_CLIENT_ID`, `DIVERGENT_CLIENT_SECRET`, `DIVERGENT_USER_ID` | unattended tool execution with service credentials, delegated to that person |
 | `DSH_HOME` | where dsh keeps its files, default `~/.dsh` |
+| `DIVERGE_NO_UPDATE_CHECK` | set to skip the once-a-day check for a newer release |
 
 ## Security