Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.decisional.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What Dex is

Dex is Decisional’s AI automation engineer. It handles one-off work across your tools and helps you build and manage agents for recurring business workflows. In the app, Dex shows up through the agent chat surfaces. The main agent modes are:
ModeWhat it is for
Chat ModeTalk with an agent conversationally
Operator ModeConfigure instructions, workflow, tools, triggers, skills, runs, node executions, and approvals
Run ModeShare a public run link for an agent that has been made public

Dex and agents

Dex is the conversational operator. Agents are the durable workers that own instructions, workflows, tools, triggers, sources, runs, and approval policy.

​
Use Dex for

  • Asking questions about an agent, its sources, or a run
  • Running one-off work through an agent’s available context and connected tools
  • Explaining what happened during a run
  • Iterating on a workflow in conversation
  • Moving into Operator Mode when the change affects configuration
Dex is useful because you can start in natural language, then keep the agent’s workflow inspectable and controlled through the product surfaces built for configuration, runs, and approvals.

​
Chat Mode

Chat Mode is the conversational surface for an agent. Use it when you want to talk with the agent, ask follow-up questions, or start a one-off task. Configuration is intentionally controlled. If you ask to change integrations or agent configuration from Chat Mode, the app treats those areas as read-only and prompts you to open Operator Mode. Good Chat Mode requests: 
Summarize the last failed run and tell me which step broke.

Use the connected sources to answer this customer question.

Run this request once and show me the output before anything gets sent.

​
Operator Mode

Operator Mode is where you change how an agent works. Use it for setup, debugging, and policy changes. Operator Mode is the right place to manage:
  • Instructions and build context
  • Workflow structure and node configuration
  • Tools, triggers, skills, and sources
  • Runs, logs, failures, and node executions
  • Agent-level approval mode
If a Chat Mode request needs access to read-only configuration or integration controls, open Operator Mode and make the change there.

​
Run Mode

Run Mode is the focused run surface for a public agent link. When an agent is made public, anyone with the link can view and run that agent from /run/{agentId}. Public links are for running or reviewing an agent, not rebuilding it. Public access does not remove policy. Approval mode, tool approval policy, blocked tools, and workflow gates still control what the agent can do.

​
Files, tools, and outputs

Agents can use the context and capabilities you configure for them. Depending on the agent, that can include uploaded documents, spreadsheets, connected apps, triggers, skills, and generated output files. When an action writes, sends, updates, creates, or deletes information, approval policy decides whether the agent can continue automatically, must ask for review, or is blocked.

​
When to switch modes

Need a conversation?

Use Chat Mode.

Need to change the agent?

Use Operator Mode.

Need to share a runnable link?

Use Run Mode after making the agent public.

Dex and Agent Modes

Understand the three agent modes and how Dex fits with agents.

Approvals and Policy

Learn how ask, bypass, and tool policies control agent actions.