e780f249d1
The previous commit put .claude/settings.json IN THE REPO, which would
have applied its strict deny rules to ANY Claude Code invocation from
this cwd — including the human user's interactive dev sessions on their
own machine. That's wrong; the production agent's lockdown should not
constrain the developer.
Remove the committed file and gitignore .claude/ entirely. The repo is
permission-neutral now.
Strict permissions for the production agent come from two server-only
sources:
1. CLI flags in agent/claude_wrapper.py (--allowed-tools +
--disallowed-tools, passed by the systemd-spawned subprocess only)
2. /var/lib/overlord-agent/.claude/settings.json (the agent's own HOME
— separate from any user's .claude/)
Also bumps claude_wrapper.py with the explicit --disallowed-tools list
of meta-tools (ToolSearch, Monitor, TodoWrite, TaskOutput, Skill, cron
tools, etc.) that the --allowed-tools whitelist does not block on its
own. Verified empirically: with only --allowed-tools, ToolSearch was
still callable; --disallowed-tools is required.
11 lines
376 B
Text
11 lines
376 B
Text
.venv
|
|
__pycache__
|
|
static/v2/
|
|
frontend/node_modules/
|
|
|
|
# Claude Code config — never commit. The production agent's strict
|
|
# permissions live server-side at /var/lib/overlord-agent/.claude/
|
|
# (and via CLI flags in agent/claude_wrapper.py). The repo stays
|
|
# permission-neutral so devs can `claude` interactively here without
|
|
# inheriting production-agent restrictions.
|
|
.claude/
|