Historical snapshot · September 2026 / v0.3.0 This preserved page is an archive, not a current capability or security claim. The crate graph has not been updated to v0.9.1. View the current development status → HARW / 0.3.0 THE LOCAL AGENT RUNTIME
Let agents think.Keep authority. A Rust runtime for agents that research, plan, and work. Explicit permissions. Durable state. You in control.
THE EXECUTION BOUNDARY 01 / RUNTIME
λ MODEL Propose an intent
untrusted tool call
HARW AUTHORITY BOUNDARY ⌑
01 Resolve authority typed context
02 Check policy scope + approval
03 Admit execution bounded effect
only if permitted
Filesystem Process Network
PROMPTS ARE INPUT. PERMISSIONS ARE CODE.
01 Authority is derived 02 Privileges only narrow 03 Work survives the turn 04 Evidence stays traceable
A HARNESS WITH A POINT OF VIEW
More than an agent loop. The model proposes the next step. Harwness owns the contracts, context, and execution that make it real.
01 / GOVERNED WORK Agents with a contract. Compile layered TOML definitions into executable, content-addressed agent snapshots. Give each role a tool surface, a budget, and a return contract.
[tools] admitted = ["fs.read", "fs.search"] forbidden = ["fs.write", "shell.exec"] [spawn.budget] max_tool_calls = 40
Understand agent definitions ↗ 02 / CONTINUITY Work that remembers where it was going. Goals, plan graphs, findings, transcripts, and jobs have a life beyond a single context window. Leases, budgets, and cancellation give background work explicit limits.
✓ Explore the workspace
✓ Attach research evidence
03 Execute a scoped plan node
04 Verify against the goal
Illustrative plan 03 / CONTEXT & LENS The right evidence. Within the right scope. Typed context distinguishes instructions from evidence. Lens combines chunking, vector and lexical search, ranking, and visibility checks across local indices.
Source provenance BM25 + vectors Budgeted context Scoped retrieval
Inside Lens ↗
DoD / THE HOST SECURITY PLANE
Detect. Orient.Defend. Observe host activity. Turn signals into evidenced findings. Keep privileged responses behind a separate authorization boundary.
Follow the security pipeline ↗ D Detect Scoped sensors for host resources, workspace drift, scanner reports, filesystem events, and eBPF signals.
SENSORS → TYPED SIGNALS O Orient Rules, baselines, evidence, and triage turn observations into findings. A model verdict is a proposal.
RULE-CHECKED → TRIAGED D Defend A separate Warden checks authorization proofs before dispatching privileged host actions.
AUTHORIZED → ENFORCED Optional Linux subsystem · separate Cargo workspace · host setup required
ONE RUNTIME, DISTINCT ENTRY POINTS
Choose your surface. Keep the boundary. Different entry points receive different capabilities. Connecting a channel does not grant it your local terminal’s authority.
>_ Terminal & CLI Interactive sessions, one-shot work, workspace analysis, setup, and operator approvals.
Local operator { } Rust SDK Compose typed providers, extensions, plans, and sessions through the harw facade.
Embeddable ⌘ MCP & Telegram Durable MCP job submission and opt-in paired Telegram ingress, with restricted runtime profiles.
Explicit admission ▤ Local control plane Expose governed operations over a Unix socket with peer identity checks. Web UI coverage is evolving.
Scoped operations
BUILT FROM THE FOUNDATIONS UP
Every crate has a role. Every boundary has an owner. Explore the packages, their dependencies, and the consumers that connect the system.
Explore 101 packages → 68 Product workspace packages
32 DoD workspace packages
01 Separate mobile policy core
EARLY BY DESIGN. EXPLICIT ABOUT IT. Build with the boundaries in view. Harwness 0.3.0 is in active development. Start locally, inspect the architecture, and expect APIs to evolve.
Read the documentation ↗