standard-out-setup

# Standard Out Setup

Guide for adding console output to make errors visible to agents. This is one of the most critical leverage points - without stdout visibility, agents operate blind.

## When to Use

- Agent failures with no visible error output
- Silent functions that return without logging
- New codebase setup for agentic coding
- Debugging why agents can't self-correct

## Why Standard Out Matters

Agents can only act on what they can see. If your application fails silently:

- Agent doesn't know something went wrong
- Agent can't identify the error
- Agent can't fix the issue
- Human intervention required (breaks autonomy)

**Standard out is often the missing link when agents fail.**

## The Pattern

### Before (Agent Can't See)

```python
def process_data(data):
    return transform(data)  # Silent - what happened?
```

```typescript
function processData(data) {
    return transform(data);  // Silent - success? failure?
}
```

### After (Agent Can See)

```python
def process_data(data):
    try:
        result = transform(data)
        print(f"SUCCESS: Processed {len(result)} items")
        return result
    except Exception as e:
        print(f"ERROR in process_data: {str(e)}")
        raise
```

```typescript
function processData(data) {
    try {
        const result = transform(data);
        console.log(`SUCCESS: Processed ${result.length} items`);
        return result;
    } catch (error) {
        console.error(`ERROR in processData: ${error.message}`);
        throw error;
    }
}
```

## What to Log

### Always Log

1. **Success with context**
   - What operation completed
   - How many items processed
   - What was created/modified

2. **Errors with detail**
   - What operation failed
   - The error message
   - Enough context to debug

3. **State changes**
   - Files created/modified/deleted
   - API calls made
   - Database operations

### Don't Over-Log

- Avoid logging every loop iteration
- Don't log sensitive data (passwords, tokens)
- K