Agent Profiles control how your coding agents behave in different contexts.
They define what the agent can read, plan, or execute — and how much autonomy it has.
To show how profiles change workflow, we’ll build an NFL Predictor App using two profiles:
Strategic Agent
YOLO Agent
Strategic Agent
Base Model: GPT-5
Planning Model: Claude 4 Opus
Configuration:
Apply code diffs → agent decides
Read files → always allow
Create plans → always allow
Execute commands → ask first
When run:
The agent asks clarifying questions (e.g., Do you want to scrape players and schedules?)
Builds a detailed 14-step plan
Requests user input for environment variables
It’s thorough and safe — but pauses often if you miss setup details.
YOLO Agent
Configuration:
Apply code diffs → always allow
Read files → always allow
Create plans → never
Execute commands → always allow
This agent skips long planning.
It builds the project quickly, skipping over optional validation and focusing on essentials:
Data ingestion
Player stats
Scoring calculation
It avoids brittle endpoints and produces a working dataset fast — though with fewer checks.
