[Feature]: 做成插件或者hooks不是更好吗大佬

[7568168]

Summary

00

Problem to solve

00

Proposed solution

00

Alternatives considered

No response

Impact

00

Evidence/examples

No response

Additional information

No response

[Kelisi808]

Kelisi here. Great question. A plugin or hooks path can be cleaner if you want maintainable extension points and smaller core diffs. A pragmatic path is to start with a minimal hook lifecycle (before_send, after_send, on_error) and strict timeout budgets so hooks cannot block the core loop. Question: would maintainers prefer a built-in hook runner or an external plugin process boundary first?

[ariesljm]

做出docker部署，让其它ai应用都能使用不是更好吗

[Kelisi808]

这个建议很好，Docker/插件化确实能让更多 AI 应用复用。给一个可落地的最小方案：

1. 先做 Docker 镜像（固定运行时）
2. 再做 hooks 插件层（可扩展）

最小 docker-compose 示例：

services:
  openclaw-zero-token:
    image: your-image:latest
    ports:
      - "18789:18789"
    environment:
      - NODE_ENV=production
      - OPENCLAW_PORT=18789
    volumes:
      - ./data:/app/data
    restart: unless-stopped

插件接口建议先只放3个点：

• before_send
• after_send
• on_error

这样先保证稳定，再逐步扩展。
如果你愿意，我可以下一条直接给你一个 hooks 接口定义草案（TypeScript 版）。

[linuxhsj]

感谢你的建议！插件化和 hooks 的讨论可以加入 Discord 的 OpenClaw 社区继续进行，那里有更活跃的讨论和社区支持。

[linuxhsj]

感谢建议！插件化讨论建议加入 Discord 的 OpenClaw 社区：https://discord.gg/openclaw