open-index/open-npm huggingface dataset:
npm package: @pingagent/openclaw-channel
Description: Beta OpenClaw channel plugin scaffolding for PingAgent.
Latest version: 0.1.5

# @pingagent/openclaw-channel

Beta OpenClaw channel plugin scaffolding for PingAgent.

This package is intentionally narrow:

- transport only
- direct conversations only
- text inbound / text outbound only
- stable session grammar: `agent:<agentId>:pingagent:direct:<peerId>`
- event id dedupe for replay protection

It does **not** replace the higher-level PingAgent product model. Keep:

- collaboration events
- projection outbox
- Decision Inbox
- Projection Policy
- Human Delivery Bindings
- Notification Intents
- Host Panel / TUI / MCP detail views

The recommended deployment model is:

1. keep `bridge` as the default
2. opt into `channel` only for transport beta testing
3. preserve the existing collaboration session + bound-channel-reply delivery model on top

Important boundary:

- this package is a transport beta, not the human-delivery stack
- it is not part of the default OpenClaw agent-first onboarding path
- bound-channel-reply is built on top of OpenClaw channels that expose explicit outbound target support
- `feishu`, `discord`, `telegram`, `slack`, and `whatsapp` currently have code-path support for explicit send / reply binding, but live delivery still depends on host-side OpenClaw channel configuration and credentials

Local extension staging target:

- `~/.openclaw/extensions/pingagent-openclaw-channel`

Use the installer helpers:

```bash
npx @pingagent/openclaw-install init-runner --channel
npx @pingagent/openclaw-install init-runner --channel --write
```