For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
ReferenceGuides
ReferenceGuides
  • Agent Studio
    • Overview
    • Quickstart Guides
    • Core Concepts
      • Assistants, Agents, & Plugins
      • Agentic Automation Engine
      • Conversational Plugins
        • Natural Language Triggers
        • Designing Conversation Processes
        • Steering Conversational Plugins
      • Ambient Agents
      • Data Types
      • Citations
      • Data Bank
      • Structured Data Analysis
    • Conversation Process
    • Actions
    • Connectors
    • System Triggers
    • Agent Architect
    • Cookbooks
    • Development and Testing
    • AI Agent Marketplace
    • Developer Tools
  • Agentic AI
    • LLM Fundamentals
    • The Agentic Reasoning Engine
    • Memory Constructs
    • Conversational Context
    • Guardrails
    • Grounding and Hallucinations
    • Continuous Learning
    • LLMs & SLMs
    • Steerability Tools
    • Multilingual Support
  • Core Platform
    • User Identity
    • Moveworks Agent (On-Prem)
    • Approvals Engine
    • Entity Catalog
    • Moveworks Data Objects
    • Security Information and Event Management (SIEM) Logs Overview
DeveloperAcademyCommunityStatus
Agent StudioCore ConceptsConversational Plugins

Steering Conversational Plugins

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Ambient Agents

Next
Built with

The Agentic Reasoning Engine understands how to use your plugins without the need for any prompt engineering. However, your organization may still want to customize that treatment for special situations. For example:

  • The reasoning engine assumes the start_date of any sick leave should be today, but in your organization, sick leaves are submitted retroactively with a doctor’s note.
  • The reasoning engine assumes the country_code should be set based on the current user’s profile, but you want it to ask.
  • After the reasoning engine executes a plugin, you want to promote specific related plugins (e.g. present a Book timeoff plugin after user views their Timeoff balance plugin)

Adding instructions to your plugin makes it possible for the Agentic Reasoning Engine to understand & achieve your desired behavior.

  • Triggering instructions
  • Slot instructions
  • Progress update instructions
  • Response instructions

Don’t worry, these instructions won’t compromise your AI agent’s guardrails & safety protections or attack other plugins. Our reasoning engine treats them as Tool Outputs, which can’t break your AI agent.


If you want to strictly enforce plugin behaviors, consider using policies or managing other logic in the Action Orchestrator