Motivation
Buzz channels already support agents, workflows, Canvases, threads, and signed event history. However, integrations that coordinate multi-step work have no native place to show a concise, current state summary.
Users currently have to reconstruct state from verbose messages, Activity/Pulse, workflow history, and separate Canvases. This is difficult when:
- several agents contribute to one outcome;
- a channel has a provider pool or delegated work;
- evidence and validation arrive at different times;
- a human decision is required; or
- the integration needs to remain auditable without taking over the channel.
For example, an exchange integration needs to show the provider pool, current outcome, match, evidence, buyer decision, and settlement status in one place.
Proposed solution
Add a native, channel-scoped panel surface that renders a signed, permission-aware projection of integration state.
The first slice could provide:
- one panel slot in the channel UI;
- a versioned signed manifest or event-backed view model;
- explicit community and channel scoping;
- structured sections, status badges, timestamps, and links;
- read-only rendering initially;
- deep links to the source Canvas, workflow run, job handoff, or thread;
- loading, empty, error, and unavailable states; and
- API/CLI parity where appropriate.
The panel would be a projection of signed Buzz events, not a second source of truth.
Buzz would own:
- panel placement and rendering;
- channel and community permissions;
- event provenance; and
- the fallback experience.
The integration would own:
- domain semantics;
- matching or workflow policy;
- acceptance authority;
- accounting and settlement; and
- external credentials.
Alternatives considered
Use a Canvas only
Canvases are an excellent fallback and remain the canonical editable document surface, but they are not always discoverable or compact enough for live operational state.
Post ordinary status messages
This works today but creates verbose timelines, repeated updates, and poor at-a-glance visibility.
Use Activity/Pulse
Activity is useful for notifications but is not a channel-owned operational view and can separate the result from the conversation that caused it.
Build a separate dashboard
A separate dashboard duplicates presentation, weakens the native Buzz experience, and makes the signed channel record harder to follow.
Add integration-specific UI
This would create bespoke product surfaces and make the desktop client harder to evolve. A small general panel contract is preferable.
Additional context
No exact open issue or PR was found for a general signed channel extension-panel surface.
Related work:
A concrete motivating integration is OEXL, an exchange layer for agentic outcomes. Its panel would show provider availability, an outcome contract, match state, deliverable/evidence state, buyer decision, disputes, and settlement status. OEXL would remain responsible for all exchange semantics; Buzz would provide the signed, channel-native presentation layer.
The initial implementation should be read-only and should not introduce payment, marketplace, or arbitrary plugin execution semantics.
Motivation
Buzz channels already support agents, workflows, Canvases, threads, and signed event history. However, integrations that coordinate multi-step work have no native place to show a concise, current state summary.
Users currently have to reconstruct state from verbose messages, Activity/Pulse, workflow history, and separate Canvases. This is difficult when:
For example, an exchange integration needs to show the provider pool, current outcome, match, evidence, buyer decision, and settlement status in one place.
Proposed solution
Add a native, channel-scoped panel surface that renders a signed, permission-aware projection of integration state.
The first slice could provide:
The panel would be a projection of signed Buzz events, not a second source of truth.
Buzz would own:
The integration would own:
Alternatives considered
Use a Canvas only
Canvases are an excellent fallback and remain the canonical editable document surface, but they are not always discoverable or compact enough for live operational state.
Post ordinary status messages
This works today but creates verbose timelines, repeated updates, and poor at-a-glance visibility.
Use Activity/Pulse
Activity is useful for notifications but is not a channel-owned operational view and can separate the result from the conversation that caused it.
Build a separate dashboard
A separate dashboard duplicates presentation, weakens the native Buzz experience, and makes the signed channel record harder to follow.
Add integration-specific UI
This would create bespoke product surfaces and make the desktop client harder to evolve. A small general panel contract is preferable.
Additional context
No exact open issue or PR was found for a general signed channel extension-panel surface.
Related work:
A concrete motivating integration is OEXL, an exchange layer for agentic outcomes. Its panel would show provider availability, an outcome contract, match state, deliverable/evidence state, buyer decision, disputes, and settlement status. OEXL would remain responsible for all exchange semantics; Buzz would provide the signed, channel-native presentation layer.
The initial implementation should be read-only and should not introduce payment, marketplace, or arbitrary plugin execution semantics.