Skip to main content
Plugin Apps are business-oriented plugins that run inside the UOSE system. They are not a single tool or prompt. A Plugin App is an installable, permissioned, configurable, and reviewable bundle of business capabilities, typically including Workbench views, Assistant tools, business Assistant templates, configuration, permission declarations, and an auditable data loop. The UOSE App marketplace showcases official Apps, partner Apps, and community Apps. Users can discover Apps by business domain, administrators can enable Apps according to organization permissions, and developers can package industry workflows as reusable business Apps through the Xpert plugin system.

What A Plugin App Usually Includes

Common Business Domains

Plugin Apps are grouped by business domain. Common domains include: Currently listed Plugin Apps include:

How To Choose A Plugin App

When choosing a Plugin App, check whether:
  • The App matches the target business domain and real workflow.
  • It provides Workbench views for human review and operations.
  • Assistant tools have clear call order, input structure, and evidence requirements.
  • Permission boundaries separate normal use, write operations, and administrator capabilities.
  • It can reuse UOSE Knowledgebase, ontology resources, audit, and organization permissions.
  • It has official or partner maintenance guidance for upgrades and troubleshooting.

How To Develop A Plugin App

To develop a UOSE Plugin App, use the AI product plugin development system instead of scattering business logic across prompts or temporary scripts. Recommended references: A UOSE business App usually needs to:
  1. Define plugin metadata, icon, target products, and marketplace content.
  2. Declare targetApps: ['data-xpert'] and targetAppMeta to describe views, tools, business App capabilities, templates, and permissions.
  3. Register a server module with entities, services, Agent middleware, and a Workbench view provider.
  4. Split core business actions into explicit, retryable, and auditable Assistant tools.
  5. Provide Workbench views or Remote Components for workflows that need human review.
  6. Contribute business Assistant templates so users can create a usable Assistant in one step.
  7. Configure permissions, defaults, publishing, and upgrade guidance.
Design the App as one loop between Agent automation and human review: the Agent extracts, reasons, retrieves, and executes; Workbench lets users inspect, confirm, correct, write back, and audit. This turns a Plugin App into an operable business system capability rather than a one-off automation script.