A lightweight and elegant Agent framework
Project description
lovia
lovia is a lightweight Python agent framework for people who want an agent loop, not a platform. It gives you the useful primitives: tools, streaming, structured output, sessions, handoff, guardrails, approvals, workspaces, skills, plugins, MCP, and a small web UI, while keeping the core easy to read and easy to replace.
pip install lovia
import asyncio
from lovia import Agent, Runner, tool
@tool
def add(a: int, b: int) -> int:
"""Add two integers."""
return a + b
async def main() -> None:
agent = Agent(
name="calculator",
instructions="Use tools when useful. Answer briefly.",
model="deepseek-v4-pro",
tools=[add],
)
result = await Runner.run(agent, "What is 21 + 21?")
print(result.output)
asyncio.run(main())
Set OPENAI_API_KEY for the official OpenAI endpoint, or set
OPENAI_BASE_URL to use any OpenAI-compatible service. Anthropic is built in
too: model="anthropic:claude-4-5-sonnet".
Why lovia
The agent ecosystem is full of heavy abstractions. lovia makes a different bet: the framework should be small enough to understand, but serious enough to ship.
- Small mental model. An
Agentdescribes behavior,Runnerexecutes it, and@toolexposes Python functions. Most of the framework follows from those three ideas. - Provider-neutral by design. Built-in adapters speak OpenAI Chat
Completions and Anthropic Messages directly over
httpx; custom providers implement a smallProtocol. - Python-native extension. Agents are dataclasses, providers, sessions, memory, plugins, skills, and workspaces are protocol-shaped. You plug things in; you do not subclass a framework universe.
- Minimal by default. The base install stays focused. Search, MCP, web UI, example niceties, and orchestration integrations live behind extras.
- Production primitives without ceremony. Approvals, guardrails, retries, budgets, cancellation, checkpoint/resume, context compaction, lifecycle hooks, and scoped workspace tools are available when you need them.
Philosophy
lovia optimizes for four things, in this order:
- Concise. A feature should fit in your head. The public surface should be obvious, and internals should be readable when you need to debug.
- Lightweight. The core should import quickly, install cleanly, and avoid dragging in infrastructure you did not ask for.
- Extensible. Real applications need their own providers, storage, policies, tools, and UI. lovia gives you seams instead of lock-in.
- General-purpose. The built-ins are practical, but not magical. They are examples of the same extension points you can use yourself.
The Core API
Agent
Agent is declarative runtime configuration. It has no conversation state, so
it is safe to reuse across requests.
from lovia import Agent
agent = Agent(
name="writer",
instructions="Write concrete, concise answers.",
model="deepseek-v4-pro",
)
Dynamic prompt fragments can depend on per-run context:
@agent.system_prompt
async def user_tier(ctx) -> str:
return f"User tier: {ctx.context['tier']}"
Create request-specific variants with clone():
strict = agent.clone(instructions="Answer with citations only.")
Runner
from lovia import Runner
result = await Runner.run(agent, "Draft a release note.")
print(result.output)
The handle returned by stream() is both async-iterable and awaitable:
from lovia import events
handle = Runner.stream(agent, "Explain context windows in one paragraph.")
async for ev in handle:
if isinstance(ev, events.TextDelta):
print(ev.delta, end="", flush=True)
result = await handle.result()
Scripts can use the sync wrapper:
result = Runner.run_sync(agent, "Summarize this file.")
Tools
Any typed Python callable can become a tool. lovia derives the tool schema from
type hints, docstrings, Annotated, and Pydantic Field metadata.
from typing import Annotated
from pydantic import Field
from lovia import tool
@tool
async def lookup_order(order_id: str) -> str:
"""Look up an order by id."""
return f"{order_id}: shipped"
@tool(strict=True)
def search_docs(
query: Annotated[str, "Search terms"],
limit: Annotated[int, Field(ge=1, le=10)] = 5,
) -> list[str]:
"""Search internal documentation."""
return []
Sync tools run in a worker thread. Async tools are awaited directly.
Structured Output
Pass a Pydantic model, dataclass, TypedDict, or supported Python type and the
final result is validated for you. If parsing fails, lovia asks the model once
to repair the response by default.
from pydantic import BaseModel
from lovia import Agent, Runner
class Brief(BaseModel):
title: str
bullets: list[str]
agent = Agent(
name="summarizer",
model="deepseek-v4-pro",
output_type=Brief,
)
result = await Runner.run(agent, "Summarize lovia for a Python developer.")
print(result.output.title)
You can override output type per call:
result = await Runner.run(agent, "Return a launch checklist.", output_type=list[str])
Provider Choice
Use a model string, a provider instance, or a fallback chain:
from lovia import Agent, ModelSettings
agent = Agent(
name="assistant",
model=[
"anthropic:claude-4-5-sonnet",
"deepseek-v4-pro",
],
settings=ModelSettings(temperature=0.2, max_tokens=800),
)
Custom providers implement the Provider protocol and can be registered with
the lovia.providers entry-point group.
Multi-Agent Workflows
Handoff
Handoff lets one agent transfer control to a specialist. The transcript follows the handoff, optionally filtered.
from lovia import Agent, Handoff, Runner, drop_stale_tool_calls
billing = Agent(name="billing", instructions="Handle billing issues.", model="deepseek-v4-pro")
support = Agent(name="support", instructions="Handle technical issues.", model="deepseek-v4-pro")
triage = Agent(
name="triage",
instructions="Route the user to the right specialist.",
model="deepseek-v4-pro",
handoffs=[billing, support],
)
result = await Runner.run(triage, "I was charged twice.")
Agent As Tool
Use an agent as a delegated subroutine:
summarizer = Agent(
name="summarizer",
instructions="Summarize text in five bullets.",
model="deepseek-v4-pro",
)
manager = Agent(
name="manager",
instructions="Delegate summarization when useful.",
model="deepseek-v4-pro",
tools=[summarizer.as_tool(description="Summarize a passage.")],
)
The sub-agent runs in its own loop and returns its final output as the tool result.
Human Control
Tool Approval
Gate sensitive actions with needs_approval=True.
from lovia import tool
@tool(needs_approval=True)
async def refund(order_id: str, amount_cents: int) -> str:
"""Issue a refund."""
return "refunded"
In streaming mode, resolve approvals from your UI:
from lovia import events
handle = Runner.stream(agent, "Refund order A123.")
async for ev in handle:
if isinstance(ev, events.ApprovalRequired):
ev.approve() # or ev.reject()
For server-side policy:
agent = agent.clone(
approval_handler=lambda call, ctx: "ask" if call.name == "refund" else "allow"
)
Ask A Human
ask_human lets the model request operator input through your application.
from lovia.tools.human import HumanChannel, ask_human
channel = HumanChannel()
agent = Agent(
name="assistant",
model="deepseek-v4-pro",
tools=[ask_human(channel)],
)
# Somewhere in your UI/event loop:
for question in channel.pending:
channel.answer(question.id, "Use option A.")
Sessions, Checkpoints, And Memory
Sessions persist conversation transcript across calls:
from lovia.stores import SQLiteSession
session = SQLiteSession("chat.db")
await Runner.run(agent, "My project is called Atlas.", session=session, session_id="u1")
result = await Runner.run(agent, "What is my project called?", session=session, session_id="u1")
Checkpoints are for crash recovery and idempotent long runs:
from lovia.stores import SQLiteCheckpointer
checkpoint = SQLiteCheckpointer("runs.db")
result = await Runner.run(
agent,
"Migrate the report format.",
checkpointer=checkpoint,
run_id="report-migration-42",
)
Memory is a small protocol for long-term semantic stores. lovia never injects memory automatically; wire it through tools or hooks so your product controls what the model sees.
Context Management
Long conversations use Compaction by default. It is view-only: the full
transcript stays in the session/checkpoint, while the per-model-call view can
offload huge tool results, clear older tool results, and summarize old history
under token pressure.
from lovia import Compaction, Runner
policy = Compaction(
context_window=200_000,
compact_at=0.75,
compact_to=0.50,
)
result = await Runner.run(agent, "Continue.", context_policy=policy)
Add recall_tool_result when you want the model to recover a compacted tool
result without re-running the tool:
from lovia.tools import recall_tool_result
agent = agent.clone(tools=[*agent.tools, recall_tool_result])
Use NoopContextPolicy() to disable automatic compaction.
Guardrails, Reliability, Hooks
Input and output guardrails are async callables. Raise GuardrailTripped or
return a truthy violation message to stop the run.
from lovia.exceptions import GuardrailTripped
async def no_email_addresses(messages, ctx):
if any("@" in str(m.content) for m in messages):
raise GuardrailTripped("Email addresses are not allowed.")
async def must_cite(output, ctx):
if "source:" not in output.lower():
return "Missing source citation."
agent = Agent(
name="researcher",
model="deepseek-v4-pro",
input_guardrails=[no_email_addresses],
output_guardrails=[must_cite],
)
Budgets, cancellation, and retry policies are explicit:
from lovia import RetryPolicy, RunBudget
result = await Runner.run(
agent,
"Analyze these logs.",
budget=RunBudget(max_tool_calls=20, max_seconds=60),
retry=RetryPolicy(max_retries=3),
)
Lifecycle hooks receive the same typed events used by streaming:
from lovia import events
from lovia.hooks import AgentHooks
hooks = AgentHooks()
@hooks.on(events.ToolCallStarted)
async def log_tool(ev):
print(ev.call.name, ev.call.arguments)
agent = agent.clone(hooks=hooks)
Built-In Tools
Nothing is imported into your agent automatically. Pick the tools you want.
from lovia.tools.http import http_fetch
from lovia.tools.time import now
from lovia.tools.search import duckduckgo_search_tool
agent = Agent(
name="researcher",
model="deepseek-v4-pro",
tools=[http_fetch, now, duckduckgo_search_tool()],
)
Install DuckDuckGo search support with:
pip install "lovia[ddg]"
Custom search is just a WebSearch implementation passed to web_search().
Skills
Skills are reusable instruction bundles following the Agent Skills specification. lovia exposes skill metadata up front, then lets the model load full instructions and referenced files only when needed.
from lovia import Agent, Skills
agent = Agent(
name="support",
instructions="Help customers using the right policy.",
model="deepseek-v4-pro",
skills=Skills.from_dir("./skills"),
)
A skill directory contains SKILL.md with YAML frontmatter, plus optional
references/, scripts/, and assets/ files. Multiple directories can be
merged:
skills = Skills.from_dir("./skills", "./team-skills")
Scope catalogs with a filter:
skills = Skills.from_dir(
"./skills",
filter=lambda meta: "internal" not in meta.extra.get("tags", []),
)
Plugins
A plugin bundles tools, instructions, view injectors, and hooks behind one object. The built-in todo plugin gives the model a checklist tool and re-shows the current list every turn without writing the reminder into the transcript.
from lovia import Agent, Runner, todo_plugin
agent = Agent(
name="builder",
instructions="Complete multi-step work carefully.",
model="deepseek-v4-pro",
plugins=[todo_plugin()],
)
await Runner.run(agent, "Implement a small REST API with tests and docs.")
The same plugin seam is useful for product-specific context, policy reminders, or observability bundles.
Workspace Agents
Workspace adds file and shell tools scoped to a root directory and permission
policy.
from lovia import Agent
from lovia.workspace import CommandRule, Workspace
agent = Agent(
name="coder",
instructions="Make small, targeted code changes.",
model="deepseek-v4-pro",
workspace=Workspace.local(
".",
mode="coding",
denied_paths=(".env*",),
command_rules=(
CommandRule("pytest", "allow"),
CommandRule("rm -rf", "deny"),
),
),
)
Modes:
| Mode | Tools |
|---|---|
readonly |
read_file, list_files, grep_files |
coding |
read tools plus write_file, edit_file, shell with approval by default |
trusted |
coding tools with shell allowed by default |
Workspace paths are root-relative; absolute paths, .. escapes, and symlink
escapes are rejected. The local shell still runs as the host user, so use
containerized or remote workspace backends when you need hard isolation.
MCP
Install optional MCP support:
pip install "lovia[mcp]"
Then attach servers; their tools are merged with ordinary lovia tools.
from lovia import Agent
from lovia.mcp import MCPServerStdio
agent = Agent(
name="assistant",
model="deepseek-v4-pro",
mcp_servers=[
MCPServerStdio(
name="web",
command="uvx",
args=["mcp-server-fetch"],
)
],
)
Each run opens and closes server configs safely. For reuse, open a session:
server = MCPServerStdio(name="web", command="uvx", args=["mcp-server-fetch"])
async with server.session() as conn:
agent = Agent(name="assistant", model="deepseek-v4-pro", mcp_servers=[conn])
await Runner.run(agent, "Fetch https://example.com and summarize it.")
Web UI
The optional web layer is a small FastAPI app with SSE streaming, sessions, markdown rendering, and approval routes.
pip install "lovia[web]"
from lovia.web import serve
serve(agent, host="127.0.0.1", port=8000, db_path="lovia.db")
Install Extras
| Need | Install |
|---|---|
| Core framework | pip install lovia |
| DuckDuckGo search | pip install "lovia[ddg]" |
| MCP integration | pip install "lovia[mcp]" |
| Web UI | pip install "lovia[web]" |
| Runnable examples | pip install "lovia[examples,web]" |
| Development | pip install -e ".[dev]" |
examples contains dependencies used only by runnable demos, such as
python-dotenv, rich, prefect, and ddgs. dev contains repository
maintenance dependencies: pytest, ruff, mypy, build, twine, and the
web test stack. They stay separate so normal development does not install
demo-only packages like Prefect.
Development
pip install -e ".[dev]"
.venv/bin/python -m pytest
.venv/bin/python -m ruff check .
.venv/bin/python -m ruff format .
.venv/bin/python -m mypy lovia
The examples/ directory contains runnable scripts for the major features.
Live provider tests are marked live_provider and stay skipped unless enabled
explicitly.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file lovia-0.6.3.tar.gz.
File metadata
- Download URL: lovia-0.6.3.tar.gz
- Upload date:
- Size: 509.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
b22a780def655be15a820eb8402bad93dc9979d4434dbecbfb6973b73dcd17fe
|
|
| MD5 |
81aa2d193889d1bd28232e0792453bac
|
|
| BLAKE2b-256 |
c65665a8f12615e611fd7b2d6aecdfc7450a2c694f63cd66d997ad0209b3a2a5
|
File details
Details for the file lovia-0.6.3-py3-none-any.whl.
File metadata
- Download URL: lovia-0.6.3-py3-none-any.whl
- Upload date:
- Size: 219.0 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
87220fea1b838cc3e215e07cde7c434b9dfffb959cc74810898568ddc19502de
|
|
| MD5 |
d82e8ceb4e0e99e5c97df8b5c3e64d5a
|
|
| BLAKE2b-256 |
f3f8aa1f9b05f15c67bfc850e4ffc0d58a2c456c39d6be9dc2c82325160ddc26
|