# Example: Restricting filesystem access
# For terminal agents, use a dedicated workspace

$ mkdir ~/secure-workspace
$ cd ~/secure-workspace
$ git clone https://github.com/your/project.git

# Set restrictive permissions
$ chmod 700 ~/.ssh  # Protect SSH keys
$ chmod 600 ~/.env  # Protect environment files

# For Claude Code, use project-scoped configuration
# .claude/settings.json:
{
    "allowedDirectories": ["./"],
    "blockedPaths": [
        "~/.ssh",
        "~/.aws",
        "~/.env*"
    ]
}

# Example: Safe Git workflow with AI agent

# 1. Agent creates changes
$ git diff  # Review what changed

# 2. You review the diff
$ git diff --stat  # See affected files
$ git diff src/  # Review actual changes

# 3. You approve and commit
$ git add -A
$ git commit -m "Fix: Resolve auth bug (agent-assisted)"

# 4. Never auto-push
$ git push  # Only after you review

# Protection rules:
# - Branch protection on main/master
# - Required PR reviews
# - Status checks before merge

# Example: Secure secrets configuration
# BAD: Exposing all environment variables
$ export $(cat .env)  # Agent gets everything

# BETTER: Scoped secrets
$ export API_KEY="limited-scope-key"
$ export DATABASE_URL=""  # Don't expose DB credentials

# BEST: Use secret manager with scoped access
$ vault read -field=key secret/agent/api-key

# For Claude Code, use project-level .env
# with only necessary secrets

# Example: Sandboxed agent environment
# Docker container with restricted capabilities

$ docker run --rm -it \
    --name agent-sandbox \
    --network none \  # No network access
    --read-only \  # Read-only filesystem
    --memory 512m \  # Memory limit
    --cpus 1.0 \  # CPU limit
    --user 1000:1000 \  # Non-root user
    -v $(pwd):/workspace:ro \  # Read-only mount
    python:3.12-slim

# Agent runs in sandbox with minimal access