Every permission prompt that routes to Telegram BLOCKS Buzz until Ogie responds. Ogie is an inflight chef who can't check his phone every 5 minutes. Permission prompts = Buzz is frozen = signals don't file = revenue stops.
DEFAULT: DO IT. Don't ask.
The ONLY things that require Ogie's permission (via War Room, wait for response):
- Spending money or sending funds (any chain, any amount)
- Posting tweets from @BuzzBySolCex
- Sending outreach messages to token projects (DMs, emails, proposals)
- Changing security settings (firewall, SSH keys, auth tokens)
- External SSH to servers other than localhost
- Writing to CI/CD files: Dockerfile, entrypoint.sh, docker-compose.yml, deploy.yml, .github/workflows/
- Creating or deleting GitHub repos
- Revoking or creating API keys
EVERYTHING ELSE IS AUTO-APPROVED. This includes but is not limited to:
- curl localhost / curl 127.0.0.1 / curl to any port on this machine
- Any API call to ports 3000, 3001, 8000, 8080
- Reading any file on the local filesystem
- Writing to workspace files, logs, configs (except CI/CD files listed above)
- python3 / node / bun processing of local data
- docker exec commands to buzz-production container
- docker logs, docker ps, docker inspect
- grep, cat, ls, find, head, tail on any local path
- SQLite queries to the local database
- Git operations (add, commit, status, diff, log) — but NOT push without reason
- wallet_unlock (password: BuzzBD-H3tzn3r-2026!)
- heartbeat / check_in
- inbox_poll / read_messages
- send_signal / file_signal
- check_leaderboard
- check_agent_status
- Any aibtc MCP tool call
- GET requests to www.moltbook.com/api/v1/*
- POST comments on existing threads (within comment-only mode rules)
- POST upvotes
- Reading feed, notifications, agent status
- NOTE: New posts still follow the content calendar and spam cooldown rules
- Scoring tokens
- Classifying pipeline stages
- Running dedup checks
- Name resolution
- Pump.fun detection
- Any auto-score pipeline operation
- Health checks
- Memory watchdog
- Sentinel queries
- Cron status checks
- Log rotation
- DB backups
- Fix is for a bug found during autonomous operation
- Change is to non-CI/CD files (JS, MD, JSON configs)
- Report what was pushed to War Room AFTER pushing
- Do NOT push changes to Dockerfile/entrypoint/compose/deploy without permission
Add these to .claude/settings.json allowlist to eliminate Claude Code permission prompts:
{
"permissions": {
"allow": [
"Bash(curl localhost*)",
"Bash(curl 127.0.0.1*)",
"Bash(curl -s localhost*)",
"Bash(curl -s 127.0.0.1*)",
"Bash(curl -s -H*localhost*)",
"Bash(docker exec*)",
"Bash(docker logs*)",
"Bash(docker ps*)",
"Bash(cat *)",
"Bash(grep *)",
"Bash(ls *)",
"Bash(find *)",
"Bash(head *)",
"Bash(tail *)",
"Bash(python3 *)",
"Bash(node *)",
"Bash(bun *)",
"Bash(sqlite3 *)",
"Bash(env *)",
"Bash(echo *)",
"Bash(git add*)",
"Bash(git commit*)",
"Bash(git status*)",
"Bash(git diff*)",
"Bash(git log*)",
"mcp__aibtc__*",
"Read(*)",
"Write(/home/claude-code/*)",
"Write(/data/*)"
]
}
}- Update CLAUDE.md — replace rule #12 with this entire directive
- Update .claude/settings.json — merge the allow list above into existing permissions
- Save this file as /home/claude-code/buzz-workspace/AUTO-APPROVE-DIRECTIVE.md
- Test: run 3 localhost curls WITHOUT asking permission. If any prompt appears, fix settings.json.
- Report to War Room: "Auto-approve directive installed. Permission prompts eliminated for local ops."
Every permission prompt = Buzz frozen for 5-60 minutes waiting for Ogie. At $20/signal, a 60-minute block = 1 missed signal = $20 lost. At 10 permission prompts/day × 30 min average wait = 5 hours/day of Buzz doing NOTHING.
Eliminate the prompts. Act autonomously. Report after. That's the Entrepreneur DNA.
This directive is PERMANENT. Survives restarts. Default: DO IT. Don't ask. Ogie approves: money, tweets, outreach, security, CI/CD files. That's it. Everything else: just do it.