Skip to content

Find a Reference

This section is the compact, searchable inventory of Kedi's public language, runtime, Python, adapter, and tooling contracts. The conceptual sections linked from each table provide examples and rationale.

Find the Rule You Need

Question Contract
Is this initialization, assignment, or model output? Outputs and Bindings
Why is a name unavailable outside a branch or loop? Scopes and Binding Lifetime
Does this condition contact a model? Branches and Claims
Does this call return an object or rendered text? Substitutions and Calls
Which model/profile applies here? Profiles and Composition
Which arguments can Python callers configure? Public Parameters
Why was a tool rejected? Approvals and Filesystem Policy
What enters the next model request? History and Artifact Policy

For a sequential introduction, return to Learn Kedi. For a complete composition, use the Cookbook.

Language

Runtime and Integration

  • CLI Reference covers invocation, options, program arguments, and exit behavior.
  • Environment Variables records Kedi-owned and provider-owned configuration.
  • Python API inventories decorators, contexts, promises, runtime helpers, approvals, MCP, and debugging.
  • Capability Matrix distinguishes framework and harness feature support.

Failure and Coverage

The reference describes public behavior. Internal modules not exported from kedi may change without preserving compatibility.

Terminology

  • Template call is the Kedi-level >> operation. It may request structured output fields or discard a raw response when no fields are present.
  • Raw invoke is [name] << prompt, which retains the model's complete text response as a string.
  • Adapter invocation is the runtime call through Kedi's AgentAdapter protocol.
  • Provider request is the outbound model or harness request made by an adapter. One Kedi operation may require multiple provider requests when tools or agent loops are involved.
  • Variable initialization (= after a binding) introduces a value in its owning scope; assignment (:=) updates an existing binding.
  • Validation checks a declared type or result contract. It does not establish factual accuracy, permission to perform an action, or security of embedded Python.