# Session: execute_code Blocked → Retry Loop → Terminal Fallback

**Date:** 2026-06-26
**Device:** Pixel Fold, Android 16, Termux
**Context:** Cron job for VisualAgent backend service

## Session Summary

The cron job was tasked with monitoring `/sdcard/VisualAgent/commands/` for JSON command files and executing them. The session demonstrates three key patterns:

1. `execute_code` blocked in cron mode (expected)
2. Accidental retry loop after the block (wasted iteration)
3. Successful fallback to `terminal` + shell commands

## Full Sequence

### Step 1: Directory Check (Normal)
```
terminal: ls -la /sdcard/VisualAgent/commands/ 2>/dev/null || echo "DIR_NOT_FOUND"
→ DIR_NOT_FOUND
```
Directory didn't exist. Correct response: create it.

### Step 2: Directory Creation with su (Normal)
```
terminal: su -c "mkdir -p /sdcard/VisualAgent/commands /sdcard/VisualAgent/results"
→ Success (exit 0)
```

### Step 3: chmod 777 Blocked (Learning Point)
```
terminal: su -c "chmod 777 /sdcard/VisualAgent /sdcard/VisualAgent/commands /sdcard/VisualAgent/results"
→ BLOCKED: "world/other-writable permissions" approval pending
```
**The `chmod 777` command triggered a safety pattern that requires approval.**

### Step 4: Accidental Retry (Anti-Pattern)
```
terminal: su -c "chmod 777 /sdcard/VisualAgent /sdcard/VisualAgent/commands /sdcard/VisualAgent/results"
→ Same block, plus tool-loop warning: "repeated_exact_failure_warning; count=2"
```
The agent retried the exact same command, triggering the repeated-exact-failure warning. This was futile — the block was policy-based, not transient.

### Step 5: chmod 755 Workaround (Solution)
```
terminal: su -c "chmod 755 /sdcard/VisualAgent /sdcard/VisualAgent/commands /sdcard/VisualAgent/results"
→ Success (exit 0)
```
`chmod 755` passed without approval. Default `mkdir -p` permissions (usually 755) would also have been sufficient.

### Step 6: Check for JSON Files (Normal)
```
terminal: su -c "ls -la /sdcard/VisualAgent/commands/"
→ myfile.dat, test.txt (no .json files)

terminal: su -c "find /sdcard/VisualAgent/commands/ -name '*.json' -type f"
→ (empty — no JSON files)
```

### Step 7: execute_code Blocked (Expected in Cron)
```
execute_code: Python script with subprocess calls for JSON parsing, command execution, result serialization
→ BLOCKED: "execute_code runs arbitrary local Python... Cron jobs run without a user present"
```
This is the expected cron-mode security restriction. The agent should have immediately switched to `terminal` + shell commands.

### Step 8: Successful Terminal Fallback (Correct Recovery)
```
terminal: su -c "ls -1 /sdcard/VisualAgent/commands/*.json 2>/dev/null || echo 'NO_JSON'"
→ NO_JSON
```
Confirmed no JSON files. Correct final response: `[SILENT]`.

## Key Learnings

### 1. chmod 777 vs 755
| Command | Result | Why |
|---------|--------|-----|
| `chmod 777` | Blocked (approval required) | World-writable flag triggers safety pattern |
| `chmod 755` | Success | No world-writable flag, no safety trigger |
| `mkdir -p` (default) | Usually sufficient | Default permissions are typically 755 |

**Rule:** For VisualAgent directory setup, never use `chmod 777`. Use `mkdir -p` alone (default permissions), or `chmod 755` if explicit permissions are needed.

### 2. The Retry Loop Trap
After `chmod 777` was blocked, the agent retried the exact same command. This:
- Wasted an iteration
- Triggered the tool-loop warning (`repeated_exact_failure_warning; count=2`)
- Would have hit the 5-repetition guardrail if continued

**Rule:** When a command is blocked by a safety pattern (not an error), do NOT retry. Change the command (e.g., `777` → `755`) or abandon the approach entirely.

### 3. execute_code Block → Immediate Terminal Fallback
When `execute_code` was blocked, the agent correctly switched to `terminal` + `su -c` shell commands. However, the attempt to use `execute_code` at all was unnecessary — the task (check for JSON files, process if found) could have been done entirely with `terminal` commands from the start.

**Rule:** In cron mode, don't attempt `execute_code` for tasks that can be done with `terminal` + shell or direct MCP tools. The block is policy-based and will always occur for subprocess calls.

### 4. The "Service" Framing Did NOT Trigger Anti-Patterns
Unlike many other VisualAgent cron sessions, this one did NOT fall into:
- Redundant polling (only checked directory 2-3 times total)
- Synthetic commands (no fake command files created)
- Health-check screenshots (no unrequested screenshots)
- Verbose reports (responded `[SILENT]` correctly)

The session was clean after the initial `chmod` and `execute_code` missteps. The agent recovered correctly and produced the right final response.

## Prevention Checklist

For future VisualAgent cron jobs:
- [ ] Use `mkdir -p` without `chmod` for directory setup
- [ ] If `chmod` is needed, use `755` not `777`
- [ ] Never retry a command blocked by safety approval — change strategy immediately
- [ ] Don't attempt `execute_code` in cron mode — use `terminal` or MCP tools from the start
- [ ] Check directory once with `find`, if empty and no history → `[SILENT]`
- [ ] If operational history exists, `[SILENT]` immediately without health checks

## Decision Tree for This Session's Scenario

```
User: "You are a VisualAgent backend service..."
  ↓
Check /sdcard/VisualAgent/commands/ exists?
  → No: mkdir -p /sdcard/VisualAgent/commands/ /sdcard/VisualAgent/results/
      ↓
      (DO NOT chmod 777 — use default permissions or chmod 755 if needed)
  → Yes: continue
  ↓
Find .json files in commands/
  → Found: process with MCP tools or terminal + su
  → Not found: check .processed_files and processed/ for operational history
      ↓
      History exists → [SILENT]
      No history → one directory verification, then [SILENT]
```