LiteAgents 0.3.0a2: exact gateway model aliases

LiteAgents 0.3.0a2 lets you use your gateway's model alias directly. Set the endpoint, key, and exact model name, then change the harness without changing the model connection.

from liteagents import ProfileOptions

profile = ProfileOptions(
    harness="deepagents",
    model="my-model",
    model_kwargs={
        "api_base": "https://your-gateway.example/v1",
        "api_key": "your-gateway-key",
    },
)

Aliases containing slashes are sent unchanged. Existing litellm_proxy/alias configurations continue to work. Without a gateway endpoint, use a LiteLLM provider/model name and provider credentials. Both paths go through LiteLLM.

Custom native provider endpoints: if you previously supplied api_base to override a provider's native API endpoint, add custom_llm_provider to model_kwargs, for example "anthropic" or "openai". Without this override, an endpoint-configured name such as anthropic/foo is now the literal gateway alias. Gateway users need no additional setting. See the migration guide.

Install with Python 3.11+ (3.12 recommended):

python -m pip install \
  'liteagents[deepagents] @ https://github.com/BerriAI/liteagents/releases/download/v0.3.0a2/liteagents-0.3.0a2-py3-none-any.whl' \
  -c https://github.com/BerriAI/liteagents/releases/download/v0.3.0a2/constraints-tested.txt

Install only the harnesses you use, or replace [deepagents] with [all] to compare them. OpenCode also requires npm install -g opencode-ai@1.18.29. A simple agent needs neither Temporal nor PostgreSQL. Use this GitHub package; the PyPI project named liteagents is a different package.

The README, JSON/YAML profiles, and cookbooks now use plain gateway aliases. Getting started · Profiles · Cookbooks

Local regression: 286 passed, 8 environment-dependent skips, and 23 opt-in live-provider cases deselected. Validation includes 60 cross-harness tests using real installed runtimes with a deterministic local model endpoint: direct/Temporal execution, tools, MCP, conversations, and tool-free runs. HTTP tests verify plain and slash-containing aliases, streaming, legacy prefixes, and explicit native-provider endpoints. Wheel/source builds, installed-wheel smoke checks, lint, types, and source-size checks pass. These checks do not claim new live-provider acceptance coverage. All seven CI jobs passed, including the Python/MCP matrix, native runtimes, Temporal, PostgreSQL, and deployment worker image build. See PR #11 for CI results.

Upgrade clients and workers together. Complete existing durable runs with their original SDK/profile version and use new profile IDs for changed configuration.