@n1creator/openacp-cli 2026.712.9 → 2026.712.11

package/README.md

@@ -227,9 +227,11 @@ not globally intercepted. Credentials live in a separate mode-0600 secret store
 and never appear in route files, agent definitions, status responses, or
 structured OpenACP logs.
 
-Manage routes from any connector with `/proxy`, from the CLI with
-`openacp proxy`, or through `/api/v1/proxy`. Channel changes are tested before
-they are saved. See [Scoped Proxy Routing](docs/gitbook/features/proxy-routing.md).
+In Telegram, open **Settings → Proxy Management** or use `/proxy` directly.
+Both paths render the same connector-neutral proxy home; other adapters can use
+that `/proxy` command model too. CLI and REST automation remain available through
+`openacp proxy` and `/api/v1/proxy`. Channel changes are tested before they are
+saved. See [Scoped Proxy Routing](docs/gitbook/features/proxy-routing.md).
 
 ### Operations
 
@@ -299,11 +301,30 @@ openacp tunnel list
 # Scoped proxy routing (requires running daemon)
 openacp proxy status
 openacp proxy import usa --env-file ~/.openacp/secrets/proxy.env
+openacp proxy create backup --from-json ~/.openacp/secrets/backup-proxy.json
+openacp proxy update backup --from-json ~/.openacp/secrets/backup-proxy.json
 openacp proxy set channels.telegram profile:usa
 openacp proxy set agents.codex profile:usa
 openacp proxy test --scope channels.telegram
 ```
 
+The protected JSON file supports a Quick URL mode: use either separate
+`protocol`, `host`, and `port` fields or one write-only `proxyUrl` such as
+`{"proxyUrl":"socks5h://user:password@proxy.example:1080"}`. The two forms are
+mutually exclusive. A URL must include an explicit port; credentials are parsed
+and stored separately, and the original URL is never persisted or returned.
+
+The connector-neutral `/proxy` interface requires `network:proxy:manage` before
+showing status, profiles, routes, diagnostics, or tests. It provides add/edit,
+candidate test-before-save, credential clearing, paginated route controls, and
+atomic delete-with-reassignment. Telegram deletes credential replies before use;
+if that guarantee is unavailable, OpenACP refuses the value and directs the
+operator to a mode-0600 CLI/API input file.
+
+Use a unique Telegram bot for each OpenACP instance. Command synchronization has
+one heartbeat-backed owner per public bot ID and a second instance will not
+modify the first instance's command menus.
+
 > **Full CLI reference** — [CLI Commands](https://openacp.gitbook.io/docs/api-reference/cli-commands)
 
 ## Documentation