Skip to main content

Harness Observability Layer

Harness Observability Layer, or HOL, is a local-first dashboard for inspecting archived agent sessions from the current project.

Today HOL centers on a localhost experience:

  • it discovers Codex and Claude Code session archives that belong to the current repository
  • it normalizes those sessions into a shared event model in memory
  • it computes aggregate metrics, prompt-group rankings, turn rankings, and prescriptive insights
  • it serves a project dashboard locally at http://localhost

The main product experience is one command:

hol init

What HOL Does Today

HOL is built for questions like:

  • where did spend accumulate in this project
  • which prompts or turns were disproportionately expensive
  • whether long context or missing /clear is driving cost
  • whether model choice looks justified
  • which sessions deserve review first

The dashboard is project-level first. It gives you one entrypoint with:

  • aggregate spend and token cards
  • prompt-group and turn rankings
  • model mix and daily trends
  • sessions requiring attention
  • prescriptive insights based on the imported session behavior

Install

pip install harness-observability-layer

This exposes:

hol --help

You can also run the package directly during development:

python -m harness_observability_layer --help

Development Install

For local development from this repository:

pip install -e .

For release validation and packaging tooling during development:

pip install -e .[dev]

Quick Start

From the project you want to inspect:

hol init

That starts a local dashboard server and opens the browser to:

http://localhost:3845

Useful variants:

hol init --no-open
hol init --port 4000
hol init --resolve-files

If you want the aggregate payload that powers the dashboard:

hol data

CLI Surface

HOL currently exposes a deliberately small command surface:

Start the dashboard

hol init

Flags:

  • --port
  • --host
  • --no-open
  • --resolve-files

Print the live aggregate JSON

hol data

Flags:

  • --resolve-files

Local Server

When HOL is running, it serves:

  • / for the dashboard HTML
  • /api/data for the current aggregate JSON
  • /api/refresh to rebuild the in-memory aggregate and return a small status payload

The default bind is:

127.0.0.1:3845

Session Discovery

HOL automatically looks for both Codex and Claude Code archives and filters them to the current project when the archived session records a matching cwd.

Codex discovery

Resolution order:

  1. HOL_CODEX_ARCHIVED_DIR
  2. CODEX_ARCHIVED_SESSIONS_DIR
  3. auto-discovery of local defaults such as:
    • $XDG_DATA_HOME/codex/archived_sessions
    • ~/.config/codex/archived_sessions
    • ~/.codex/archived_sessions

Claude Code discovery

Resolution order:

  1. HOL_CLAUDE_ARCHIVED_DIR
  2. CLAUDE_ARCHIVED_SESSIONS_DIR
  3. auto-discovery of local defaults such as:
    • $XDG_DATA_HOME/claude/projects
    • ~/.config/claude/projects
    • ~/.claude/projects

Sessions without a usable cwd remain eligible. Sessions that clearly belong to another project are skipped.

Privacy And Security

HOL is intended to stay local-first.

Current behavior:

  • session archives are read from local disk
  • normalization and aggregation happen in memory
  • the dashboard is served from localhost
  • HOL does not require a remote backend to produce the dashboard

The localhost dashboard currently exposes project aggregates through /api/data, so it should be treated as local sensitive data while the server is running.

Security-sensitive areas for this repository include:

  • session prompt and tool-output disclosure
  • local path leakage
  • archive discovery and filtering
  • hidden network behavior
  • localhost exposure beyond the intended interface

See also:

Local Development

Run the test suite with:

python -m unittest discover -s tests

If you want to test the local checkout directly:

PYTHONPATH=src python3 -m harness_observability_layer.cli.main --project-root . init --no-open

Repository-Local Helper

This repository still contains lower-level normalization, metrics, and reporting modules that are useful for development and internal testing. The public user-facing product, however, is the localhost dashboard started by hol init.

Citation

If you use this project in research, documentation, or derivative tooling, please cite it using CITATION.cff.

Metadata

Release files for harness-observability-layer 1.1.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 harness-observability-layer 1.1.1
File Size Uploaded
harness_observability_layer-1.1.1.tar.gz 104.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for harness-observability-layer 1.1.1
File Interpreter ABI Platform
harness_observability_layer-1.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 211.5 kB

Release files / harness_observability_layer-1.1.1.tar.gz

Download URL harness_observability_layer-1.1.1.tar.gz
Size 104.8 kB
Tags Source
SHA-256 checksum
How to use checksums
363a3b36a7aaf7d9f8ffd8d33340da30885abd4875c533677550c4f3813553d1
BLAKE2b-256 checksum
How to use checksums
a983a14874879bc4613656737d8cdd30897d6e024cf1e7e990535229a0418095
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 Apr 20, 2026.

Transparency log

Release files / harness_observability_layer-1.1.1-py3-none-any.whl

Download URL harness_observability_layer-1.1.1-py3-none-any.whl
Size 106.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0ada9389fc7a995991789c3ed06f1952d577f5e159be03721cfed688c7bf4821
BLAKE2b-256 checksum
How to use checksums
ee9e6db8d5607526a3a6ec927ee0b05efdc4598f67eb02225c339d4270bcf76c
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 Apr 20, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.1.1 This release

2 release files

1.1.0

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

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