Its theme's rank, 14 days: 56 on the Claude Code sheet
4 people reported

All time, since Oct 10, including 2 thumbs-up on GitHub.

Sandbox leaves .git/config.lock

“error: could not lock config file .git/config”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/11713/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Sandbox leaves read-only .git/config.lock on host, blocking git config. Bubblewrap creates a 0-byte read-only placeholder at the shared git dir, so git config writes fail outside the sandbox and in sibling worktrees.

Is this your bug?

File my report
Where
Bash sandbox
Error text
error: could not lock config file .git/config
Versions
2.1.296
Platforms
Linux
How bad
Breaks a normal workflow.

Part of: Sandbox breaks git operations3 bugs

  1. Git over SSH fails in sandbox4 people
  2. Sandbox placeholder files in .git2 people

Not quite your bug?

  1. Sandbox read-only bind breaks Bash3 people
  2. Sandbox fails on symlinked paths2 people

Original reports2, newest first

  1. Sandbox leaves a real 0-byte read-only .git/config.lock on the host, breaking git config writes in the user's own terminal#102516
  2. Linux sandbox leaves a read-only .git/config.lock on the host, breaking git config writes in sibling worktrees#101155

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.