Freelancer Toolkit

Codex is a force multiplier for freelancers and solo developers. It helps you take on more projects, deliver faster, and maintain quality — all without hiring additional help. This guide covers practical Codex workflows for common freelance scenarios.

Why Codex for Freelancers#

| Challenge | How Codex Helps | |-----------|----------------| | Onboarding to new client codebases | Codebase exploration in minutes instead of days | | Handling multiple projects | Parallel agent threads in the desktop app | | Maintaining code quality solo | Automated code review before every commit | | Building features quickly | Image-to-code for UI work | | Debugging client issues | Systematic bug fixing with verification |

Setup for Freelancers#

Recommended Plan#

ChatGPT Plus ($20/mo) gives you solid Codex usage for most freelance work. If you work full-time on code, ChatGPT Pro ($200/mo) gives you higher limits and access to GPT-5.3-Codex-Spark.

Recommended Config#

# ~/.codex/config.toml
model = "gpt-5.4"
approval_policy = "on-request"
sandbox_mode = "workspace-write"
review_model = "gpt-5.3-codex"

Global AGENTS.md#

Create a ~/.codex/AGENTS.md with your standard practices:

# Freelancer Defaults

- Use conventional commit messages
- Run tests before completing any task
- Never commit .env files or API keys
- Add JSDoc comments to public functions
- Use TypeScript strict mode when available

Workflow 1: Client Project Onboarding#

When you get a new client project:

cd ~/clients/new-project
codex "Give me a complete overview of this project:
1. What it does and who it is for
2. Tech stack and frameworks
3. Project structure and key files
4. How to run it locally
5. How to run tests
6. Known issues or technical debt
7. Generate an AGENTS.md for this project"

Save the AGENTS.md output to the project root. Every future session will benefit.

Workflow 2: Pre-Commit Code Review#

Before committing any work, get a code review:

# In Codex TUI
/review
# Select "Review uncommitted changes"

Or automate it:

# Add to .git/hooks/pre-commit
codex exec "Review the staged changes. Report any bugs,
security issues, or missing error handling.
Exit with 0 if clean, 1 if issues found."

## Workflow 3: Rapid Feature Development

For a typical client feature request:

codex "Client request: Add a user settings page with:
- Profile information (name, email, avatar)
- Password change form
- Notification preferences (email, push, SMS toggles)
- Account deletion option

Use the existing project patterns. Match the style of other pages.
Add proper form validation and error handling.
Include unit tests for the settings logic."

Workflow 4: Bug Fix Turnaround#

When a client reports a bug:

codex "Client bug report: Users cannot upload files larger than 5MB.
Error message: 'Request entity too large'

Find and fix the upload size limit. Check:
1. Server-side file size configuration
2. Reverse proxy limits (nginx/apache)
3. Cloud storage upload limits
4. Client-side validation

After fixing, add a test for file uploads up to 50MB."

Workflow 5: Documentation Generation#

Generate documentation for client handoff:

codex "Generate documentation for this project:
1. README.md with setup instructions
2. API documentation for all endpoints
3. Database schema documentation
4. Deployment guide

Write for a developer who has never seen this codebase.
Use clear markdown with code examples."

Managing Multiple Projects#

Use the Codex desktop app to run agents across multiple client projects simultaneously:

1. Open project A in one thread: "Add the payment integration"
2. Open project B in another thread: "Fix the CSS layout issues"
3. Open project C for review: "Review the recent changes"

Each thread maintains its own context and sandbox.

Cost Management#

| Strategy | Impact | |----------|--------| | Use GPT-5.4 for complex tasks | Best quality, moderate cost | | Switch to GPT-5.1-Codex-Mini for simple tasks | Lower cost, still capable | | Use codex exec for repeatable tasks | Efficient, no TUI overhead | | Batch similar work | One session handles multiple related changes |

## Next Steps

• Codebase Onboarding — Deep dive on project exploration
• Bug Fixing — Systematic debugging
• Code Review — Automated quality checks
• Comparisons — See how Codex compares to alternatives