
Built an offline harness that conforms to your agent loop, not the other way around
I have been trying a bunch of harness models and frameworks for the last month, and I realize most agent frameworks want you to rebuild your runtime around their harness.
We went the other way with AURA Harness: a thin membrane around loops you already run, plain Python, Ollama, LangGraph, whatever. You keep the body/runtime, while AURA records and optionally gates what crosses the boundary. Shouldn't this be what harness is about??
Local-first by default:
- Works offline with
agent_ref+ session IDs, no cloud identity required integrations/ollama/llama_loop.py,stdlib HTTP against Ollama (llama3.2:1bis our dev default)- Optional verified operator identity if you need it later, not required for OSS/dev
What you get on close: JSONL spine, audit report, hash chain, aura verify chain for CI.
Loose coat = audit-only logging. Tight coat = rules/gates at egress when you wire tool paths.
Open source (Python): github.com/ARPAHLS/aura
Happy to answer setup questions, especially Ollama related + “wrap my script, don’t replace it.”
Contributors more than just welcome, bunch of good first issues open <3