Codex Accounts

You're using a Codex account (not API) and manually checking if generated code works by copy-pasting into your editor.

Execution steps: Codex accounts include the full sandbox environment. Instead of copying code out, use the built-in execution:

1. Write your test file directly in the Codex interface
2. Ask Codex to implement the function and run the tests in the same session
3. Codex iterates automatically until tests pass

<code class="language-python"># In your Codex session, paste this first:
def test_parse_csv():
result = parse_csv("name,age\nAlice,30")
assert result == [{&quot;name&quot;: "Alice", "age": "30"}]

# Then prompt: "Implement parse_csv to pass the test above.
# Run the test and fix any failures."</code></pre>

The account-level advantage over API: you get persistent session state, so Codex remembers previous iterations. With the API, each call is stateless and you manage the test loop yourself.

This workflow turns Codex into a TDD partner — define what "correct" means upfront, then let it iterate.

Every new Codex session starts from scratch — you re-explain your project, coding style, and constraints each time.

What to do next: Codex accounts support persistent system-level configuration. Set up a pinned context at the account level:

1. Go to your Codex account settings
2. Add a system prompt or project configuration that loads automatically
3. Include your standard conventions:

<code class="language-markdown"># Default Context

## Stack
- Python 3.12 + FastAPI + SQLAlchemy 2.0
- Always use async/await
- Type hints required on all functions

## Rules
- Never use print() for logging — use structlog
- All database queries must use parameterized statements
- Error responses follow RFC 7807 format

## Testing
- pytest with pytest-asyncio
- 100% coverage on business logic modules</code></pre>

The difference from API-level AGENTS.md: account-level configuration persists across all sessions automatically. With the API, you'd need to inject the context into every request programmatically. The account gives you a GUI-based "set and forget" approach.

Update this monthly as your project evolves.

Issue:
Shared Codex account usage becomes unstable when multiple teams reuse one browser context.

What to do:
1. Separate each operator into independent browser profiles.
2. Keep recovery and security ownership clearly assigned.
3. Run a short access check before each working session.

Result:
Session conflicts are reduced and daily access remains predictable.

Symptom:
Codex account access fails for some team members but not others.

Fix path:
1. Separate team usage by browser profile and credential owner.
2. Revalidate security methods and recovery ownership.
3. Run a short login check before each shared session.

Expected outcome:
Cross user session conflicts drop significantly.