Antinel

AgentState

The public state of AI agent behaviour. Every tool call recorded, dangerous operations held, one morning report.

It runs on your machine. No cloud, no key, no network egress.

Why not cloud observability

Cloud observability

Your repo activity is uploaded; records are editable server-side; third parties cannot recompute.

Antinel

Stays local; hash chain — changes are detected; anyone with the directory can recompute every hash.

Three facts

Fact
It records behaviour, not peopleNo rankings, no scores.
It records hashes, not contentsNo file contents — only hashes and lengths. So the ledger can be shared.
It cannot undo what already happenedHooks decide before the action. What already left, it cannot bring back.

Where it stands

Scene
In your IDEdangerous calls held on the spot
Overnight runsfull trace; one morning report
Team reposthe audit block travels with the repo
CI pipelinesagent actions on the pipeline are recorded too

If your job is one of these four

RoleThe sentence you say
Security"I cannot answer what the AI did on my machine today."
Audit & compliance"Our audit system doesn't know which operations were the AI's decisions."
Legal & forensics"After an incident, can I prove which call, on whose instruction?"
Vendor management"Vendors use AI on my code; code review isn't enough."

Install

pipx install antinel antinel install # attach to your host antinel digest # first ledger

24 rules → The gate →  Limits →

Cite this page

Antinel AgentState. AgentState — the public state of AI agent behaviour. https://antinel.com/en/agentstate/ (accessed YYYY-MM-DD)

Antinel. (2026). AgentState — the public state of AI agent behaviour. AgentState. https://antinel.com/en/agentstate/

BibTeX

@misc{antinel_en_agentstate,
  title        = {AgentState — the public state of AI agent behaviour},
  author       = {{Antinel}},
  year         = {2026},
  url          = {https://antinel.com/en/agentstate/},
  note         = {claim tier: measured}
}

Claim tier: measured 采集时刻:2026-09-23T22:41:18+08:00