Signals

2026-09-21 / Hermes Agent

The harness's own git ran repository code before the trust prompt

Edited by Michael Ruescher

Manifold Security (2026-09-01): seven agents run git to orient themselves at startup, and a repository's .git/config can set core.fsmonitor to a command git then runs as the user, outside any sandbox, before or without a prompt. Hermes fixed it in v2026.9.7 (commit f6234d00, GHSA-7x36, not yet published); every tag through v2026.8.31 is exposed. Manifold reports a second Claude Code path still reproducing on 2.1.252, and no changelog line through 2.1.278 names a fix. Codex 0.154.0 stopped running workspace helpers before a project is trusted.

What this changes for operators

  • Upgrade Hermes to v2026.9.7 or later. Open untrusted repositories only inside a container or VM; the trust prompt appears after the harness’s own git has run.
  • Before opening a repo you did not create, check .git/config for command-valued keys such as core.fsmonitor and core.hooksPath.
  • Evidence that would settle residual: a Claude Code changelog line or advisory for the second path, and Grok Build’s status (unpatched at 1.0.13 per Manifold).

Signal metadata

Source findings

Featured in

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-09-21-gitspawn-the-harness-ran-git-before-trust

Research evidence and publication history are open in the repository.