Integrations
Plugins
Extend ASUME with plugins that add UI panels, ingest hooks, and workflow actions while keeping the same trace and permission model as the core product.
What plugins do
Plugins let teams customize ASUME without forking core behavior. A plugin can surface extra context on feed cards, enrich ingest, or trigger actions when evidence changes.
Every plugin runs inside workspace permissions. Output still links to traced reasoning so reviewers can audit what changed.
Building plugins
Plugins declare capabilities, required scopes, and the UI surfaces they extend. Use the plugin SDK to register hooks for objectives, feed, and lists.
Keep plugins focused on one workflow. ASUME core handles matching and evidence; plugins add team-specific tooling on top.
- Register UI extensions for feed cards and company panels
- Subscribe to ingest and objective events
- Return structured metadata that reasoning can cite
Install and manage
Workspace admins install plugins from the marketplace or a private registry. Enable or disable plugins per workspace without affecting other tenants.
Review requested scopes before install. Plugins only access data their declared capabilities require.
Plugins vs MCP
Plugins extend the ASUME UI and workspace workflows inside the product. MCP exposes ASUME to external agent hosts with the same traced structures.
Use plugins when your team needs in-product customization. Use MCP when agents outside ASUME should read objectives and return cited evidence.