正在載入完整 README。 以下為已儲存的摘錄。
Mojentic is a framework that provides a simple and flexible way to interact with Large Language Models (LLMs). It offers integration with various LLM providers and includes tools for structured output generation, task automation, and more. With comprehensive support for all OpenAI models including GPT-5 and automatic parameter adaptation, Mojentic handles the complexities of different model types seamlessly. The future direction is to facilitate a team of agents, but the current focus is on robust LLM interaction capabilities.檢視完整 README ↗Mojentic is a framework that provides a simple and flexible way to interact with Large Language Models (LLMs). It offers integration with various LLM providers and includes tools for structured output generation, task automation, and more. With comprehensive support for all OpenAI models including GPT-5 and automatic parameter adaptation, Mojentic handles the complexities of different model types seamlessly. The future direction is to facilitate a team of agents, but the current focus is on robust LLM interaction capabilities.
mxbai-embed-large for embeddingsWe recommend using uv for fast, reliable Python project management.
# Install from PyPI using uv
uv pip install mojentic
# Or with pip
pip install mojentic
Or install from source:
git clone https://github.com/svetzal/mojentic.git
cd mojentic
# Using uv (recommended)
uv sync
# Or with pip
pip install -e .
from mojentic.llm import LLMBroker
from mojentic.llm.gateways import OpenAIGateway, OllamaGateway
from mojentic.llm.gateways.models import LLMMessage
from mojentic.llm.tools.date_resolver import ResolveDateTool
from pydantic import BaseModel, Field
# Initialize with OpenAI (supports all models including GPT-5, GPT-4.1, reasoning models)
openai_llm = LLMBroker(model="gpt-5", gateway=OpenAIGateway(api_key="your_api_key"))
# Or use other models: "gpt-4o", "gpt-4.1", "o1-mini", "o3-mini", etc.
# Or use Ollama for local LLMs
ollama_llm = LLMBroker(model="qwen3:32b")
# Simple text generation
result = openai_llm.generate(messages=[LLMMessage(content='Hello, how are you?')])
print(result)
# Generate structured output
class Sentiment(BaseModel):
label: str = Field(..., description="Label for the sentiment")
sentiment = openai_llm.generate_object(
messages=[LLMMessage(content="Hello, how are you?")],
object_model=Sentiment
)
print(sentiment.label)
# Use tools with the LLM
result = openai_llm.generate(
messages=[LLMMessage(content='What is the date on Friday?')],
tools=[ResolveDateTool()]
)
print(result)
# Image analysis
result = openai_llm.generate(messages=[
LLMMessage(content='What is in this image?', image_paths=['path/to/image.jpg'])
])
print(result)
OpenAIGateway now supports environment-variable defaults so you can get started without hardcoding secrets:
api_key, it will use the OPENAI_API_KEY environment variable.base_url, it will use the OPENAI_API_ENDPOINT environment variable (useful for custom endpoints like Azure/OpenAI-compatible proxies).OpenAIGateway(api_key=..., base_url=...) always override environment variables.Examples:
from mojentic.llm import LLMBroker
from mojentic.llm.gateways import OpenAIGateway
# 1) Easiest: rely on environment variables
# export OPENAI_API_KEY=sk-...
# export OPENAI_API_ENDPOINT=https://api.openai.com/v1 # optional
llm = LLMBroker(
model="gpt-4o-mini",
gateway=OpenAIGateway() # picks up OPENAI_API_KEY/OPENAI_API_ENDPOINT automatically
)
# 2) Explicitly override one or both values
llm = LLMBroker(
model="gpt-4o-mini",
gateway=OpenAIGateway(api_key="your_key", base_url="https://api.openai.com/v1")
)
The framework automatically handles parameter differences between model types, so you can switch between any models without code changes.
Some models have specific parameter restrictions that are automatically handled:
temperature=1.0 when explicitly requested. Other temperature values are automatically adjusted with a warning.temperature=1.0 when explicitly requested. Other temperature values are automatically adjusted with a warning.temperature parameter at all. The parameter is automatically removed with a warning.max_completion_tokens instead of max_tokens, and have limited tool support.The framework will automatically adapt parameters and log warnings when unsupported values are provided.
In 3.0, temperature, context and output limits default to None and stay off the
wire. Use max_tokens as the only output control; num_predict is only Ollama's
wire field. Anthropic requires an output limit and uses its registered maximum
or 4096 for unknown models. ChatSession's max_context only trims local history.
For former config defaults, explicitly set
CompletionConfig(temperature=1.0, num_ctx=32768, max_tokens=16384).
See request fidelity and migration.
src/
├── mojentic/ # Main package
│ ├── llm/ # LLM integration (primary focus)
│ │ ├── gateways/ # LLM provider adapters (OpenAI, Ollama)
│ │ ├── registry/ # Model registration
│ │ └── tools/ # Utility tools for LLMs
│ ├── agents/ # Agent implementations (under development)
│ ├── context/ # Shared memory and context (under development)
├── _examples/ # Usage examples
The primary focus is currently on the llm module, which provides robust capabilities for interacting with various LLM providers.
Visit the documentation for comprehensive guides, API reference, and examples.
# Clone the repository
git clone https://github.com/svetzal/mojentic.git
cd mojentic
# Using uv (recommended)
uv sync --extra dev
# Or with pip
pip install -e ".[dev]"
# Run tests
pytest
# Quality checks
flake8 src # Linting
bandit -r src # Security scan
pip-audit # Dependency vulnerabilities
The agentic aspects of this framework are in the highest state of flux. The first layer has stabilized, as have the simpler parts of the second layer, and we're working on the stability of the asynchronous pubsub architecture. We expect Python 3.14 will be the real enabler for the async aspects of the second layer.
This code is Copyright 2025 Mojility, Inc. and is freely provided under the terms of the MIT license.
Ollama, oMLX and OpenAI ordinary, structured, and tool-capable streaming completions can use an explicit RecoveryPolicy
through the existing broker and chat session APIs. Local retries require caller admission
when inference termination is unknown. See the migration guide
for bounded delays, cancellation, safe reports, and caller-owned wire capture.
Anthropic supports opt-in ordinary completion recovery; structured output, streaming and tools remain unsupported.
Cloud retries may proceed without an admission hook; local retries still require explicit admission.
Raw stream-event APIs retain their existing single-request compatibility behavior.
Supported streams report client-measured time_to_first_token_ms,
first_token_kind and request_duration_ms independently of provider metrics.
Read terminal event metadata/metrics, or last_stream_metrics after consuming a
legacy gateway, broker or session text stream. Timing starts at HTTP dispatch,
spans admitted retries, and resets for tool continuations. See
stream timing.