[potsrevennil]

PR #51 loads the agent git config through GIT_CONFIG_GLOBAL, which replaces the global config. That forced a Nix store copy at ~/.config/git-agent/config: otherwise a missing file (an older branch in the main checkout) would silently drop the whole global config, identity included. It also put an extra folder next to ~/.config/git.

This loads it as an include from the environment instead (GIT_CONFIG_COUNT=1, GIT_CONFIG_KEY_0=include.path, GIT_CONFIG_VALUE_0=~/.config/git/agent.gitconfig, set in ~/.claude/settings.json). The normal global config keeps loading. A missing file is skipped, so agents just get plain git. git config --global writes the normal config, as in a terminal. So the file stays in the version-controlled ~/.config/git folder symlink, the git-agent store copy goes, and agent.gitconfig no longer includes the normal config itself.

• Look at: include scope. An env-provided include ranks above a repo's own .git/config, so agent.gitconfig must hold only output settings, never identity or editor. That's also why the old [include] of the normal config is removed.
• Verify:

  GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=include.path GIT_CONFIG_VALUE_0=$PWD/users/home/git/agent.gitconfig git status

  GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=include.path GIT_CONFIG_VALUE_0=/nonexistent git config user.email

  The first prints short status; the second still prints your email.
• After merge: pull the main checkout (no make home needed for the file; make home removes the stale ~/.config/git-agent), then add the three env entries to ~/.claude/settings.json.

🤖 Generated with Claude Code