Skip to main content

Hellig

Multi-agent natural language orchestration programming framework.

Hellig lets you compose programs out of natural language steps that are dispatched to specialized agents. Treat prompts as instructions, agents as functions, and an orchestrator as the runtime that wires them together.

PyPI Python License

Why Hellig

Modern LLM applications quickly outgrow a single prompt. Hellig provides a tiny, opinionated core so you can:

  • Describe work in natural language and let agents do the heavy lifting.
  • Compose programs as ordered steps, with named outputs feeding later prompts.
  • Swap agent runtimes (any LLM client, a local model, or a stub for tests) without rewriting your orchestration.
  • Operate from the terminal with the hg CLI for quick experiments.

Install

pip install hellig
# or
uv add hellig

Quick start

from hellig import Agent, Orchestrator, Program

def echo_runtime(prompt: str, **_: object) -> str:
    return prompt.upper()

researcher = Agent(name="researcher", instructions="You research topics.", runtime=echo_runtime)
writer = Agent(name="writer", instructions="You write summaries.", runtime=echo_runtime)

program = (
    Program(name="brief")
    .add("researcher", "Collect facts about {topic}", output="facts")
    .add("writer", "Write a 3-bullet summary of:\n{facts}", output="summary")
)

orchestrator = Orchestrator().register(researcher).register(writer)
result = orchestrator.run(program, topic="agentic programming")
print(result["summary"])

Core concepts

Concept Description
Agent A named worker with optional instructions, runtime, and tools.
Program An ordered sequence of natural language Steps with named outputs.
Orchestrator Registers agents and executes programs, threading outputs into later prompts.

Steps use str.format substitution, so any prior step's output (and any context kwargs passed to run) is available as a placeholder.

CLI

The package installs an hg command powered by Click:

hg --help
hg version
hg hello HSPK
hg run --agent researcher --agent writer \
       --step researcher "Find facts about Hellig" \
       --step writer "Summarize the facts"

Development

uv sync
uv run hg --help
uv build

Roadmap

  • Pluggable LLM runtimes (OpenAI, Anthropic, local).
  • Tool calling and structured outputs.
  • Parallel and conditional steps.
  • Persistent traces for debugging.

License

MIT © HSPK

Metadata

Release files for hellig 0.0.1

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

Source distribution (sdist)

Source distribution for hellig 0.0.1
File Size Uploaded
hellig-0.0.1.tar.gz 3.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for hellig 0.0.1
File Interpreter ABI Platform
hellig-0.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 9.3 kB

Release files / hellig-0.0.1.tar.gz

Download URL hellig-0.0.1.tar.gz
Size 3.7 kB
Tags Source
SHA-256 checksum
How to use checksums
643ba73ee44bcbf69f640ae9301690b95334c35a748c370ae00ed7b0ab2f5cda
BLAKE2b-256 checksum
How to use checksums
1f20a2eccfe79373b99a7e16b0758c42e424e3a50f4a42fbf9fe0b9b50363369
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.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.

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 Jun 10, 2026.

Transparency log

Release files / hellig-0.0.1-py3-none-any.whl

Download URL hellig-0.0.1-py3-none-any.whl
Size 5.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fc3ee6996aceb0923eb98374a9bf082afb02d7b651320fb19d9338c851a4fabe
BLAKE2b-256 checksum
How to use checksums
83eee9424046d35173c99c0eb890f5e4bf0efcf9f0b38e2ddb345474eef890d2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.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.

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 Jun 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files

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