Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

AgentField Python SDK

The AgentField SDK provides a production-ready Python interface for registering agents, executing workflows, and integrating with the AgentField control plane.

Installation

pip install agentfield

To work on the SDK locally:

git clone https://github.com/Agent-Field/agentfield.git
cd agentfield/sdk/python
python -m pip install -e .[dev]

Quick Start

from agentfield import Agent

agent = Agent(
    node_id="example-agent",
    agentfield_server="http://localhost:8080",
    dev_mode=True,
)

@agent.reasoner()
async def summarize(text: str) -> dict:
    result = await agent.ai(
        prompt=f"Summarize: {text}",
        response_model={"summary": "string", "tone": "string"},
    )
    return result

if __name__ == "__main__":
    agent.serve(port=8001)

AI Tool Calling

Let LLMs automatically discover and invoke agent capabilities across your system:

from agentfield import Agent, AIConfig, ToolCallConfig

app = Agent(
    node_id="orchestrator",
    agentfield_server="http://localhost:8080",
    ai_config=AIConfig(model="openai/gpt-4o-mini"),
)

@app.reasoner()
async def ask_with_tools(question: str) -> dict:
    # Auto-discover all tools and let the LLM use them
    result = await app.ai(
        system="You are a helpful assistant.",
        user=question,
        tools="discover",
    )
    return {"answer": str(result), "trace": result.trace}

# Filter by tags, limit turns, use lazy hydration
result = await app.ai(
    user="Get weather for Tokyo",
    tools=ToolCallConfig(
        tags=["weather"],
        schema_hydration="lazy",  # Reduces token usage for large catalogs
        max_turns=5,
        max_tool_calls=10,
    ),
)

Key features:

  • tools="discover" — Auto-discover all capabilities from the control plane
  • ToolCallConfig — Filter by tags, agent IDs, health status
  • Lazy hydration — Send only tool names/descriptions first, hydrate schemas on demand
  • Guardrails — max_turns and max_tool_calls prevent runaway loops
  • Observability — result.trace tracks every tool call with latency

See examples/python_agent_nodes/tool_calling/ for a complete orchestrator + worker example.

MiniMax Video Generation

Set an API key and choose a video model from the MiniMax video API documentation:

export MINIMAX_API_KEY="..."
export MINIMAX_VIDEO_MODEL="..."

The global API base is used by default. Set MINIMAX_BASE_URL to select a region:

export MINIMAX_BASE_URL="https://api.minimax.io/v1"
# China: https://api.minimaxi.com/v1

Use the minimax/ model prefix to route the request to the MiniMax media provider:

import os

from agentfield import Agent, AIConfig

app = Agent(
    node_id="video-agent",
    agentfield_server="http://localhost:8080",
    ai_config=AIConfig(
        video_model=f"minimax/{os.environ['MINIMAX_VIDEO_MODEL']}",
    ),
)

result = await app.ai_generate_video(
    "A camera moves through a futuristic city",
    duration=6,
    resolution="1080p",
)
result.videos[0].save("video.mp4")

Note: AIConfig(minimax_api_key=..., minimax_base_url=...) takes precedence over the MINIMAX_API_KEY / MINIMAX_BASE_URL environment variables when both are set.

Human-in-the-Loop Approvals

The Python SDK provides a first-class waiting state for pausing agent execution mid-reasoner and waiting for human approval:

from agentfield import Agent, ApprovalResult

app = Agent(node_id="reviewer", agentfield_server="http://localhost:8080")

@app.reasoner()
async def deploy(environment: str) -> dict:
    plan = await app.ai(f"Create deployment plan for {environment}")

    # Pause execution and wait for human approval
    result: ApprovalResult = await app.pause(
        approval_request_id="req-abc123",
        expires_in_hours=24,
        timeout=3600,
    )

    if result.approved:
        return {"status": "deploying", "plan": str(plan)}
    elif result.changes_requested:
        return {"status": "revising", "feedback": result.feedback}
    else:
        return {"status": result.decision}

Two API levels:

  • High-level: app.pause() blocks the reasoner until approval resolves, with automatic webhook registration
  • Low-level: client.request_approval(), client.get_approval_status(), client.wait_for_approval() for fine-grained control

See examples/python_agent_nodes/waiting_state/ for a complete working example.

See docs/DEVELOPMENT.md for instructions on wiring agents to the control plane.

Running several agents in one process (AgentMesh)

from agentfield import Agent, AgentMesh

writer = Agent(node_id="writer")
editor = Agent(node_id="editor")

@editor.reasoner()
async def revise(text: str) -> dict:
    return {"text": text.strip()}

@writer.reasoner()
async def draft(topic: str) -> dict:
    return await writer.call("editor.revise", text=f"Draft about {topic}")

AgentMesh([writer, editor]).run(port=8000)

AgentMesh v1 is offline-only. See the AgentMesh guide for mount layout, call_local, error behavior, and limitations.

Logging

  • AGENTFIELD_LOG_STDOUT controls the on-by-default structured JSON mirror. Set it to 0, false, no, or off to disable the mirror; execution-scoped records still dispatch to the control plane.
  • AGENTFIELD_LOG_QUEUE controls the Python SDK's bounded stdout writer queue. It is enabled by default for real-fd writes made from a running event loop; see the environment-variable reference for queue sizing, overflow, shutdown, and opt-out details.
  • AGENTFIELD_LOG_MAX_LINE_BYTES defaults to 16384 bytes and clamps any integer below 256 to 256. It limits both captured stdout/stderr lines and structured-mirror records; non-integers use the default.
  • AGENTFIELD_LOGS_ENABLED controls stdout/stderr capture and the node logs endpoint only, not control-plane execution-log dispatch.
  • AGENTFIELD_LOG_LEVEL controls human-readable Python SDK logging and defaults to WARNING.

See the environment-variable reference and agent-node logs API for details.

Testing

./scripts/run_pytest.sh

To run coverage locally:

./scripts/run_pytest.sh --cov=agentfield --cov-report=term-missing

The wrapper sets a private PYTEST_DEBUG_TEMPROOT automatically so local runs and CI do not rely on pytest's predictable default temp directory layout.

License

Distributed under the Apache 2.0 License. See the project root LICENSE for details.

Realtime session turn detection

See session turn detection and interruption for VAD configuration, defaults, validation, and the WebRTC connection flow.

Metadata

Release files for agentfield 0.1.146rc7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agentfield 0.1.146rc7
File Size Uploaded Provenance Actions
agentfield-0.1.146rc7.tar.gz 355.8 kB Without provenance Details for agentfield-0.1.146rc7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agentfield 0.1.146rc7
File Interpreter ABI Platform Actions
agentfield-0.1.146rc7-py3-none-any.whl Python 3 none any Details for agentfield-0.1.146rc7-py3-none-any.whl

Total release size: 749.5 kB

Release files / agentfield-0.1.146rc7.tar.gz

Download URL agentfield-0.1.146rc7.tar.gz
Size 355.8 kB
Tags Source
SHA-256 checksum
How to use checksums
ddba611890122fd848fdf0ca505709888783554983ee6dcea8e067142f764e93
BLAKE2b-256 checksum
How to use checksums
df6159d136d138e7e096ea3c2eb1266b044e8fe8ff108062e61c006e795913f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.17

Release files / agentfield-0.1.146rc7-py3-none-any.whl

Download URL agentfield-0.1.146rc7-py3-none-any.whl
Size 393.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a0c572a741f357ef63a665a47be47597ccecb76c5553090e847933674321dc1e
BLAKE2b-256 checksum
How to use checksums
53f6474cab1f62173c4576b4037d09b2d98dc2c60945880df3e947d1bb45b84b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.17

Security for agentfield 0.1.146rc7

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page