@osovv/vv-opencode 0.17.2 → 0.17.3

package/README.md

@@ -1,23 +1,22 @@
 # @osovv/vv-opencode
 
-Portable OpenCode workflow package with plugins and a Bun CLI for setup, sync, diagnostics, and explicit memory.
+Portable OpenCode workflow package with a Bun CLI that installs and maintains OpenCode plugins, managed agent prompts, and a canonical `vvoc.json` config.
 
-## What You Get
+## What This Package Does
 
-- `vvoc` CLI for bootstrap, sync, inspection, model overrides, and named presets
-- `GuardianPlugin` for permission review
-- `MemoryPlugin` for explicit persistent memory
-- `SystemContextInjectionPlugin` for reusable primary-session system guidance
-- `SecretsRedactionPlugin` for redacting secrets before LLM requests
-- report-only `memory-reviewer` subagent
-- vvoc-managed prompt files and OpenCode agent registrations
-- managed primary agent `enhancer` for meta-prompting raw intent into structured XML
+- installs one pinned `@osovv/vv-opencode@<version>` entry into OpenCode
+- that package entry exports four plugins: `GuardianPlugin`, `MemoryPlugin`, `SystemContextInjectionPlugin`, `SecretsRedactionPlugin`
+- creates and maintains canonical `vvoc` config at `$XDG_CONFIG_HOME/vvoc/vvoc.json`
+- scaffolds managed prompt files under `vvoc/agents/`
+- registers managed OpenCode agents: `enhancer`, `implementer`, `spec-reviewer`, `code-reviewer`, `investitagor`
+- installs plugin-managed agents: `guardian`, `memory-reviewer`
+- ships model-target presets, diagnostics, and shell completion through the `vvoc` CLI
 
 ## Quick Start
 
-Examples below use `vvoc` directly.
+If the package is installed as a project dependency, run it via `bun x vvoc` or `bun run vvoc`.
 
-Install the package:
+Install globally:
 
 ```bash
 bun add -g @osovv/vv-opencode
@@ -27,137 +26,119 @@ Bootstrap the default global setup:
 
 ```bash
 vvoc install
-```
-
-Inspect the result:
-
-```bash
 vvoc status
 ```
 
-Use project-local scope instead of global scope:
+Write OpenCode config and managed prompts into the current repository instead of the global OpenCode config:
 
 ```bash
 vvoc install --scope project
 ```
 
-`vvoc install` does the following:
-
-- adds a pinned `@osovv/vv-opencode@<installed-version>` entry to the OpenCode `plugin` array
-- registers vvoc-managed OpenCode agents, including the primary `enhancer` agent
-- creates managed prompt files under `vvoc/agents/` when missing
-- creates and fully seeds the canonical `vvoc.json` file at `$XDG_CONFIG_HOME/vvoc/vvoc.json`
-- seeds default `openai` and `zai` agent-model presets inside canonical `vvoc.json`
-- keeps vvoc-managed config in one canonical file separate from native OpenCode config
-- leaves unmanaged files alone unless `--force` is passed
+## What `install` And `sync` Do
 
-For conversational meta-prompting, use the managed `enhancer` primary agent. It can ask follow-up questions and then return a clean XML prompt in English with semantically unique repeated tags such as `<constraint-1>...</constraint-1>` and `<verification-check-2>...</verification-check-2>`.
+`vvoc install` and `vvoc sync`:
 
-Typical workflow:
+- ensure OpenCode has a pinned `@osovv/vv-opencode@<version>` package entry
+- register managed agents and scaffold their prompt files
+- create or refresh canonical `vvoc.json`
+- seed starter presets: `openai`, `zai`, `minimax`
 
-```text
-1. Start a fresh session with the enhancer agent
-2. Paste the rough request in plain language
-3. Answer any short follow-up questions
-4. Copy the final XML prompt into the execution session
-```
-
-The OpenCode config entry written by `install` looks like this:
-
-```json
-{
-  "$schema": "https://opencode.ai/config.json",
-  "plugin": ["@osovv/vv-opencode@<installed-version>"]
-}
-```
+That package entry exports four plugins:
 
-That package entry points at the package root, which exports `GuardianPlugin`, `MemoryPlugin`, `SystemContextInjectionPlugin`, and `SecretsRedactionPlugin`.
+- `GuardianPlugin`
+- `MemoryPlugin`
+- `SystemContextInjectionPlugin`
+- `SecretsRedactionPlugin`
 
-## Common Workflows
+## Config And Data Layout
 
-### Interactive Bootstrap
+OpenCode config stays in OpenCode-managed paths:
 
-Use `init` when you want an interactive setup flow:
+- global: `$XDG_CONFIG_HOME/opencode/opencode.json` or `~/.config/opencode/opencode.json`
+- project: `./opencode.json` or `./opencode.jsonc`
 
-```bash
-vvoc init
-vvoc init --scope project
-```
+vvoc-owned config stays separate from OpenCode config:
 
-Use `--non-interactive` if you want `init` without prompts:
+- canonical config: `$XDG_CONFIG_HOME/vvoc/vvoc.json` or `~/.config/vvoc/vvoc.json`
 
-```bash
-vvoc init --non-interactive --scope project
-```
+Managed prompt files live here:
 
-### Scripted Install
+- global: `$XDG_CONFIG_HOME/vvoc/agents/*.md`
+- project: `./.vvoc/agents/*.md`
 
-`install` is the non-interactive bootstrap command and is the best fit for repeatable setup:
+For CLI commands that accept `--scope project`, only the OpenCode config target and managed prompt directory become project-local. Canonical `vvoc.json` stays global.
 
-```bash
-vvoc install
-vvoc install --scope project
-vvoc install --config-dir /tmp/vvoc-home
-```
+Persisted vvoc data lives here:
 
-When `--config-dir` is used for global scope, `vvoc` writes under the supplied root for both `opencode/` and `vvoc/`.
+- global data root: `$XDG_DATA_HOME/vvoc/` or `~/.local/share/vvoc/`
+- project-local memory: `$XDG_DATA_HOME/vvoc/projects/<project-id>/memory/`
+- shared memory: `$XDG_DATA_HOME/vvoc/memory/shared/<namespace>/`
 
-Regardless of scope, vvoc-owned settings are written to the canonical `vvoc.json` file under the effective XDG config root.
+`vvoc.json` currently contains these top-level sections:
 
-### Sync Managed Files
+- `guardian`
+- `memory`
+- `secretsRedaction`
+- `presets`
 
-Refresh the pinned package entry, managed agent registrations, managed prompt files, and the canonical `vvoc.json` file:
+The current schema is versioned and published with the package:
 
-```bash
-vvoc sync
-vvoc sync --scope project
+```json
+{
+  "$schema": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@<installed-version>/schemas/vvoc/v2.json",
+  "version": 2
+}
 ```
 
-### Inspect And Validate Setup
+Schema source of truth lives in this repository at `schemas/vvoc/v2.json`.
 
-```bash
-vvoc status
-vvoc doctor
-vvoc config validate
-```
+## CLI Overview
 
-- `status` shows the current installation state
-- `doctor` reports parse problems and missing required setup
-- `config validate` validates `$XDG_CONFIG_HOME/vvoc/vvoc.json` against the versioned vvoc JSON Schema
+| Command | Purpose |
+| --- | --- |
+| `vvoc init` | Interactive bootstrap flow |
+| `vvoc install` | Non-interactive setup and scaffolding |
+| `vvoc sync` | Refresh plugin entry, managed agents, prompts, and `vvoc.json` |
+| `vvoc status` | Show current installation state |
+| `vvoc doctor` | Diagnose setup problems and exit non-zero if problems are found |
+| `vvoc config validate` | Validate canonical `vvoc.json` |
+| `vvoc agent list/set/unset` | Manage model target overrides |
+| `vvoc preset list`, `vvoc preset show <name>`, `vvoc preset <name>` | Inspect or apply named presets |
+| `vvoc guardian config` | Print or write the `guardian` section of `vvoc.json` |
+| `vvoc plugin list` | List plugin entries from OpenCode config |
+| `vvoc patch-provider stepfun-ai|zai` | Patch a global OpenCode config preset |
+| `vvoc completion` | Install shell completions |
+| `vvoc upgrade` | Upgrade the global package and run a follow-up sync |
+| `vvoc version` | Print the installed package version |
 
-### Manage Model Targets
+## Model Targets And Presets
 
-List configured model overrides:
+Inspect current model targets:
 
 ```bash
 vvoc agent list
 ```
 
-Set model overrides:
+Set overrides:
 
 ```bash
-vvoc agent set default openai/gpt-5
-vvoc agent set small-model openai/gpt-5-mini
-vvoc agent set general openai/gpt-5-nano
-vvoc agent set explore openai/gpt-5-nano
-vvoc agent set enhancer openai/gpt-5
-vvoc agent set implementer openai/gpt-5
-vvoc agent set code-reviewer anthropic/claude-sonnet-4-20250514
+vvoc agent set default openai/gpt-5.4
+vvoc agent set small-model openai/gpt-5.4-mini
 vvoc agent set guardian anthropic/claude-sonnet-4-5:high
 vvoc agent set memory-reviewer openai/gpt-5:high
+vvoc agent set explore openai/gpt-5.4-mini
 ```
 
 Remove overrides:
 
 ```bash
 vvoc agent unset default
-vvoc agent unset small-model
-vvoc agent unset spec-reviewer
+vvoc agent unset explore
 vvoc agent unset guardian
-vvoc agent unset memory-reviewer
 ```
 
-Supported model target IDs:
+Supported target IDs:
 
 - `default`
 - `small-model`
@@ -171,201 +152,39 @@ Supported model target IDs:
 - `code-reviewer`
 - `investitagor`
 
-`default` writes OpenCode `model`, and `small-model` writes OpenCode `small_model`.
-
-`guardian` and `memory-reviewer` accept `provider/model[:variant]` syntax. The other targets use `provider/model`.
+Model syntax rules:
 
-### Switch Named Presets
+- `guardian` and `memory-reviewer` accept `provider/model[:variant]`
+- all other targets use `provider/model`
+- OpenCode-side targets respect `--scope`
+- `guardian` and `memory-reviewer` live in canonical `vvoc.json`, so they remain global even when `--scope project` is passed
 
-List the presets stored in canonical `vvoc.json`:
+Presets are stored in canonical `vvoc.json` and are useful when you want to switch several model targets together:
 
 ```bash
 vvoc preset list
-```
-
-Show a preset definition:
-
-```bash
 vvoc preset show openai
-```
-
-Apply a preset in one command:
-
-```bash
 vvoc preset openai
 vvoc preset zai --scope project
-vvoc preset minimax
 ```
 
-Preset rules in v1:
+Preset rules:
 
-- presets live only in canonical `vvoc.json`
-- presets manage only model-target overrides in v1
+- starter presets are `openai`, `zai`, and `minimax`
 - presets may be partial
-- `vvoc preset <name>` only changes the targets listed in that preset
-- targets not listed in the selected preset are left untouched
-- `--scope` behaves like `vvoc agent set`: it changes the OpenCode target for OpenCode-managed targets, while canonical `vvoc.json` stays global
-
-This replaces the common workflow of running many `vvoc agent set ...` commands when you want to switch a known group of model targets together.
-
-The canonical config ships with starter `openai`, `zai`, and `minimax` presets and uses this format:
-
-```json
-{
-  "presets": {
-    "openai": {
-      "description": "Starter OpenAI overrides for common vvoc model targets.",
-      "agents": {
-        "default": "openai/gpt-5.4:xhigh",
-        "small-model": "openai/gpt-5.4-mini",
-        "guardian": "openai/gpt-5.4-mini",
-        "explore": "openai/gpt-5.4-mini"
-      }
-    },
-    "zai": {
-      "description": "Starter ZAI overrides for common vvoc model targets.",
-      "agents": {
-        "default": "zai-coding-plan/glm-5.1",
-        "small-model": "zai-coding-plan/glm-4.5-air",
-        "guardian": "zai-coding-plan/glm-4.5-air",
-        "explore": "zai-coding-plan/glm-4.5-air"
-      }
-    },
-    "minimax": {
-      "description": "Starter MiniMax overrides for common vvoc model targets.",
-      "agents": {
-        "default": "minimax-coding-plan/minimax-m2.7",
-        "small-model": "minimax-coding-plan/minimax-m2.1",
-        "guardian": "minimax-coding-plan/minimax-m2.1",
-        "explore": "minimax-coding-plan/minimax-m2.1"
-      }
-    }
-  }
-}
-```
-
-Preset `agents` support the same target IDs as `vvoc agent set`:
-
-- `default`
-- `small-model`
-- `guardian`
-- `memory-reviewer`
-- `general`
-- `explore`
-- `enhancer`
-- `implementer`
-- `spec-reviewer`
-- `code-reviewer`
-- `investitagor`
-
-### Plugin Inspection, Provider Presets, And Shell Completion
-
-```bash
-vvoc plugin list
-vvoc plugin list --verbose
-vvoc path-provider stepfun-ai
-vvoc completion
-```
-
-- `plugin list` shows plugin entries from OpenCode config
-- `path-provider stepfun-ai` patches the global OpenCode provider base URL for StepFun
-- `completion` installs completions for the current shell (`bash`, `zsh`, or `fish`)
-
-### Check For Upgrades
-
-```bash
-vvoc upgrade
-vvoc version
-```
-
-- `vvoc upgrade` checks npm for a newer `@osovv/vv-opencode`, runs `bun add -g @osovv/vv-opencode@<latest>` when one exists, and then runs the default global `vvoc sync` flow.
-- If the package upgrade succeeds but the follow-up sync cannot run, rerun `vvoc sync` manually.
-
-## Command Reference
-
-| Command | Purpose |
-| --- | --- |
-| `vvoc init` | Interactive bootstrap flow |
-| `vvoc install` | Non-interactive setup and scaffolding |
-| `vvoc sync` | Refresh managed config and prompt files |
-| `vvoc status` | Show current installation state |
-| `vvoc doctor` | Diagnose setup problems |
-| `vvoc agent list/set/unset` | Manage model targets and overrides |
-| `vvoc preset <name>/list/show <name>` | Switch or inspect declarative named presets |
-| `vvoc guardian config` | Print or write the `guardian` section of `vvoc.json` |
-| `vvoc config validate` | Validate canonical `vvoc.json` |
-| `vvoc plugin list` | List OpenCode plugins from config |
-| `vvoc path-provider stepfun-ai` | Patch a global provider endpoint preset |
-| `vvoc completion` | Install shell completions |
-| `vvoc upgrade` | Check npm, globally install the latest package with Bun, then run `vvoc sync` |
-| `vvoc version` | Print the installed `vvoc` version |
-
-## Config And Data Layout
-
-OpenCode config stays in OpenCode-managed paths:
-
-- global: `$XDG_CONFIG_HOME/opencode/opencode.json` or `~/.config/opencode/opencode.json`
-- project: `./opencode.json` or `./opencode.jsonc`
-
-vvoc-managed config stays separate from OpenCode config and now has one canonical file:
-
-- canonical config: `$XDG_CONFIG_HOME/vvoc/vvoc.json` or `~/.config/vvoc/vvoc.json`
-
-That canonical config contains the `guardian`, `memory`, `secretsRedaction`, and `presets` sections.
-
-Project scope still uses `./.vvoc/agents/` for managed prompt files, but vvoc's own settings always live in the canonical global config file.
-
-Persisted vvoc data lives under the XDG data root:
-
-- global data root: `$XDG_DATA_HOME/vvoc/` or `~/.local/share/vvoc/`
-- project-local memory: `$XDG_DATA_HOME/vvoc/projects/<project-id>/memory/`
-- shared memory: `$XDG_DATA_HOME/vvoc/memory/shared/<namespace>/`
-
-Managed prompt files live here:
-
-- global: `~/.config/vvoc/agents/*.md`
-- project: `./.vvoc/agents/*.md`
-
-Scope rules:
-
-- vvoc settings are always read from the canonical global `vvoc.json` file
-- project scope only changes the OpenCode config target and the managed prompt directory
-- existing unmanaged prompt files are not rewritten unless `--force` is passed
-
-## JSON Schema
-
-`vvoc.json` includes a versioned `$schema` URL:
-
-```json
-{
-  "$schema": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@<installed-version>/schemas/vvoc/v2.json",
-  "version": 2
-}
-```
-
-Schema source of truth and hosting strategy:
-
-- the current schema is checked into this repository at `schemas/vvoc/v2.json`
-- the legacy schema remains checked in at `schemas/vvoc/v1.json`
-- the package publishes that file to npm by shipping the `schemas/` directory
-- the canonical hosted schema URL is version-pinned: `https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@<installed-version>/schemas/vvoc/v2.json`
-- `v1.json` is immutable once published; breaking schema changes must ship as `v2.json` instead of rewriting `v1.json`
-- existing `version: 1` configs still load during the migration window, and `vvoc install` or `vvoc sync` rewrites them to canonical `version: 2`
+- applying a preset only changes the targets listed in that preset
+- OpenCode-side targets respect `--scope`
+- special targets such as `guardian` and `memory-reviewer` still write to canonical `vvoc.json`
 
 ## Plugins Included
 
 ### GuardianPlugin
 
-`GuardianPlugin` reviews OpenCode permission requests with a constrained Guardian agent and safe deny behavior.
+`GuardianPlugin` reviews OpenCode permission requests with a constrained `guardian` agent and safe deny behavior.
 
-Print or rewrite the `guardian` section of canonical `vvoc.json`:
-
-```bash
-vvoc guardian config --print
-vvoc guardian config --model "anthropic/claude-sonnet-4-5" --variant high
-```
+Runtime settings live in the `guardian` section of canonical `vvoc.json`.
 
-Supported Guardian config fields:
+Supported `guardian` fields:
 
 - `model`
 - `variant`
@@ -373,11 +192,20 @@ Supported Guardian config fields:
 - `approvalRiskThreshold`
 - `reviewToastDurationMs`
 
-The `guardian` section lives under `$XDG_CONFIG_HOME/vvoc/vvoc.json`.
+Print or update the `guardian` section:
+
+```bash
+vvoc guardian config --print
+vvoc guardian config --model "anthropic/claude-sonnet-4-5" --variant high
+```
+
+The runtime prompt is loaded from `guardian.md`, preferring `./.vvoc/agents/guardian.md` over the global `vvoc` agents directory.
 
 ### MemoryPlugin
 
-`MemoryPlugin` adds explicit persistent memory tools to OpenCode.
+`MemoryPlugin` adds explicit persistent memory tools and installs a report-only `memory-reviewer` subagent.
+
+Memory scopes are `session`, `branch`, `project`, and `shared`. Writes default to `project`; `shared` is cross-project, the rest are repository-local.
 
 Available tools:
 
@@ -390,47 +218,38 @@ Available tools:
 
 Memory is explicit-only:
 
-- stored entries are never injected into the prompt automatically
+- stored entries are never injected into prompts automatically
 - the agent must call memory tools directly when durable context is useful
-- settings live in `$XDG_CONFIG_HOME/vvoc/vvoc.json` under the `memory` section
-
-Supported scopes:
+- `memory-reviewer` can read memory but cannot modify it
 
-- `session` for the current session in the current project
-- `branch` for the current git branch in the current project
-- `project` for repository-specific memory
-- `shared` for cross-project memory
-
-The `memory` section supports these fields:
+Supported `memory` fields:
 
 - `enabled`
 - `defaultSearchLimit`
 - `reviewerModel`
 - `reviewerVariant`
 
-The package also installs a bundled reviewer subagent named `memory-reviewer`.
-
 Example:
 
 ```text
 @memory-reviewer review the current memory and suggest keep/update/merge/delete actions
 ```
 
-The reviewer can read memory but cannot modify it.
+The runtime prompt is loaded from `memory-reviewer.md`, preferring `./.vvoc/agents/memory-reviewer.md` over the global `vvoc` agents directory.
 
 ### SystemContextInjectionPlugin
 
-`SystemContextInjectionPlugin` injects reusable system guidance into primary chat sessions without polluting known subagent prompts.
+`SystemContextInjectionPlugin` injects reusable system guidance into primary sessions without polluting known subagent prompts.
 
 The default injected guidance tells the main session to proactively use the `explore` subagent when the task depends on unfamiliar code, unclear scope, or multiple candidate implementation areas.
 
-The plugin currently injects guidance through the `chat.message` hook so it can inspect the resolved agent name and skip known subagents such as `general`, `explore`, `implementer`, and `memory-reviewer`.
-
 ### SecretsRedactionPlugin
 
-`SecretsRedactionPlugin` redacts secrets from chat content before LLM requests and restores placeholders after the request lifecycle where needed.
+`SecretsRedactionPlugin` redacts secrets from chat content before LLM requests and restores placeholders afterward where needed.
+
+Settings live in the `secretsRedaction` section of canonical `vvoc.json`.
 
-`vvoc install` and `vvoc sync` seed the `secretsRedaction` section in canonical `vvoc.json`. The generated config uses:
+The default seeded config uses:
 
 ```json
 {
@@ -440,35 +259,32 @@ The plugin currently injects guidance through the `chat.message` hook so it can
 
 Set `VVOC_SECRET` if you want placeholder restoration to stay stable across restarts.
 
-If no canonical config file exists, the plugin falls back to defaults and generates a random secret for the current runtime.
-
-Built-in patterns cover common identifiers and tokens such as:
+Built-in patterns cover common identifiers and tokens such as email addresses, UUIDs, IP and MAC addresses, bearer tokens, and common OpenAI, Anthropic, GitHub, AWS, and Stripe-style keys.
 
-- email addresses
-- UUIDs
-- IP and MAC addresses
-- OpenAI, Anthropic, GitHub, AWS, and Stripe-style keys
-- bearer tokens and generic hex-like tokens
+## Managed Prompts And Agents
 
-## Managed Prompts And Subagents
-
-`vvoc` manages prompt files for:
+Managed prompt files are created for:
 
 - `guardian`
 - `memory-reviewer`
+- `enhancer`
 - `implementer`
 - `spec-reviewer`
 - `code-reviewer`
 - `investitagor`
 
-`install` and `sync` register these OpenCode subagents in `opencode.json`:
+OpenCode agent registrations written by `vvoc install` and `vvoc sync` are:
 
+- `enhancer`
 - `implementer`
 - `spec-reviewer`
 - `code-reviewer`
 - `investitagor`
 
-`GuardianPlugin` and `MemoryPlugin` load `guardian.md` and `memory-reviewer.md` from vvoc-managed paths at runtime.
+Plugin runtime agents are:
+
+- `guardian`
+- `memory-reviewer`
 
 If a managed prompt file is missing, rerun one of these commands:
 
@@ -477,28 +293,6 @@ vvoc install
 vvoc sync
 ```
 
-## Package API
-
-Root exports:
-
-```ts
-import {
-  GuardianPlugin,
-  MemoryPlugin,
-  SystemContextInjectionPlugin,
-  SecretsRedactionPlugin,
-} from "@osovv/vv-opencode";
-```
-
-Subpath exports:
-
-```ts
-import { GuardianPlugin } from "@osovv/vv-opencode/plugins/guardian";
-import { MemoryPlugin } from "@osovv/vv-opencode/plugins/memory";
-import { SystemContextInjectionPlugin } from "@osovv/vv-opencode/plugins/system-context-injection";
-import { SecretsRedactionPlugin } from "@osovv/vv-opencode/plugins/secrets-redaction";
-```
-
 ## Local Development
 
 Install dependencies:
@@ -507,7 +301,7 @@ Install dependencies:
 bun install
 ```
 
-Run the full local verification stack:
+Run the local verification stack:
 
 ```bash
 bun run typecheck
@@ -524,11 +318,6 @@ Format source files:
 bun run fmt
 ```
 
-Git hooks are managed with `lefthook`.
-
-- `bun install` runs `lefthook install --force` through the `prepare` script
-- the `pre-commit` hook runs `bun run lint` and `bun run fmt:check`
-
 Smoke-test the built CLI against a temporary config root:
 
 ```bash
@@ -538,9 +327,11 @@ bun dist/cli.js install --config-dir "$tmpdir"
 bun dist/cli.js status --config-dir "$tmpdir"
 ```
 
+Git hooks are managed with `lefthook`.
+
 ## Publishing
 
-This package is published manually from the terminal.
+Publishing is manual from the terminal.
 
 Typical release flow:
 
@@ -556,4 +347,4 @@ npm publish
 
 ## Optional: RTK
 
-[RTK](https://github.com/rtk-ai/rtk) is a CLI proxy that reduces token usage for common developer commands. It works well alongside `vvoc`, and the interactive `vvoc init` flow recommends it after setup.
+[RTK](https://github.com/rtk-ai/rtk) is a CLI proxy that can reduce token usage for common developer commands. The interactive `vvoc init` flow recommends it after setup.