Go to file

hzhang 76a3bfbedb feat(inbound): emit media in notification instead of appending footer

Channel plugins now have a structured way to propagate attachments —
Plexum's host turns each MediaItem into a canonical.ImageBlock content
on the user message. This replaces the F-6 workaround that crammed
local file paths into a markdown footer at the end of the message
text.

internal/inbound/inbound.go:
- Notifier signature gains `media []MediaItem`; MediaItem mirrors
  the host's channel.MediaRef (Path/MediaType/Name)
- dispatch downloads attachments (unchanged) then forwards results
  as MediaItem to Notify — no more footer appending
- dispatch now also receives guildEndpoint so it can resolve Fabric's
  RELATIVE attachment URLs (`/api/files/<id>`) against the guild base.
  Previously the downloader received the relative path verbatim and
  failed every fetch silently.

cmd/plexum-fabric-channel-plugin/main.go:
- notifier closure pushes media[] in the EmitNotification payload

Live verified: alice uploads blue 32x32 PNG → Fabric guild → plugin
downloads to /tmp/plexum-fabric/<msg>/blue32.png → emits inbound with
media → host routes to kimi agent → Kimi: "Blue".

(MiniMax M2.7 is text-only per openclaw model definitions, so the
same flow against MiniMax returns "I don't see an image" — that's a
model capability limit, not a plugin issue.)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-31 21:03:24 +01:00

cmd

feat(inbound): emit media in notification instead of appending footer

2026-05-31 21:03:24 +01:00

internal

feat(inbound): emit media in notification instead of appending footer

2026-05-31 21:03:24 +01:00

scripts

feat: Phase F-5+F-7 — command-sync + sub-discussion + channel-create tools

2026-05-31 15:40:09 +01:00

go.mod

feat: Phase F-2 — socket.io inbound + wakeup gate + token refresh

2026-05-31 15:29:01 +01:00

README.md

feat: Phase F-6 — attachments + final docs (F-8 = no-op)

2026-05-31 15:42:23 +01:00

README.md

Plexum-fabric-channel-plugin

Native Plexum channel plugin connecting Plexum agents to Fabric guilds as real channel members. Port of Fabric.OpenclawPlugin — delivered in phases.

Status

Phase	Scope	Status
F-1	identity + REST + plugin scaffold + `send` outbound	✅
F-2	socket.io inbound + wakeup gate + token refresh + per-channel serial	✅
F-3	exponential reconnect backoff	✅
F-4	tool surface batch 1 (8 tools)	✅
F-5	command-sync (slash autocomplete)	✅
F-6	attachments → temp-dir + footer	✅
F-7	sub-discussion KV + create-*-channel + discussion-complete	✅
F-8	coalesce parity	⏭ no-op — Plexum doesn't segment deliver
F-5b	presence-sync	⏭ deferred — Plexum state machine ≠ HF semantics

Agent-facing tools (16)

send — host-driven channel outbound (channel manager → plugin)
fabric-send-message, fabric-send-sys-msg — post normal / system msgs
fabric-channel-list, fabric-guild-list — discovery
fabric-message-history — paginate by seq
fabric-channel, fabric-channel-set-purpose — channel metadata
fabric-canvas — get/share/update/remove canvas
create-{chat,work,report,discussion}-channel — create new channels
discussion-complete — summary + close
create-sub-discussion, close-sub-discussion — sub-discussion lifecycle

Install

cd ~/Plexum-fabric-channel-plugin
./scripts/install.sh                  # build + install plugin + register CLI

Then:

Mint a Center API key for each Plexum agent that should speak in Fabric:

docker exec fabric-backend-center node dist/cli.js user apikey --email <agent-email>

Register the key with Plexum:

plexum-fabric-register --agent-id alice --api-key fak_xxxx
# writes ~/.plexum/fabric-identity.json

Configure plugin-level settings at ~/.plexum/plugins/plexum-fabric-channel/config.json:
```
{
  "center_api_base": "http://localhost:7001/api"
}
```

Bind a Plexum channel name to a Fabric channel at ~/.plexum/channels/<plexum-channel-name>.json:

{
  "agent_id": "alice",
  "plugin": "plexum-fabric-channel",
  "fabric": {
    "guild_node_id": "test-guild1",
    "channel_id": "ch_xxxxxxxxx"
  }
}

Allow the plugin in ~/.plexum/plexum.json:

{"plugins": {"allow": ["plexum-fabric-channel"]}}

Restart the gateway: systemctl --user restart plexum

What you get in F-1

Plugin loads at gateway start, validates every bound agent's API key against Center via agentLogin, and warms a session per agent.
send MCP tool posts plain text to the bound Fabric channel as the agent user.
No inbound yet — Fabric → Plexum routing arrives in F-2.

Build manually

go build -o bin/plexum-fabric-channel-plugin ./cmd/plexum-fabric-channel-plugin
go build -o bin/plexum-fabric-register      ./cmd/plexum-fabric-register

License

Same as Plexum.