This guide is the quick inventory of built-in Jido.AI.Actions.* modules and what each one is for.

Production Baseline (Standalone Surface)

For direct app integration (Jido.Exec-driven), this is the primary standalone action surface:

  1. Core generation:
  2. Tool orchestration:
  3. Planning templates:
  4. Retrieval memory operations:
  5. Quota operations:
  6. Reasoning templates (optional):
  7. Dedicated strategy orchestration:
  8. Compatibility convenience:

LLM Actions

Tool Calling Actions

Planning Actions

Retrieval Actions

Quota Actions

  • Jido.AI.Actions.Quota.GetStatus
    • Use when you need the current rolling quota snapshot for one scope.
    • Required params: none. Optional params: scope.
    • Scope resolution when scope is omitted: context[:plugin_state][:quota][:scope] -> context[:state][:quota][:scope] -> context[:agent][:id] -> "default".
    • Output contract: %{quota: %{scope, window_ms, usage, limits, remaining, over_budget?}}.
    • Runnable example: examples/scripts/demo/actions_quota_runtime_demo.exs
  • Jido.AI.Actions.Quota.Reset
    • Use when you need to clear rolling quota counters for one scope.
    • Required params: none. Optional params: scope.
    • Scope resolution when scope is omitted: context[:plugin_state][:quota][:scope] -> context[:state][:quota][:scope] -> context[:agent][:id] -> "default".
    • Output contract: %{quota: %{scope, reset}}.
    • Runnable example: examples/scripts/demo/actions_quota_runtime_demo.exs

Reasoning Actions

Shared Helpers

Not Standalone: Strategy Internals

Reasoning strategy command atoms and lifecycle/event handlers are intentionally not standalone actions:

  • :cod_start, :ai_react_start, :cot_start, :aot_start, :tot_start, :got_start, :trm_start, :adaptive_start
  • *_llm_result, *_llm_partial, request error lifecycle handlers, worker event handlers

These belong to strategy orchestration and are not app-level AI primitives.

Selection Heuristic

  • Need chat/completion/embed/object output: use LLM actions.
  • Need model-directed tool use: use Tool Calling actions.
  • Need structured planning templates: use Planning actions.
  • Need in-process memory upsert/recall/clear primitives: use Retrieval actions.
  • Need rolling quota status or a quota counter reset operation: use Quota actions.
  • Need explicit reasoning strategy execution as a callable capability: use RunStrategy.

Failure Mode: Action Used Outside Expected Context

Symptom:

  • runtime errors due to missing tool context or model/provider config

Fix:

  • pass required context explicitly
  • verify model/provider config and tool maps before execution
  • for plugin-routed calls, ensure plugin state keys match mounted capability

Next