Skip to main content

Halios

PyPI version License

Your pair programmer for AI agent evaluations.

Halios helps you build reliable AI agents in minutes. Add the Halios skill to Codex, Claude Code, Cursor, or your favorite coding agent, and create eval suites, run multi-turn simulations, investigate failures, and gate pull requests directly from your repository.

Halios provides the evaluation framework, developer tools, and hosted evaluation runtime underneath.


Quickstart

1. Install the Agent Skill

Add the Halios skill to your coding agent environment:

npx skills add HaliosAI/halios --skill halios

(Works with Codex, Claude Code, Cursor, GitHub Copilot, Gemini CLI, OpenCode, and any harness supporting the open Agent Skills format).

2. Ask Your Coding Agent

Prompt your agent to set up evaluations for your project:

"Set up evals for this agent: inspect the repository, create realistic test scenarios and checks, run one smoke test, and summarize before asking whether to run the full suite."

Your agent will inspect your application entrypoint, configure standard OpenTelemetry, draft scenarios in .halios/, and run one smoke scenario. It stops with a verification summary before asking whether to run the full suite and how many trials per scenario to use. The summary includes direct Halios UI links for reviewing the materialized suite, smoke run, and trace evidence.

If the Halios CLI is missing, the coding agent will tell you before installing haliosai-cli as user-level tooling that can be reused across projects. It is kept separate from your application's runtime dependencies.

When evidence or access is missing

The Skill continues supportable work and records unresolved evidence, access, policy, capability, or verification needs in optional .halios/discovery.yml. This applies to any agent, including RAG applications with inaccessible knowledge sources. Its handoff distinguishes completed work, unverified or pending work, and the next input/action needed.

halios eval review --json exposes these local notes under discovery, separately from executable suite validation. Open or malformed discovery notes produce advisory output without changing review exit codes or evaluation gates. A passing configured suite is not proof of missing coverage. The notes are not uploaded, executed, or used as grading inputs; see the discovery contract. Existing projects need no new file.


Standalone CLI Installation

If you prefer to drive evaluations directly from the command line or CI:

# Recommended: Install with uv tool
uv tool install 'haliosai-cli>=2.0.7'

# Or install with pipx
pipx install 'haliosai-cli>=2.0.7'

# See available commands and usage
halios --help

The API and UI use the same origin by default. For a self-hosted deployment with separate origins, set HALIOS_UI_URL so structured review links point to the web application without changing the API endpoint used by HALIOS_BASE_URL.


How It Works

  1. Inspect & Connect: Your coding agent inspects your agent's tools, policies, and runtime, then configures standard OpenTelemetry export.
  2. Author Scenarios & Checks: Test cases, rubrics, and failure criteria are stored directly in your repository (.halios/scenarios.yml and .halios/eval.yml). You own the evaluation suite.
  3. Simulate Multi-Turn Trajectories: Halios runs fresh simulation passes against your agent across edge cases, tool dependencies, and user personas.
  4. Investigate & Fix Failures: Pinpoint hallucinated parameters, broken tool handoffs, or policy violations from complete trace evidence.
  5. Gate Pull Requests: Run protected checks in CI to block regressions before merging to production.
  6. Monitor Production: Evaluate production traces using the same checks, and turn real-world failures into new regression test scenarios.

Key Principles

  • You own the evaluation suite: Scenarios and checks are clean YAML files stored in your Git repository.
  • Fresh simulations, not static replays: Halios tests real agent execution across multiple turns, rather than replaying outdated completions.
  • Framework agnostic: Works with any agent architecture—OpenAI Agents SDK, LangChain, LlamaIndex, PydanticAI, or custom workflows.
  • Stock OpenTelemetry: Applications emit standard OpenTelemetry GenAI spans; no proprietary vendor lock-in in your production runtime.
  • Unified local, CI, and production loop: The same checks run during local development, gate merge requests in CI, and monitor live production traces.

Resources


Development

# Clone and install locally in editable mode
git clone https://github.com/HaliosAI/halios.git
cd halios
python -m pip install -e '.[dev]'

# Run the test suite
python -m pytest -q

License

Apache 2.0 © Anomalytica Inc. 2026

Metadata

Release files for haliosai-cli 2.0.8

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

Source distribution (sdist)

Source distribution for haliosai-cli 2.0.8
File Size Uploaded
haliosai_cli-2.0.8.tar.gz 47.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for haliosai-cli 2.0.8
File Interpreter ABI Platform
haliosai_cli-2.0.8-py3-none-any.whl Python 3 none any Details

Total release size: 93.5 kB

Release files / haliosai_cli-2.0.8.tar.gz

Download URL haliosai_cli-2.0.8.tar.gz
Size 47.9 kB
Tags Source
SHA-256 checksum
How to use checksums
244bb887d4e571ff0d0bc20f6a5d2ae5aa4075e3211b83e32b36ba97649e41a9
BLAKE2b-256 checksum
How to use checksums
8d81fd328d3b4da0052fde2a954b5cb8daad9f8313bada395d305f4fffc9152e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 29, 2026.

Transparency log

Release files / haliosai_cli-2.0.8-py3-none-any.whl

Download URL haliosai_cli-2.0.8-py3-none-any.whl
Size 45.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b750dca1ea2b46892e9d1b3fee1d33a05646c36dc367ca2d6e8d1caeada14e76
BLAKE2b-256 checksum
How to use checksums
77d5d1d9b7362d095b939247d7cdb4d8cd6294ba682a81c261bcb2a11b2f3885
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 29, 2026.

Transparency log

Release history Release notifications | RSS feed

2.0.9

2 release files

This release

2.0.8 This release

2 release files

2.0.7

2 release files

2.0.6

2 release files

2.0.5

2 release files

2.0.4

2 release files

2.0.3

2 release files

2.0.2

2 release files

2.0.1

2 release files

2.0.0

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