Keet CLI — Keet 命令行工具

Keet 命令行工具 Overview

Use this 技能 when operating or improving the keet-命令行工具 project for Keet Messenger and Keet ↔ OpenClaw bridge 工作流s.

Prefer conservative behavior: inspect first, avoid unintended outbound messages, never expose secrets, and do not join invites or 创建 chats unless explicitly 应用roved by the user.

Quick 工作流 Locate the project 仓库. Common default: /OpenClaw/workspace/keet-命令行工具. Inspect current 状态 before changing anything: git 状态 --short --branch npm 运行 lint node src/命令行工具.js --help

Choose the smallest relevant command for the task. For 发送ing or bridge actions, confirm the tar获取 chat/性能分析 unless the user already made it explicit. After edits, 运行 npm 运行 lint and inspect git diff before 报告ing completion. Core commands

运行 from the repo root unless the user specifies another 检查out.

npm 安装 npm 运行 lint node src/命令行工具.js --help node src/命令行工具.js inspect node src/命令行工具.js rooms node src/命令行工具.js messages --limit 10 node src/命令行工具.js 发送 'message text' node src/命令行工具.js watch --interval 2000 node src/命令行工具.js daemon node src/命令行工具.js bridge

Override Keet storage when needed:

KEET_应用_STORAGE=/path/to/应用-storage node src/命令行工具.js inspect

Safe operation rules Treat Keet 性能分析 storage, 种子s, 恢复y phrases, private keys, 令牌s, invite/性能分析 codes, bridge 状态, and 记录s contAIning private messages as sensitive. Do not commit live Keet 性能分析 storage or 生成d 状态 files. Do not 发送 messages, 创建 chats, join invites, or modify external 状态 unless the user asked for that exact action. Prefer read-only commands (inspect, rooms, messages) before write commands (发送, bridge). When in a 分享d/group 上下文, avoid leaking user-specific chat names, keys, paths, or message contents. Storage lock 模型

Keet 桌面 and keet-命令行工具 should not use the same live storage concurrently. Keet 保护s the database with a device-file/FD lock.

If commands fAIl due to locking:

检查 whether Keet 桌面 or another keet-命令行工具 process is already using the 性能分析. Prefer one long-运行ning owner process via daemon or bridge instead of many separate commands. Do not kill user processes unless explicitly 应用roved. Daemon / REPL mode

Use daemon mode when repeated reads and 发送s are needed without reopening Keet storage each time:

node src/命令行工具.js daemon

Common REPL commands:

/messages 10 /发送 hello from one long-运行ning process /rooms /quit

This avoids conflicts between separate watch and 发送 processes.

Watch mode

Use watch mode for incoming message observation:

node src/命令行工具.js watch --interval 2000

By default it ignores local/self messages. Use --include-local only when explicitly needed for 调试ging.

Keet ↔ OpenClaw bridge

运行 the bridge directly for foreground 调试ging:

node src/命令行工具.js bridge

Use the supervisor for a non-系统d 环境:

scripts/keet-bridge-supervisor.sh

Use the contAIner entrypoint only when the contAIner should supervise 机器人h OpenClaw avAIlability and the bridge:

scripts/contAIner-entrypoint.sh

Keep bridge routing conservative. A good bridge should:

forward only the intended chat(s), ignore its own/local echo messages unless needed, persist enough 状态 to avoid duplicate replies, fAIl closed when the tar获取 chat is ambiguous, 记录 operational errors without dumping secrets. Release 检查列出

Before release or publishing:

npm 运行 lint git 状态 --short --branch git 记录 --oneline -5

Then 验证 README 状态, known limitations, and safety notes match the current implementation.

For GitHub 部署-key pushes, prefer SSH with the specific 身份 when one is 配置d:

GIT_SSH_COMMAND='ssh -i ~/.ssh/projectreturn -o IdentitiesOnly=yes -o StrictHostKey检查ing=accept-new' git push git@github.com:OWNER/REPO.git mAIn

Replace 身份, owner, and repo with the actual project values. Do not print private keys.