Files

zhi a3a1081f22 feat: add /ego-mgr slash command and rename pcexec to pc-exec

Changes:
1. Add /ego-mgr slash command with subcommands:
   - get, set, list, delete, add-column, add-public-column, show
   - Uses pcExec to call ego-mgr binary with proper env vars

2. Rename pcexec → pc-exec throughout codebase:
   - Tool name: pcexec → pc-exec
   - Function exports: pcexec → pcExec, pcexecSync → pcExecSync
   - Updated all references in skills and plugin files

3. Translate all Chinese text to English:
   - ego-mgr-slash.ts responses
   - slash-commands.ts responses
   - SKILL.md files remain in English

2026-03-24 10:43:13 +00:00

2.6 KiB

Raw Blame History

name, description

name	description
secret-mgr	Manage OpenClaw agent credentials (usernames/secrets). Use when storing, retrieving, listing, generating, or removing credentials for an agent. Trigger on requests about saving or fetching usernames, passwords, tokens, API keys, or other secrets. MUST call secret-mgr via the pc-exec tool.

Secret Manager

Purpose

Use secret-mgr to store and retrieve agent-scoped credentials (username/secret pairs) and generate secrets.

Mandatory safety rule

Always invoke secret-mgr through the pc-exec tool. Do NOT run secret-mgr directly.

Commands (run via pc-exec)

List keys for current agent
- secret-mgr list
- Include shared scope: secret-mgr list --public
Get username for a key
- secret-mgr get-username --key <key>
- Shared scope: secret-mgr get-username --public --key <key>
Get secret for a key
- secret-mgr get-secret --key <key>
- Shared scope: secret-mgr get-secret --public --key <key>
Set a key entry (username optional)
- secret-mgr set --key <key> --secret <secret> [--username <username>]
- Shared scope: secret-mgr set --public --key <key> --secret <secret> [--username <username>]
Remove a key entry
- secret-mgr unset --key <key>
- Shared scope: secret-mgr unset --public --key <key>
Generate a random secret for a key (prints secret)
- secret-mgr generate --key <key> [--username <username>]
- Shared scope: secret-mgr generate --public --key <key> [--username <username>]
Legacy (hidden) getter
- secret-mgr get <key>

Usage notes

Treat all outputs as sensitive. Never echo secrets.
When the agent needs credentials to access a resource, first try list to see if a matching key already exists before asking the user.
Prefer generate when the user wants a new secret or password.
Use set to store both username and secret in one step.
Use get-username and get-secret for retrieval.
Storing can be explicit (user asks) or proactive after the agent successfully registers/creates an account.
Secrets should be fetched and used immediately in a command, not displayed (e.g., xxx_cli login --user $(secret-mgr get-username --key some_key) --pass $(secret-mgr get-secret --key some_key)).

Examples (pc-exec)

Store credentials
- pc-exec: secret-mgr set --key github --username alice --secret <secret>
Retrieve username
- pc-exec: secret-mgr get-username --key github
Retrieve secret
- pc-exec: secret-mgr get-secret --key github
Generate secret
- pc-exec: secret-mgr generate --key github
Delete entry
- pc-exec: secret-mgr unset --key github

2.6 KiB Raw Blame History