Code Pluginsource linked

EdgeOpsv1.1.0

ClawOps: OpenClaw plugin for EdgeOps — manifest 动态注册扩展工具,服务端管理提示词

@edgeops/claw-ops·runtime claw-ops·by @edgeops
Community code plugin. Review compatibility and verification before install.
openclaw plugins install clawhub:@edgeops/claw-ops
Latest release: v1.1.0Download zip

Capabilities

configSchema
Yes
Executes code
Yes
HTTP routes
0
Runtime ID
claw-ops

Compatibility

Built With Open Claw Version
2026.3.31
Min Gateway Version
2026.3.24-beta.2
Plugin Api Range
>=2026.3.24-beta.2
Plugin Sdk Version
2026.3.31
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The purpose is coherent with EdgeOps operations, and the README/manifest disclose remote HTTP tools, SSH channels, dynamic manifest tools, and host prompt management. The concern is proportionality: fallback and dynamic tools include high-impact actions such as SSH execution, remote file write, and host prompt overwrite.
!
Instruction Scope
The plugin intentionally injects system context to steer agents toward edgeops_* tools and blocks local shell calls to EdgeOps, which is disclosed and purpose-aligned. However, edgeops_invoke and remote manifest registration create an expandable tool surface without a visible local allowlist, signing check, or confirmation gate.
Install Mechanism
The package has ordinary OpenClaw plugin metadata, no postinstall script, and simple pack scripts. Configuration requires an EdgeOps base URL and bearer token; the token field is marked sensitive and docs recommend environment references.
!
Credentials
For a production operations environment, remote SSH, file modification, batch/task inspection, prompt updates, and free-form ops chat are high-impact capabilities. They fit the plugin’s stated purpose, but the package relies on backend authorization and does not show local path scoping, approval prompts, rollback controls, or per-tool risk gates.
!
Persistence & Privilege
The plugin does not create local persistence beyond OpenClaw configuration, but it can change persistent remote host prompts and may load persistent server-provided system prompt/tool definitions from the EdgeOps manifest.
Scan Findings in Context
[SDI-1] expected: The SSH and invoke capabilities are not hidden in the overall artifacts: the README and openclaw.plugin.json enumerate SSH channel tools, edgeops_invoke, and dynamic manifest tools. This downgrades the scanner’s scope-mismatch framing, but the breadth remains a Review concern.
[SDI-1] expected: Fallback extended tools are disclosed in the README as the offline fallback and are listed in the plugin contract. The issue is not secrecy, but that fallback includes powerful state-changing operations.
[SQP-2] expected: Dynamic remote manifest registration and generic invoke are central to the stated design. They remain concerning because the package does not show manifest authenticity checks, a fixed allowlist, or local confirmation for newly exposed tools.
[SQP-2] expected: ops_chat necessarily sends user messages, optional attachment UUIDs, and context to the EdgeOps service. The remote data flow is broadly disclosed, though users should treat it as sending operational content to the configured service.
[SQP-2] expected: edgeops_remote_fs_write is purpose-aligned for operations work but can modify managed hosts; the local tool description is terse and lacks an explicit destructive/action confirmation warning.
[SQP-2] expected: edgeops_update_host_prompt is disclosed and purpose-aligned, but overwriting host prompts can persistently affect future agent behavior and is not paired with visible rollback or approval controls in the package.
What to consider before installing
Install only if you trust the EdgeOps server configured by baseUrl and the operators who control its manifest. Use a least-privilege EdgeOps token, prefer a self-hosted or verified base URL, restrict which agents can use claw-ops, and review dynamic tools before allowing the agent to perform SSH, file-write, or prompt-update actions.

Verification

Tier
source linked
Scope
artifact only
Summary
Validated package structure and linked the release to source metadata.
Commit
fed4884
Tag
fed4884
Provenance
No
Scan status
suspicious

Tags

latest
1.1.0

EdgeOps · OpenClaw 插件(claw-ops)

OpenClaw 网关内连接 EdgeOps,用统一工具完成 主机资产、探活、集成运维对话,无需在聊天里手写 curl / PowerShell 调 EdgeOps API。

npm 包名@edgeops/claw-ops(需在 registry 发布后,方可用于 openclaw plugins install @edgeops/claw-ops@<版本>;未发布时正常现象)
插件 IDclaw-opsopenclaw.jsonplugins.entries.claw-ops
版本:见 package.json / openclaw.plugin.json(与 EdgeOps 产品对齐时可对照仓库 config.pyVERSION)。

安装(不依赖 ClawHub 时推荐)

  • 离线包:仓库内 npm run pack → 将生成的 edgeops-claw-ops-*.tgz 拷到目标机 → openclaw plugins install <tgz 路径>
  • npm:包已 npm publish 后 → openclaw plugins install @edgeops/claw-ops@x.y.zx.y.zpackage.jsonversion 一致;或用 @latesttag,勿写 npm: 前缀、勿用 ^ 范围)。ClawHub 忙/429 时作用域包可能仍先撞 ClawHub,优先用离线 .tgz 或本地目录安装
  • npm 装不上/很慢:可先设 npm_config_registry(如 https://registry.npmmirror.com)再执行 openclaw plugins install …,与常见 npx … --registry=… 同类;不能解决 ClawHub 限流,详见 OPENCLAW_INSTALL.md §3.7
  • ClawHub 慢 / 429:可配置 CLAWHUB_SITECLAWHUB_REGISTRY 指向国内镜像 https://mirror-cn.clawhub.com,详见 OPENCLAW_INSTALL.md(§3.6 · 国内镜像)。
  • 详表与 ClawHub 说明见 OPENCLAW_INSTALL.md §3

功能概览

能力工具名说明
探活 / 版本edgeops_gateway_pingGET /api/version
主机列表edgeops_list_hostsGET /api/hosts(分页)
主机检索edgeops_search_hostsGET /api/hosts/search(别名/标签/remark)
提示词检索主机edgeops_search_hosts_by_promptGET /api/integration/hosts/search-by-prompt
主机详情 / 提示词 / 标签edgeops_get_host / edgeops_get_host_prompt / edgeops_list_host_tags解析 host_id 与约定
探活 / 统计 / 最佳实践edgeops_host_alive / edgeops_host_stats / edgeops_search_best_practices轻量查询
运维对话edgeops_ops_chatPOST /api/integration/ops-chat/complete

SSH 交互通道(无界面 TTY)

能力工具名说明
创建edgeops_ssh_channel_createPOST /api/ssh-channel
列表edgeops_ssh_channel_listGET /api/ssh-channel?all_open=true
详情edgeops_ssh_channel_infoGET /api/ssh-channel/{id}
发送edgeops_ssh_channel_sendPOST …/send
按行读edgeops_ssh_channel_read_linesGET …/lines
按字符读edgeops_ssh_channel_readGET …/read
有新输出edgeops_ssh_channel_has_newGET …/has-new
关闭edgeops_ssh_channel_closeDELETE …/{id}
导出 spilledgeops_ssh_channel_dumpPOST …/dump
批量关edgeops_ssh_channel_close_batchPOST …/close-batch
读 spilledgeops_read_chat_dataGET /api/integration/spill/read

完整 contracts 见 openclaw.plugin.jsonv1.1.0+:22 核心 + manifest 动态扩展 + edgeops_invoke)。

扩展工具(P1/P2,v1.1.0+ manifest 动态注册)

Gateway 启动edgeops_gateway_ping 时拉取 GET /api/integration/claw-ops/manifestextended_tools,对尚未注册项 registerTool;执行仍走 POST …/invoke。EdgeOps 后台在 claw_ops_registry.py 新增工具后,重启 Gateway 即可出现在模型工具列表(无需改插件 fallback)。离线或 manifest 失败时用 manifest-fallback.ts 兜底。

编排式后台 ops(orchestrate)仅 MCP,本插件不提供。

Hermes 用户见 claw-skillsCursor MCPservices/edgeops_mcp(47 工具超集)。


服务端驱动(减少插件发版)

能力EdgeOps API说明
系统提示词GET /api/integration/claw-ops/manifest启动/gateway_ping 拉取,注入 before_prompt_build
扩展工具 schema同上 extended_toolsv1.1.0+ 启动/ping 时 动态 registerTool;执行走 invoke
版本检查GET …/check-update?plugin_version=低于推荐版本时在提示词顶部提醒
通用调用POST …/invokemanifest 尚未同步时的兜底;或显式按名调用

后续在 EdgeOps 侧改 services/claw_ops_registry.py 即可扩展工具/提示词;重启 Gateway 加载新具名工具仅当 invoke 协议、核心工具签名或 OpenClaw registerTool 行为变化时才需发 claw-ops 新版本

所有 HTTP 均在 OpenClaw Gateway / 插件进程 内通过 fetch 完成;Bearer 只来自插件配置 OpenClaw 密钥引用,不应出现在本机 exec 或用户粘贴的命令里。


执行方式(与网页的关系)

  • 不依赖打开 EdgeOps 浏览器界面,也不依赖网页里的 AI 聊天区、Web 终端 DOM。
  • 集成路径对应 EdgeOps 的 session_scope: integration 会话:在服务端完成推理与工具调用,与是否有人开着网页无关。
  • 插件会在 before_prompt_build 注入系统说明,引导模型优先使用 edgeops_*;可选在 before_tool_call 拦截指向已配置 EdgeOps 的 exec 类调用(blockLocalEdgeOpsExec,默认开启)。

配置要点(必须配齐才能工作)

未在 openclaw.json 中正确配置时,edgeops_* 不可用或不会出现在模型工具列表中。

说明
plugins.allow可选。若配置了非空 plugins.allow,则必须"claw-ops" 才会加载本插件;未配置或为空时插件仍可能被自动发现(官方会建议改为显式白名单)。
plugins.entries.claw-opsenabled: truehooks.allowPromptInjection 建议 true
plugins.entries.claw-ops.config.baseUrl可修改;省略时默认 https://ops.pinglan.cc(自建请填实际根地址,无尾斜杠)。
plugins.entries.claw-ops.config.accessToken必填(EdgeOps JWT 或 eop_ Token)。
config.appendOpenClawUiHints / config.blockLocalEdgeOpsExec写在 config 下(不是 hooks);可按需设为 true/false
tools.alsoAllow使用 tools.profile: coding 等精简集时须含 "claw-ops"

完整可合并示例:openclaw.claw-ops.example.json(填入真实 accessToken 后合并进 ~/.openclaw/openclaw.json)。

详细安装、命令行改配置、ClawHub、打包与跨平台说明见 OPENCLAW_INSTALL.md


环境要求

  • Node.js ≥ 22
  • OpenClaw CLI / Gateway 版本满足 package.jsonopenclaw.compatopenclaw.build 要求
  • 可访问的 EdgeOps 实例与有效令牌

开发与仓库

发布至 npm / ClawHub 前请阅读 OPENCLAW_INSTALL.mdOpenClaw Plugin Setup


许可证

MIT-0MIT No Attribution):与常见 MIT 类似,但不要求再分发时附带版权或许可正文。全文见仓库根目录 LICENSEpackage.jsonlicense 字段为 MIT-0