Abhed documentation

Abhed is a deep agent harness. It runs where your code is, against whichever model you point it at, and records everything it does.

Guide

Using Abhed day to day.

Getting startedAbhed is a single static binary with no runtime to install.ConfigurationAbhed reads `.abhed/config.json` from the workspace. `abhed init` writes a starter file; everything below is optional and has a default.Models and providersAbhed does not ship a model. It is model-agnostic by construction: the harness is the same whichever endpoint you point it at, and a better model makePermissions and safetyAn agent that can run shell commands in your repository needs a real answer to "what is it allowed to do". Abhed's answer is a policy engine that deciToolsFour routes, none of which needs a rebuild. Pick by where your tool already lives.SkillsA skill is a procedure Abhed should follow when a request matches it: how your team cuts a release, the checklist for a schema migration, the house foExtensionsAn extension changes how the agent behaves without forking it. Extensions are separate processes speaking line-delimited JSON on stdin and stdout, so MCPAbhed is an MCP client and gateway. A tool exposed by a Model Context Protocol server appears in the model's tool list like any built-in one.The SDKAbhed's internals live under `internal/`, which Go refuses to let another module import. The `sdk` package is the supported surface across that wall, AutomationThree ways to run Abhed without a person at the prompt.Sessions and auditAbhed's state is a chronological stream of events. The agent is a function from that history to an action, and the runtime is a function from an actioObservabilityEvery session is already an ordered log of events — that is the audit trail, and it is the source of truth. Observability is the same facts in the shaStructured outputA program embedding Abhed usually does not want prose. It wants a value: a verdict, a list of findings, a record it can store. `RunJSON` runs a promptParallel subagents and worktree isolationThe `task` tool runs one subagent and waits. The `tasks` tool runs several at once. The agent chooses it when subtasks are independent — investigate tScheduled runsA recurring run is the shape of a lot of real work: every weekday at nine, summarise what changed overnight; hourly, check the staging pods; Sunday ni

Architecture

How it is built, and why.

Operations

Running it in a real environment.

Trust

What a security review will ask, answered from the code.

Benchmarks

Measured, reproducible, published whatever they say.