Omniscio documentation
Browse all documentation
  1. Getting Started13
  2. Sessions & Agents115
  3. Inbox & Notifications59
  4. Projects & Tasks95
  5. Automation & Scheduling75
  6. Knowledge & Memory26
  7. AI Features60
  8. Integrations100
  9. Plugins & Marketplace33
  10. Cloud & Teams56
  11. Settings & Customization58
  12. Account & Billing28
  13. Troubleshooting84
  14. CLI & API Reference22
  15. Legal & Policies4
  16. Uncategorised22

Team Chat hover toolbar extensibility (future plugin/integration hooks)

Status: Planned (no code yet). Depends on a broader plugin/extension framework. The message hover toolbar (TeamChatHoverToolbar.tsx) has a fixed set of actions: Add reaction (emoji picker) Reply in thread Edit (own messages only) Overflow menu (pin, save, copy, quote, delete) These are hardcoded in the component.

What it is

Status: Planned (no code yet). Depends on a broader plugin/extension framework.

Current state

The message hover toolbar (TeamChatHoverToolbar.tsx) has a fixed set of actions:

  • Add reaction (emoji picker)
  • Reply in thread
  • Edit (own messages only)
  • Overflow menu (pin, save, copy, quote, delete)

These are hardcoded in the component. There is no plugin hook or dynamic action registration.

Where to find it

The toolbar itself is the hover bar on a Team Chat message. There is nothing to configure — this page is about the hooks it will offer later.

How it behaves

Future extensibility considerations

When Omniscio's plugin framework matures (the plugin-ui-contributions unreleased feature), the hover toolbar is a natural extension point for custom message actions such as:

  • Create task from message — forward a message's content to Mission Control as a new item
  • Add to knowledge base — save a message to KMS/Nothari for later retrieval
  • Custom integrations — third-party actions (e.g. create a Jira ticket, log to a CRM)
  • AI actions — summarize thread, translate, analyze sentiment

For agents

Architectural notes for future implementation

  • The overflow menu (onOpenMenu) already renders a dynamic list of actions; extending it with plugin-contributed items is the path of least resistance.
  • The plugin-ui-contributions unreleased feature and the PluginContributionPoint pattern (used elsewhere in the app) would provide the registration mechanism.
  • Actions would need: a label, an icon, an onClick(message: ChatMessage) handler, and optionally a visibility predicate (e.g. only show on messages with attachments).
  • Priority: low. The fixed action set covers core chat needs. Extensibility becomes valuable once the plugin ecosystem and third-party integrations are more developed.

Related

Last verified 2026-09-23