The repository or configuration that created this release differ from a previous release. View details.
SOFIA is an open-source, configurable multi-step agent framework for building advanced LLM-powered assistants. Define your agent's persona, tools, and step-by-step flows in Python or YAML—perfect for conversational, workflow, and automation use cases.
Features
- Step-based agent flows: Define agent behavior as a sequence of steps, each with its own tools and transitions.
- Persona-driven: Easily set the agent's persona for consistent, branded responses.
- Tool integration: Register Python functions as tools for the agent to call.
- Package-based tools: Reference Python package functions directly using
package_name:functionsyntax. - Auto tool documentation: Tool descriptions and parameter documentation are automatically generated from docstrings.
- YAML or Python config: Configure agents via code or declarative YAML.
- Step-level answer models: Specify an
answer_modelfor any step to receive structured (JSON/object) responses from the agent, enabling UIs and clients to render rich, custom layouts or workflows based on structured data, not just plain text. - OpenAI, Mistral, and Gemini LLM support
- Session management: Save and resume conversations with Redis or PostgreSQL persistent storage.
- Advanced error handling: Built-in error recovery mechanisms with configurable retry limits.
- API integration: Ready-to-use FastAPI endpoints for web and WebSocket interaction.
- Elastic APM tracing: Built-in support for distributed tracing and monitoring.
- Docker deployment: Pre-built base image for rapid deployment.
- Extensible: Build your own tools, steps, and integrations.
- Interactive CLI: Bootstrap new agents with
sofia init(install with[cli]extra).
Installation
From PyPI
pip install sofia-agent
With CLI support
pip install sofia-agent[cli]
With LLM support
pip install sofia-agent[openai] # For OpenAI support
pip install sofia-agent[mistralai] # For Mistral AI support
pip install sofia-agent[gemini] # For Google Gemini support
With tracing support
pip install sofia-agent[traces]
Usage: From No-Code to Low-Code to Full Code
CLI: Bootstrap a New Agent
sofia init
This will interactively guide you to create a config YAML and starter Python file for your agent.
Python API Example
from sofia_agent import *
from sofia_agent.llms import OpenAIChatLLM
def get_time():
"""Get the current time.
Returns:
str: The current time in string format.
"""
from datetime import datetime
return f"Current time: {datetime.now()}"
steps = [
Step(
step_id="start",
description="Greet and offer to tell the time or perform calculations.",
available_tools=["get_time", "math:sqrt"], # Direct reference to the sqrt function from math package
routes=[Route(target="end", condition="User is done")],
),
Step(
step_id="end",
description="Say goodbye.",
),
]
llm = OpenAIChatLLM()
agent = Sofia(
name="clockbot",
llm=llm,
steps=steps,
start_step_id="start",
tools=[get_time, "math:sqrt"], # Mix of custom functions and package references (Optional for package functions)
persona="You are a friendly assistant that can tell time and perform calculations.",
max_errors=3 # Will retry up to 3 times before failing
)
sess = agent.create_session()
# ... interact with sess.next(user_input)
Error Handling
SOFIA provides a configurable error handling mechanism:
# Configure the maximum number of consecutive errors before stopping
agent = Sofia(
name="robust-agent",
# ... other parameters
max_errors=5 # Default is 3
)
# Handle tool errors gracefully
try:
decision, result = session.next(user_input)
except ValueError as e:
# Handle error (e.g., maximum errors reached)
print(f"Error: {e}")
The agent will automatically retry on errors and provides informative error messages in the session history.
YAML Config Example
name: utility-bot
persona: You are a helpful utility bot that can perform various calculations and data operations.
steps:
- step_id: start
description: Handle user requests for mathematical operations or data processing.
available_tools:
- math:sqrt
- json:loads
- itertools:combinations
routes:
- target: end
condition: User is done with calculations
- step_id: end
description: Say goodbye to the user.
start_step_id: start
max_errors: 3 # Maximum consecutive errors before stopping
See examples/config.barista.yaml for a more full-featured example.
LLM Support
SOFIA supports multiple LLM providers out of the box:
OpenAI
from sofia_agent.llms import OpenAIChatLLM
llm = OpenAIChatLLM(
model="gpt-4o", # Optional, defaults to "gpt-4o-mini"
api_key="your-api-key" # Optional, defaults to OPENAI_API_KEY env var
)
Mistral AI
from sofia_agent.llms import MistralChatLLM
llm = MistralChatLLM(
model="mistral-medium", # Optional
api_key="your-api-key" # Optional, defaults to MISTRAL_API_KEY env var
)
Google Gemini
from sofia_agent.llms import GeminiLLM
llm = GeminiLLM(
model="gemini-pro", # Optional
api_key="your-api-key" # Optional, defaults to GOOGLE_API_KEY env var
)
You can also specify LLM configuration in your YAML config:
name: my-agent
llm:
provider: openai
model: gpt-4o
# ...rest of config
Configuration
- Persona: Set in YAML or Python for consistent agent style.
- Steps: Each step defines available tools, description, and routes to other steps.
- Tools: Python functions registered with the agent or package references.
Package Tool Integration
SOFIA now allows you to reference Python package functions directly using the package_name:function syntax:
# Reference a function from a standard library
"math:sqrt" # Standard library function
"json:loads" # Another standard library function
"itertools:combinations" # Complex functions work too!
# Reference nested module functions
"package_name:module.submodule.function"
Benefits of package tool integration:
- No-code/low-code development: Use existing Python functions without writing wrapper code
- Automatic documentation: Function docstrings are used to generate tool descriptions and parameter documentation
- Simplified configuration: Easily reference any Python function in your environment
Tool parameter descriptions in configuration files take precedence over automatically extracted docstring descriptions.
NOTE: Make sure the package is installed in your environment and function returns an output that is string representable.
Example: Barista Agent
A full example is provided in examples/barista/barista.py and examples/config.barista.yaml.
To run the Barista agent:
cd examples/barista
export OPENAI_API_KEY=your-api-key-here
python barista.py
# or
python barista_with_config.py
Example: Financial Planning Assistant
A production-ready example of a Financial Planning Assistant is available in examples/financial-advisor/. This example demonstrates:
- Budget planning and expense tracking
- Savings goal management
- Financial health assessment
- Uses the sofia-base Docker image
- Production-ready configuration
To run the Financial Planning Assistant:
docker run -e OPENAI_API_KEY=your-api-key-here -p 8000:8000 financial-advisor
Docker Base Image
SOFIA provides a base Docker image that you can use to quickly containerize your agents. The base image is available on Docker Hub as chandralegend/sofia-base.
To use the base image in your own agent:
- Create a Dockerfile:
FROM chandralegend/sofia-base:latest
# Copy your config file
COPY config.agent.yaml /app/config.agent.yaml
# Copy your tools
COPY tools.py /app/tools/
- Build and run your container:
docker build -t my-sofia-agent .
docker run -e OPENAI_API_KEY=your-api-key-here -p 8000:8000 my-sofia-agent
The base image supports configuration via environment variables:
| Variable | Description | Required |
|---|---|---|
OPENAI_API_KEY |
OpenAI API key | Yes (if using OpenAI) |
CONFIG_URL |
URL to download agent configuration | No |
CONFIG_PATH |
Path to mounted configuration file | No |
PORT |
Server port (default: 8000) | No |
DATABASE_URL |
PostgreSQL connection URL | No |
REDIS_URL |
Redis connection URL | No |
ENABLE_TRACING |
Enable OpenTelemetry tracing (true/false) |
No |
ELASTIC_APM_SERVER_URL |
Elastic APM server URL | If tracing enabled |
ELASTIC_APM_TOKEN |
Elastic APM Token | If tracing enabled |
SERVICE_NAME |
Service name for tracing | No (default: sofia-agent) |
SERVICE_VERSION |
Service version for tracing | No (default: 1.0.0) |
Tracing and Elastic APM Integration
SOFIA now supports distributed tracing using OpenTelemetry and can export traces to Elastic APM.
Enabling Tracing
To enable tracing, set the following environment variables:
| Variable | Description | Required |
|---|---|---|
ENABLE_TRACING |
Enable OpenTelemetry tracing (true/false) |
No (default: false) |
ELASTIC_APM_SERVER_URL |
Elastic APM server URL (e.g. http://localhost:8200) |
If tracing enabled |
ELASTIC_APM_TOKEN |
Elastic APM Token | If tracing enabled |
SERVICE_NAME |
Service name for tracing | No (default: sofia-agent) |
SERVICE_VERSION |
Service version for tracing | No (default: 1.0.0) |
Example: Running with Tracing Enabled
docker run \
-e ENABLE_TRACING=true \
-e ELASTIC_APM_SERVER_URL=http://your-apm-server:8200 \
-e ELASTIC_APM_TOKEN=your-apm-token \
-e SERVICE_NAME=my-sofia-agent \
-e SERVICE_VERSION=1.0.0 \
-e OPENAI_API_KEY=your-openai-key \
-p 8000:8000 my-sofia-agent
When tracing is enabled, SOFIA will automatically instrument agent sessions, tool calls, and LLM interactions, and send trace data to your Elastic APM instance.
Persistent Storage and Session Management
SOFIA base image supports multiple options for session storage:
In-Memory Storage
The default storage mechanism is in-memory, which does not persist sessions between container restarts.
Redis Session Storage
For caching and distributed deployments, you can use Redis as a session store:
docker run \
-e REDIS_URL=redis://redis:6379/0 \
-e OPENAI_API_KEY=your-openai-key \
-p 8000:8000 my-sofia-agent
PostgreSQL Persistent Storage
For fully persistent sessions that survive container restarts:
docker run \
-e DATABASE_URL=postgresql+asyncpg://user:pass@postgres/dbname \
-e OPENAI_API_KEY=your-openai-key \
-p 8000:8000 my-sofia-agent
API Endpoints
SOFIA base image provides the following REST and WebSocket endpoints:
Server-side Session Management
POST /session- Create a new sessionPOST /session/{session_id}/message- Send a message to a sessionWS /ws/{session_id}- WebSocket connection for real-time interactionDELETE /session/{session_id}- End a sessionGET /session/{session_id}/history- Get session history
Client-side Session Management
POST /chat- Stateless chat endpoint where the client maintains session state// Request format { "user_input": "Hello, how are you?", "session_data": { "session_id": "unique-id", "current_step_id": "start", "history": [] } } // Response format { "response": { "action": "answer", "input": "I'm doing well, how can I help you today?" }, "tool_output": null, "session_data": { "session_id": "unique-id", "current_step_id": "start", "history": [...] } }
For more details, see the base image README.
Contributing
Contributions are welcome! Please open issues or pull requests on GitHub.
From No-Code to Low-Code Evolution
SOFIA is evolving to support a spectrum of implementation approaches:
No-Code
- Configure agents entirely through YAML
- Reference existing Python functions using
package_name:functionsyntax - Auto-documentation from function docstrings
Low-Code
- Minimal Python code for custom tools
- Mix pre-existing package tools with custom tools
- Configure complex behaviors with minimal coding
Full-Code
- Complete control over agent implementation
- Custom tool development
- Advanced integrations and behaviors
This flexibility allows both non-programmers and experienced developers to create sophisticated AI agents that suit their needs.
License
MIT License. See LICENSE.
Acknowledgements
- Inspired by the open-source LLM community.
- Built with ❤️ by contributors.
Metadata
Release files for sofia-agent 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sofia_agent-0.1.12.tar.gz | 27.3 kB | With provenance | Details for sofia_agent-0.1.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sofia_agent-0.1.12-py3-none-any.whl | Python 3 | none | any | Details for sofia_agent-0.1.12-py3-none-any.whl |
Total release size: 57.0 kB
Release files / sofia_agent-0.1.12.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | sofia_agent-0.1.12.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7084ae628e7ef4630acc818c485a3d01c789ed5f3b918bea13e4bb86da36ba36
|
|
BLAKE2b-256 checksum How to use checksums |
99eab5dc8b84de3e7a61ecde7f81ac7e4dfda11c7dc1acd88f0779ab64c79d75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logRelease files / sofia_agent-0.1.12-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | sofia_agent-0.1.12-py3-none-any.whl |
|---|---|
| Size | 29.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3dc25e7695fa4a2b673d7f38e043dd23979f5a2724d7a6bec78a2b2f7f4cc466
|
|
BLAKE2b-256 checksum How to use checksums |
c4478195e35be21d7757a2dac7b2b2531a01cbd97435f8acb89cdd63eea890d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logSecurity for sofia-agent 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Change of provenance
The repository and configuration that created this release differ from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
- Removed 0.1.11 github.com/poly-eye/sofia
- Added 0.1.12 github.com/dowhiledev/sofia
Attestation for sofia_agent-0.1.12.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.