Skip to main content

Embeddable agent execution kernel — LLM loop, hooks, events, tools, dynamic sub-agents.

Project description

power-loop

Documentation | 中文文档 | Examples | Changelog

Embeddable, stateful agent execution for Python.

power-loop gives application code one small interface, StatefulAgentLoop, and handles the repetitive agent runtime work around it: multi-turn LLM loops, tool calls, hooks, events, context compaction, sub-agents, retry/cancel, structured output, memory, and SQLite-backed session persistence.

It is a library, not a service or a full application framework. You keep ownership of product logic, HTTP APIs, auth, queues, RAG, UI, and deployment.

Scope: orchestration, not isolation

power-loop orchestrates the agent loop; it does not sandbox tool execution. The built-in bash / file tools run in-process (a subprocess shell inheriting the host environment) — convenient for trusted, local use, but not a security boundary. If your agent runs model-authored or otherwise untrusted commands, run them in your own sandbox (container / gVisor / microVM) and inject it via the ShellBackend seam (runtime.exec_backend); power-loop launches the persistent shell through your backend. Keep secrets in your orchestrator — the loop does not scrub the tool environment for you.

Likewise there is no built-in scheduler/timer: a session only runs while a send() / resume() call is in flight. "Wake this agent again in 10 minutes" is orchestrator state — keep it in your own durable store and call send() when it fires (that survives restarts; an in-process timer would not).

Install

pip install power-loop

For local development:

git clone https://github.com/PL-play/power-loop.git
cd power-loop
pip install -e ".[dev]"

Python 3.10+ is required.

Quick Example

import asyncio

from power_loop import AgentLoopConfig, StatefulAgentLoop, create_llm_service_from_env


async def main() -> None:
    llm = create_llm_service_from_env()
    loop = StatefulAgentLoop(
        llm=llm,
        db_path="./power_loop_sessions.db",
        config=AgentLoopConfig(
            system_prompt="You are a concise assistant.",
            max_rounds=4,
        ),
    )

    sid = loop.new_session(metadata={"user_id": "demo"})
    first = await loop.send("My favorite color is teal.", session_id=sid)
    second = await loop.send("What is my favorite color?", session_id=sid)

    print(second.final_text)


asyncio.run(main())

Configure any OpenAI-compatible endpoint with environment variables:

POWER_LOOP_BASE_URL=https://api.openai.com/v1
POWER_LOOP_API_KEY=sk-...
POWER_LOOP_MODEL=gpt-4o-mini

See Getting Started for the complete first run.

What It Provides

Capability Where to read more
Stateful sessions and cross-process resume Sessions
Tool calling with JSON Schema validation Tools
Lifecycle hooks for control flow Hooks
Typed events for streaming, audit, and metrics Events
Context compaction Compaction
Sub-agents with AgentSpec Sub-agents
Retry, timeout, and cancellation Retry & Cancel
Structured JSON output Structured Output
Pluggable cross-session memory Memory
Provider configuration Providers

Per-call overrides

Build one loop and reuse it across callers; restrict tools or swap the system prompt per send without rebuilding (the model only sees the allowed tools). Ideal for multi-tenant hosts.

# loop registered with all tools; this run exposes only "get_weather"
await loop.send("…", session_id=sid, tools=["get_weather"])

# per-run system prompt override (precedence: per-call > session > config)
await loop.send("…", session_id=sid, system_prompt="You are a terse bot.")

The same overrides are available on send_sync(). When follow_up() is idle and falls back to a new send, it accepts them too. A follow-up queued into an already running call keeps that call's active tool and prompt policy.

For a multi-tenant host that reuses one registry across workspaces, build an unbound registry and supply the workspace at invocation time:

from power_loop import RuntimeEnv, create_default_tool_registry, runtime_env_context

registry = create_default_tool_registry(preset="core", bind=False)
with runtime_env_context(RuntimeEnv(workspace_dir=tenant_workspace)):
    result = await registry.invoke_async("read_file", {"path": "README.md"})

See examples/23_per_send_overrides.py.

Token usage accounting

Every send() returns the run's cumulative token usage — summed over all LLM calls of that run (tool loops make several) — so cost accounting needs no event plumbing:

res = await loop.send("…", session_id=sid)
res.usage
# {"prompt_tokens": 1234, "completion_tokens": 56, "cache_read_tokens": 0,
#  "reasoning_tokens": 0, "total_tokens": 1290, "calls": 2}

For per-call, real-time metering subscribe to the usage_updated event (one per LLM call, tagged with session_id). See examples/25_token_usage.py.

Crash recovery: heal_pending

A run killed mid tool-call leaves the session with unresolved tool_calls; the next send() raises SessionPendingError (the message protocol forbids continuing). Orchestrators whose runs can legitimately die (human interrupts, process restarts) can opt into self-healing:

res = await loop.send("…", session_id=sid, heal_pending=True)
# stale tool_calls are aborted with synthetic <aborted> results, then the
# send proceeds. Default remains raise — healing discards in-flight work.

Or recover explicitly with resume(sid) / abort_pending(sid).

Public API

Stable imports are re-exported from power_loop:

from power_loop import (
    AgentLoopConfig,
    StatefulAgentLoop,
    StatefulResult,
    ToolDefinition,
    ToolRegistry,
)

The stability tiers are:

Tier Meaning
Stable Backward compatible across minor releases. Listed in power_loop.STABLE_API.
Provisional Available from the top-level package during 0.x, but may change.
Internal Submodule imports such as power_loop.core.*; no compatibility promise.

See the API reference for the current surface.

Examples

The examples/ directory is ordered from minimal usage to full chatbot composition:

python examples/00_hello_world.py
python examples/02_tool_calling.py
python examples/19_full_chatbot.py

The full list is in examples/README.md.

Development

pip install -e ".[dev]"
ruff check .
pytest -q --no-real

Real LLM examples/tests use POWER_LOOP_* or the legacy OPENAI_COMPAT_* variables.

Project Links

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

power_loop-0.9.0.tar.gz (136.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

power_loop-0.9.0-py3-none-any.whl (155.3 kB view details)

Uploaded Python 3

File details

Details for the file power_loop-0.9.0.tar.gz.

File metadata

  • Download URL: power_loop-0.9.0.tar.gz
  • Upload date:
  • Size: 136.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for power_loop-0.9.0.tar.gz
Algorithm Hash digest
SHA256 7aee192a0b605e37aff8fa7f1a7958812b79948d671bf304d54a830f9e5ed262
MD5 d2350883554f11046de3d4781605b957
BLAKE2b-256 8f00b4637fb811bb1b9428441d219e7621820328e62624135a64720384ebe1e3

See more details on using hashes here.

File details

Details for the file power_loop-0.9.0-py3-none-any.whl.

File metadata

  • Download URL: power_loop-0.9.0-py3-none-any.whl
  • Upload date:
  • Size: 155.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for power_loop-0.9.0-py3-none-any.whl
Algorithm Hash digest
SHA256 a16e490d8e0b3a5d7c690c628c3a500aba7c1de19bcd5fa0d3b26bf15ba5a7f8
MD5 38a9cacd5c253459055a950a404ea363
BLAKE2b-256 8b33041b571de08b65bb1dee297bca68924cd803e478053eca72d6154f29daa6

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page