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.

​
Dex and agents

Decisional has two top-level concepts:
  • Dex is the conversational operator for your workspace. Use Dex to ask questions, build agents, change existing agents, run one-off work, and monitor what is happening.
  • Agents are durable AI workers. Each agent owns instructions, a workflow, tools, sources, triggers, runs, and approval policy for a repeatable business process.
Dex is how you steer the system. Agents are the operating units that run the work.

​
How they work together

Dex can help you create a new agent, update an existing agent, or complete a task through conversation. When the work should happen repeatedly, Dex helps turn that intent into an agent with a workflow and operating policy. Once the agent exists, you can keep using Dex to ask what happened, inspect a run, change instructions, or route the agent into the right operating mode.

​
Agent operating modes

An agent can be used in different modes depending on who is using it and what they need to do.
ModeUse it forWho should use it
Chat ModeAsk questions, run one-off tasks, inspect context, and iterate conversationallyAnyone collaborating with the agent
Operator ModeConfigure instructions, workflow, tools, triggers, skills, sources, runs, and approval behaviorOwners and builders of the agent
Run ModeShare a public link where people can view and run a public agentExternal stakeholders or internal users who do not need the builder surface

​
Chat Mode

Chat Mode is the everyday conversational surface for an agent. It is best when you want to ask the agent to explain a result, process a small request, answer questions over its sources, or continue an existing thread. Chat Mode keeps configuration changes controlled. If a request requires editing integrations, workflow structure, triggers, or other operator-level settings, the agent will route you to Operator Mode.

​
Operator Mode

Operator Mode is the builder and control room for an agent. Use it when you need to change how the agent works, not just ask it to do work. Operator Mode includes:
  • Agent instructions and build context
  • Workflow viewer and node configuration
  • Connected tools and credentials
  • Triggers and schedules
  • Skills and sources
  • Runs, logs, failures, and pending reviews
  • Agent-level approval settings
Use Operator Mode for setup, debugging, and policy changes.

​
Run Mode

Run Mode is the shareable run experience for an agent. When an agent is made public, anyone with the link can view and run that agent from the focused public surface. Run Mode is useful for:
  • Intake workflows
  • Customer-facing request flows
  • Vendor or partner review
  • Internal forms where most users should not edit the agent
  • Approval pages where a stakeholder only needs the context and decision controls
Public access does not remove the agent’s approval policy. Tool policies, approval requirements, and blocked actions still apply.

​
Choosing a mode

Need an answer?

Use Chat Mode.

Need to change behavior?

Use Operator Mode.

Need to share a run?

Use Run Mode after making the agent public.

Approvals and Policy

Learn how approval modes, bypass approvals, and global policy work.

Working with Agents

Build and manage agents end to end.