AgentChute docs
How AgentChute Works
AgentLint stays local-first. AgentChute distributes policy, receives sanitized events, and gives teams a shared control plane.
Local-first invariant#
AgentLint hook evaluation does not depend on the network. Local OSS rules and the last valid cached workspace policy run on the developer machine.
AgentChute can enrich enforcement with policy, feeds, visibility, and evidence, but it should never be required for the hook path to return a decision.
Runtime flow#
- 01A coding agent invokes a local hook.
- 02AgentLint evaluates local rules and cached workspace policy.
- 03AgentLint writes a sanitized event to a local durable queue.
- 04A background flusher uploads queued events automatically.
- 05AgentChute stores the event, policy version, decision, agent, tool, and delivery metadata.
Offline behavior#
- 01If AgentChute is down, hooks still run.
- 02If policy cache is stale, AgentLint uses stale cache.
- 03If no valid policy cache exists, cloud policy rules no-op.
- 04Events remain queued locally and upload when connectivity returns.