grix-connector 3.1.13 → 3.1.14

package/openclaw-plugin/skills/grix-register/SKILL.md

@@ -1,86 +1,86 @@
----
-name: grix-register
-description: Used only during the initial installation phase to complete Grix environment account registration/login and obtain the first provider_type=3 Agent parameters; this skill does not perform any local OpenClaw configuration.
----
-
-# Grix Register
-
-This skill is solely responsible for the cloud preparation during "initial installation": account registration/login + generating the first `provider_type=3` Agent parameters.  
-You (AI) operate fully automatically in the terminal, **without requiring the user to open a browser**. After obtaining the parameters, you must hand off to `grix-admin` for local configuration and runtime convergence through `grix_admin`'s `task` entry.
-
-## Workflow
-
-### 0. Role Boundary (Declare Before Executing)
-
-1. This skill **can only** perform account and cloud Agent parameter preparation.
-2. This skill **cannot** execute `openclaw` commands or modify local `openclaw.json`.
-3. Anything involving local configuration, plugin installation, tool permissions, hot-reload validation, or runtime switch verification must be handed to `grix-admin`.
-
-### 1. Ask for Email and Send Verification Code
-
-1. Ask the user for their email address. **Do not ask the user to register on the website**; clearly state that you will complete it within the conversation.
-2. After obtaining the email, execute the verification code sending command in the terminal:
-   ```bash
-   node scripts/grix_auth.js send-email-code --email "<user's email>" --scene "register"
-   ```
-3. After the command executes successfully, prompt the user to check their inbox for the verification code and ask for it.
-
-### 2. Execute Automatic Registration (Obtain Token)
-
-1. After the user provides the verification code, generate a high-complexity random secure password for the user (recommended: 12-character strong password including uppercase, lowercase, numbers, and special characters).
-2. Using the collected information, execute the registration command:
-   ```bash
-   node scripts/grix_auth.js register --email "<email>" --password "<generated random password>" --email-code "<verification code>"
-   ```
-3. This command returns the user's `access_token` on success. In your reply, securely **inform the user of the generated password** and suggest they save it properly.
-
-Note: If registration indicates the email is already registered:
-1. Only switch to the `node scripts/grix_auth.js login` path when the user explicitly provides their existing password
-2. If the user does not have their existing password, do not guess or pretend recovery is complete; clearly tell the user to provide their existing password first, or go through a standalone password reset flow, then continue this skill
-
-### 3. Create the First Cloud Agent Parameters
-
-After obtaining the `access_token`, ask for the Agent name (use it directly if already available in context), then execute:
-
-```bash
-node scripts/grix_auth.js create-api-agent --access-token "<token>" --agent-name "<agent name>"
-```
-
-This step creates the first `provider_type=3` main API agent (`is_main=true`) through the backend's real API, giving it the full initial scope set. If a same-name `provider_type=3` Agent already exists, the script will automatically rotate the API Key and reuse it.
-
-### 4. Force Handoff to grix-admin via `grix_admin.task`
-
-After step 3 executes successfully, the script returns these key settings:
-- `agent_id`
-- `agent_name`
-- `api_endpoint`
-- `api_key`
-
-Then immediately call `grix_admin`, but **do not** pass these fields directly as `grix_admin`'s typed params. The correct approach is to write them into the `task` text, letting `grix-admin` enter the `bind-local` flow.
-
-Recommended `task` format:
-
-```text
-bind-local
-agent_name=<agent_name>
-agent_id=<agent_id>
-api_endpoint=<api_endpoint>
-api_key=<api_key>
-do_not_create_remote_agent=true
-```
-
-If the script output already includes `handoff.task`, prefer reusing that `task` directly. Before `grix-admin` actually completes, do not describe the local side as already configured or activated.
-
-## Guardrails
-
-1. Do not ask the user to register on the website or manually click pages.
-2. Do not modify any local OpenClaw configuration.
-3. Do not install plugins, change tool permissions, or restart the gateway.
-4. After creating or reusing parameters, must hand off to `grix-admin`.
-5. Do not claim local completion or activation; local completion state is determined by `grix-admin`.
-
-## References
-
-1. [references/api-contract.md](references/api-contract.md)
-2. [references/handoff-contract.md](references/handoff-contract.md)
-3. [scripts/grix_auth.js](scripts/grix_auth.js)
+---
+name: grix-register
+description: Used only during the initial installation phase to complete Grix environment account registration/login and obtain the first provider_type=3 Agent parameters; this skill does not perform any local OpenClaw configuration.
+---
+
+# Grix Register
+
+This skill is solely responsible for the cloud preparation during "initial installation": account registration/login + generating the first `provider_type=3` Agent parameters.  
+You (AI) operate fully automatically in the terminal, **without requiring the user to open a browser**. After obtaining the parameters, you must hand off to `grix-admin` for local configuration and runtime convergence through `grix_admin`'s `task` entry.
+
+## Workflow
+
+### 0. Role Boundary (Declare Before Executing)
+
+1. This skill **can only** perform account and cloud Agent parameter preparation.
+2. This skill **cannot** execute `openclaw` commands or modify local `openclaw.json`.
+3. Anything involving local configuration, plugin installation, tool permissions, hot-reload validation, or runtime switch verification must be handed to `grix-admin`.
+
+### 1. Ask for Email and Send Verification Code
+
+1. Ask the user for their email address. **Do not ask the user to register on the website**; clearly state that you will complete it within the conversation.
+2. After obtaining the email, execute the verification code sending command in the terminal:
+   ```bash
+   node scripts/grix_auth.js send-email-code --email "<user's email>" --scene "register"
+   ```
+3. After the command executes successfully, prompt the user to check their inbox for the verification code and ask for it.
+
+### 2. Execute Automatic Registration (Obtain Token)
+
+1. After the user provides the verification code, generate a high-complexity random secure password for the user (recommended: 12-character strong password including uppercase, lowercase, numbers, and special characters).
+2. Using the collected information, execute the registration command:
+   ```bash
+   node scripts/grix_auth.js register --email "<email>" --password "<generated random password>" --email-code "<verification code>"
+   ```
+3. This command returns the user's `access_token` on success. In your reply, securely **inform the user of the generated password** and suggest they save it properly.
+
+Note: If registration indicates the email is already registered:
+1. Only switch to the `node scripts/grix_auth.js login` path when the user explicitly provides their existing password
+2. If the user does not have their existing password, do not guess or pretend recovery is complete; clearly tell the user to provide their existing password first, or go through a standalone password reset flow, then continue this skill
+
+### 3. Create the First Cloud Agent Parameters
+
+After obtaining the `access_token`, ask for the Agent name (use it directly if already available in context), then execute:
+
+```bash
+node scripts/grix_auth.js create-api-agent --access-token "<token>" --agent-name "<agent name>"
+```
+
+This step creates the first `provider_type=3` main API agent (`is_main=true`) through the backend's real API, giving it the full initial scope set. If a same-name `provider_type=3` Agent already exists, the script will automatically rotate the API Key and reuse it.
+
+### 4. Force Handoff to grix-admin via `grix_admin.task`
+
+After step 3 executes successfully, the script returns these key settings:
+- `agent_id`
+- `agent_name`
+- `api_endpoint`
+- `api_key`
+
+Then immediately call `grix_admin`, but **do not** pass these fields directly as `grix_admin`'s typed params. The correct approach is to write them into the `task` text, letting `grix-admin` enter the `bind-local` flow.
+
+Recommended `task` format:
+
+```text
+bind-local
+agent_name=<agent_name>
+agent_id=<agent_id>
+api_endpoint=<api_endpoint>
+api_key=<api_key>
+do_not_create_remote_agent=true
+```
+
+If the script output already includes `handoff.task`, prefer reusing that `task` directly. Before `grix-admin` actually completes, do not describe the local side as already configured or activated.
+
+## Guardrails
+
+1. Do not ask the user to register on the website or manually click pages.
+2. Do not modify any local OpenClaw configuration.
+3. Do not install plugins, change tool permissions, or restart the gateway.
+4. After creating or reusing parameters, must hand off to `grix-admin`.
+5. Do not claim local completion or activation; local completion state is determined by `grix-admin`.
+
+## References
+
+1. [references/api-contract.md](references/api-contract.md)
+2. [references/handoff-contract.md](references/handoff-contract.md)
+3. [scripts/grix_auth.js](scripts/grix_auth.js)

package/openclaw-plugin/skills/grix-register/references/api-contract.md

@@ -1,76 +1,76 @@
-# API Contract
-
-## Responsibility Boundary
-
-1. `grix-register` is solely responsible for account authentication and cloud `provider_type=3` Agent parameter production.
-2. This skill is not responsible for local OpenClaw configuration.
-3. Local configuration is handled by `grix-admin`.
-
-## Base
-
-1. Default website: `https://grix.dhf.pub/`
-2. Default public Grix API base: `https://grix.dhf.pub/v1`
-3. Local development or private deployment can override the base URL.
-
-## Route Mapping
-
-### Agent bootstrap action
-
-| Action | Method | Route | Auth |
-|---|---|---|---|
-| `create-api-agent` | `POST` | `/agents/create` | `Authorization: Bearer <access_token>` |
-| `list-agents` (internal helper) | `GET` | `/agents/list` | `Authorization: Bearer <access_token>` |
-| `rotate-api-agent-key` (internal helper) | `POST` | `/agents/:id/api/key/rotate` | `Authorization: Bearer <access_token>` |
-
-## Payloads
-
-### `create-api-agent`
-
-```json
-{
-  "agent_name": "grix-main",
-  "provider_type": 3,
-  "is_main": true
-}
-```
-
-`provider_type=3` means Agent API type.  
-The bundled bootstrap flow uses `is_main=true` so the first API agent gets the full initial scope set.
-
-## Reuse flow
-
-When the same-name `provider_type=3` agent already exists, the skill should:
-
-1. read `/agents/list`
-2. find the exact-name API agent
-3. rotate its key through `/agents/:id/api/key/rotate`
-4. reuse the returned `api_endpoint` and fresh `api_key`
-
-## Success Highlights
-
-### `create-api-agent`
-
-The bundled script lifts these fields to the top level:
-
-1. `agent_id`
-2. `agent_name`
-3. `provider_type`
-4. `api_endpoint`
-5. `api_key`
-6. `api_key_hint`
-7. `session_id`
-
-## Common Errors
-
-1. create-agent or rotate-key returns missing `api_endpoint` or `api_key`
-
-## Handoff
-
-After success, do not pass the structured fields directly as `grix_admin`'s typed params; instead assemble them into a `grix_admin.task`:
-
-1. First line: `bind-local`
-2. Then include `agent_id`
-3. `agent_name`
-4. `api_endpoint`
-5. `api_key`
-6. Add a line `do_not_create_remote_agent=true`
+# API Contract
+
+## Responsibility Boundary
+
+1. `grix-register` is solely responsible for account authentication and cloud `provider_type=3` Agent parameter production.
+2. This skill is not responsible for local OpenClaw configuration.
+3. Local configuration is handled by `grix-admin`.
+
+## Base
+
+1. Default website: `https://grix.dhf.pub/`
+2. Default public Grix API base: `https://grix.dhf.pub/v1`
+3. Local development or private deployment can override the base URL.
+
+## Route Mapping
+
+### Agent bootstrap action
+
+| Action | Method | Route | Auth |
+|---|---|---|---|
+| `create-api-agent` | `POST` | `/agents/create` | `Authorization: Bearer <access_token>` |
+| `list-agents` (internal helper) | `GET` | `/agents/list` | `Authorization: Bearer <access_token>` |
+| `rotate-api-agent-key` (internal helper) | `POST` | `/agents/:id/api/key/rotate` | `Authorization: Bearer <access_token>` |
+
+## Payloads
+
+### `create-api-agent`
+
+```json
+{
+  "agent_name": "grix-main",
+  "provider_type": 3,
+  "is_main": true
+}
+```
+
+`provider_type=3` means Agent API type.  
+The bundled bootstrap flow uses `is_main=true` so the first API agent gets the full initial scope set.
+
+## Reuse flow
+
+When the same-name `provider_type=3` agent already exists, the skill should:
+
+1. read `/agents/list`
+2. find the exact-name API agent
+3. rotate its key through `/agents/:id/api/key/rotate`
+4. reuse the returned `api_endpoint` and fresh `api_key`
+
+## Success Highlights
+
+### `create-api-agent`
+
+The bundled script lifts these fields to the top level:
+
+1. `agent_id`
+2. `agent_name`
+3. `provider_type`
+4. `api_endpoint`
+5. `api_key`
+6. `api_key_hint`
+7. `session_id`
+
+## Common Errors
+
+1. create-agent or rotate-key returns missing `api_endpoint` or `api_key`
+
+## Handoff
+
+After success, do not pass the structured fields directly as `grix_admin`'s typed params; instead assemble them into a `grix_admin.task`:
+
+1. First line: `bind-local`
+2. Then include `agent_id`
+3. `agent_name`
+4. `api_endpoint`
+5. `api_key`
+6. Add a line `do_not_create_remote_agent=true`

package/openclaw-plugin/skills/grix-register/references/grix-concepts.md

@@ -1,26 +1,26 @@
-# Grix Concepts
-
-## Canonical Explanation
-
-This plugin integration is for managing OpenClaw through the `https://grix.dhf.pub/` website, with mobile PWA page support.
-
-## Feature Highlights
-
-1. `grix-register` handles initial account preparation and first agent parameter generation
-2. `grix-admin` handles OpenClaw local configuration and subsequent management
-3. After both are chained together, users can use and manage through `https://grix.dhf.pub/`
-
-## Default User-Facing Framing
-
-### One sentence
-
-`grix-register` only does "register an account and obtain the first agent parameters"; local configuration is uniformly handled by `grix-admin`.
-
-### Short paragraph
-
-`grix-register` is only responsible for cloud preparation during initial installation: registering/logging into an account and generating the first `provider_type=3` agent parameters; it must then hand the parameters to `grix-admin`, which is responsible for local OpenClaw configuration.
-
-## After Setup
-
-1. After `grix-register` produces parameters, it hands off directly to `grix-admin`.
-2. `grix-register` does not execute any local configuration actions.
+# Grix Concepts
+
+## Canonical Explanation
+
+This plugin integration is for managing OpenClaw through the `https://grix.dhf.pub/` website, with mobile PWA page support.
+
+## Feature Highlights
+
+1. `grix-register` handles initial account preparation and first agent parameter generation
+2. `grix-admin` handles OpenClaw local configuration and subsequent management
+3. After both are chained together, users can use and manage through `https://grix.dhf.pub/`
+
+## Default User-Facing Framing
+
+### One sentence
+
+`grix-register` only does "register an account and obtain the first agent parameters"; local configuration is uniformly handled by `grix-admin`.
+
+### Short paragraph
+
+`grix-register` is only responsible for cloud preparation during initial installation: registering/logging into an account and generating the first `provider_type=3` agent parameters; it must then hand the parameters to `grix-admin`, which is responsible for local OpenClaw configuration.
+
+## After Setup
+
+1. After `grix-register` produces parameters, it hands off directly to `grix-admin`.
+2. `grix-register` does not execute any local configuration actions.

package/openclaw-plugin/skills/grix-register/references/handoff-contract.md

@@ -1,24 +1,24 @@
-# Handoff Contract to grix-admin
-
-## Purpose
-
-After `grix-register` completes account and first Agent parameter preparation, it uniformly hands local configuration work to `grix-admin`.
-
-## Required `grix_admin` Task
-
-```text
-bind-local
-agent_name=grix-main
-agent_id=2029786829095440384
-api_endpoint=wss://grix.dhf.pub/v1/agent-api/ws?agent_id=2029786829095440384
-api_key=ak_xxx
-do_not_create_remote_agent=true
-```
-
-## Rules
-
-1. The entry is fixed to `grix_admin`'s `task` parameter; do not pass these fields directly as typed params.
-2. The first line must be `bind-local`.
-3. `agent_name`, `agent_id`, `api_endpoint`, `api_key` are required.
-4. `grix-register` is only responsible for generating the above parameters; it does not execute local configuration commands.
-5. Local writing, plugin handling, tool permissions, and hot-reload validation are all handled by `grix-admin`.
+# Handoff Contract to grix-admin
+
+## Purpose
+
+After `grix-register` completes account and first Agent parameter preparation, it uniformly hands local configuration work to `grix-admin`.
+
+## Required `grix_admin` Task
+
+```text
+bind-local
+agent_name=grix-main
+agent_id=2029786829095440384
+api_endpoint=wss://grix.dhf.pub/v1/agent-api/ws?agent_id=2029786829095440384
+api_key=ak_xxx
+do_not_create_remote_agent=true
+```
+
+## Rules
+
+1. The entry is fixed to `grix_admin`'s `task` parameter; do not pass these fields directly as typed params.
+2. The first line must be `bind-local`.
+3. `agent_name`, `agent_id`, `api_endpoint`, `api_key` are required.
+4. `grix-register` is only responsible for generating the above parameters; it does not execute local configuration commands.
+5. Local writing, plugin handling, tool permissions, and hot-reload validation are all handled by `grix-admin`.

package/openclaw-plugin/skills/grix-register/references/openclaw-setup.md

@@ -1,6 +1,6 @@
-# OpenClaw Setup Ownership
-
-`grix-register` is not responsible for OpenClaw local configuration.  
-All OpenClaw configuration-related actions (plugin installation, channel writing, tools permissions, hot-reload validation) belong to `grix-admin`.
-
-This file is retained in this directory solely for responsibility clarification, to prevent misuse.
+# OpenClaw Setup Ownership
+
+`grix-register` is not responsible for OpenClaw local configuration.  
+All OpenClaw configuration-related actions (plugin installation, channel writing, tools permissions, hot-reload validation) belong to `grix-admin`.
+
+This file is retained in this directory solely for responsibility clarification, to prevent misuse.

package/openclaw-plugin/skills/grix-register/references/user-replies.md

@@ -1,25 +1,25 @@
-# User Replies
-
-## One-liner Pitch
-
-I'll first help you complete registration and obtain the first agent parameters, then hand off to `grix-admin` to complete local configuration.
-
-## Short Intro
-
-`grix-register` is only responsible for account and cloud parameter preparation; it does not modify local configuration. Local configuration is handled by `grix-admin`.
-
-## Ready Reply
-
-Account and first agent parameters are ready. Next, I'll hand the parameters to `grix-admin` for local configuration.
-
-## Main Ready, Admin Pending Reply
-
-The `grix-register` phase is complete. I'm now only doing parameter handoff; subsequent local configuration will be continued by `grix-admin`.
-
-## Configured Now Reply
-
-Parameters have been handed off to `grix-admin`; it will complete the local configuration from here.
-
-## Needs Setup Reply
-
-Currently still in the `grix-register` phase. I'll continue completing registration and obtaining the first agent parameters.
+# User Replies
+
+## One-liner Pitch
+
+I'll first help you complete registration and obtain the first agent parameters, then hand off to `grix-admin` to complete local configuration.
+
+## Short Intro
+
+`grix-register` is only responsible for account and cloud parameter preparation; it does not modify local configuration. Local configuration is handled by `grix-admin`.
+
+## Ready Reply
+
+Account and first agent parameters are ready. Next, I'll hand the parameters to `grix-admin` for local configuration.
+
+## Main Ready, Admin Pending Reply
+
+The `grix-register` phase is complete. I'm now only doing parameter handoff; subsequent local configuration will be continued by `grix-admin`.
+
+## Configured Now Reply
+
+Parameters have been handed off to `grix-admin`; it will complete the local configuration from here.
+
+## Needs Setup Reply
+
+Currently still in the `grix-register` phase. I'll continue completing registration and obtaining the first agent parameters.