Training course · OpenAI Codex · Software Architecture
OpenAI Codex for Software Architects
Delegate development work with OpenAI Codex: CLI and cloud agent, AGENTS.md, sandboxing, approvals and team PR workflows.
- Duration
- 2 days (14 hrs)
- Format
- Online or on-site
- Language
- German or English
- Participants
- open dates or exclusive for your team
- Certificate
- Certificate of attendance
Overview
This course connects OpenAI Codex with the everyday processes of Software Architecture. Participants work on realistic scenarios and leave with prompts, workflows and checklists they can use straight away.
OpenAI Codex is a coding agent that runs both locally, as a command-line tool and IDE extension, and as a cloud agent. Locally, Codex reads your repository, proposes changes and runs commands inside a sandboxed environment. In the cloud, it works on delegated tasks in parallel inside isolated containers and returns results as traceable diffs or pull requests. Over two days you will learn how to combine both modes effectively and how to scope tasks so that the agent can complete them reliably and with minimal back-and-forth.
Control and security sit at the heart of the course. With AGENTS.md you hand Codex project knowledge, build and test commands, and conventions. You configure approval modes and sandboxing so that the agent only does what you permit, and you set up cloud environments with suitable setup scripts. You will also integrate Codex into your pull request workflows, use automated code review, and define team rules on which tasks are delegated and how results are checked before they are merged into the main branch.
When AI agents write large parts of the code, architecture becomes more important, not less: clear module boundaries, documented decisions and verifiable quality goals are the frame that keeps generated code consistent. AI assistants also support architects directly, for example by analysing existing codebases, producing C4 diagrams, drafting architecture decision records and weighing alternatives against quality attributes. Fitness functions and architecture tests can be generated and anchored in your pipelines. In this course you learn to use AI as a sparring partner for architectural decisions, prepare architectural knowledge so that coding agents follow it reliably and spot erosion early in fast-growing codebases.
The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.
Who is this course for?
- Software architects and solution architects
- Enterprise architects with links to application development
- Senior developers and tech leads with architectural responsibility
- Platform and cloud architects
- Owners of architecture governance and review boards
Typical challenges we address
- Architecture documentation goes stale quickly and drifts from the actual code
- Decisions are made verbally and their context is lost
- Gradual architectural erosion through cyclic dependencies and violated layer boundaries
- Without clear guidance, AI-generated code ignores established patterns and conventions
What you will be able to do
- You use Codex locally and in the cloud for the development tasks each mode suits best.
- You write an AGENTS.md that guides the agent reliably through your project.
- You configure approval modes and sandboxing to match your security requirements.
- You delegate tasks to the cloud agent and review the results systematically.
- Use AI to analyse existing systems, evaluate architectural options and record decisions as ADRs.
- Anchor architecture rules as fitness functions in the pipeline and detect erosion early.
- Shape context and rules so that AI coding agents reliably respect your architectural guidelines.
Course outline
Day 1
Module 1 Codex at a glance: CLI, IDE and cloud
- Comparing how Codex works locally and in the cloud
- Installing the Codex CLI, signing in and starting it in a repository
- Interactive sessions, non-interactive execution and model choice
- Distinguishing tasks that suit a coding agent from those that do not
Module 2 Project knowledge with AGENTS.md
- Building an AGENTS.md with build, test and lint commands
- Stating conventions, architectural notes and prohibitions precisely
- Using nested AGENTS.md files for monorepos and sub-projects
- Checking effectiveness and refining instructions iteratively
Module 3 Sandboxing, approvals and security
- Choosing approval modes deliberately, from read-only to largely autonomous
- Understanding sandbox boundaries for file system and network access
- Handling secrets, dependencies from the internet and prompt injection
- Configuration files for team standards and safe defaults
Module 4 Delegating tasks to the cloud agent
- Configuring cloud environments with setup scripts and dependencies
- Writing tasks with a clear goal, context and acceptance criteria
- Launching several tasks in parallel and comparing the results
- Using logs and test output to understand the proposed solutions
Day 2
Module 5 PR workflows and code review in the team
- Turning results into pull requests and requesting follow-up changes
- Using automated Codex code review on GitHub
- Embedding Codex in scripts and CI pipelines
- Setting team rules for delegation, review duties and accountability
Module 6 Practice lab: Software Architecture
- Documenting architecture decisions
- Reconstructing existing architecture
- Evaluating alternatives
- Generating fitness functions
- Guardrails for coding agents
- Carving out domains
Module 7 Data protection, quality & transfer to daily work
- Architecture documents often describe security-relevant details such as network zones and data flows: you learn which information may be shared with AI services, how to assess licensing risks of components and how architectural decisions traceably reflect GDPR, NIS2 and Cyber Resilience Act requirements.
- Ground rules for safe AI use in your team
- Checking results: facts, sources, tests and the four-eyes principle
- Personal action plan for the next 30 days
- Open questions, outlook and resources for further learning
Practical scenarios from your field
Documenting architecture decisions
Turn discussions, meeting notes and pull requests into structured architecture decision records with context, options considered, decision and consequences, stored consistently in the repository. Related decisions are linked automatically.
Reconstructing existing architecture
Analyse existing codebases, extract modules, dependencies and interfaces and generate up-to-date C4 diagrams as diagrams-as-code with PlantUML, Mermaid or Structurizr. Diagrams can be refreshed automatically on every build.
Evaluating alternatives
Compare options such as a modular monolith, microservices or event-driven integration against quality scenarios, cost and team structure, and make trade-offs visible following ATAM principles.
Generating fitness functions
Express architecture rules such as layer access, forbidden dependencies or naming conventions as automated tests with ArchUnit, dependency-cruiser or similar tools and wire them into CI.
Guardrails for coding agents
Describe architectural principles, module boundaries and patterns in rule files and context documents so AI agents follow them reliably when generating code, and spot deviations in review.
Carving out domains
Derive bounded contexts, aggregates and context maps following domain-driven design from event storming results and business descriptions, and use them to shape teams and services.
Possible hands-on projects
ADR assistant
A command-line tool that turns bullet points into a complete ADR from a template, links related decisions and updates an index in the repository.
Dependency visualiser
A script that analyses import relationships in a codebase, flags cycles and layer violations and renders an interactive diagram in the browser.
Architecture Q&A over repos
A small application that indexes ADRs, diagrams and code and answers architecture questions with references to the underlying sources. New team members onboard faster.
Prerequisites
You have hands-on programming experience, are comfortable with Git and the command line, and know pull-request-based workflows. You have several years of development experience and have made or supported architectural decisions in larger software systems.
Technical requirements
Your own laptop with a terminal, Git and a Node.js runtime; a ChatGPT plan with Codex access or an OpenAI API key, plus a GitHub account for the cloud exercises.
Data protection & compliance
Architecture documents often describe security-relevant details such as network zones and data flows: you learn which information may be shared with AI services, how to assess licensing risks of components and how architectural decisions traceably reflect GDPR, NIS2 and Cyber Resilience Act requirements.
Suggested dates
All dates are suggestions – your preferred date is always possible.
- Tue, 24 November 2026 – Wed, 25 November 2026 Online Request
- Wed, 2 December 2026 – Thu, 3 December 2026 Hanover Request
- Thu, 17 December 2026 – Fri, 18 December 2026 Online Request
- Tue, 19 January 2027 – Wed, 20 January 2027 Munich Request
- Tue, 2 February 2027 – Wed, 3 February 2027 Online Request
- Wed, 10 February 2027 – Thu, 11 February 2027 Stuttgart Request
Frequently asked questions
When should I use Codex locally and when in the cloud?
Locally you work interactively and close to the code, for example when debugging or making exploratory changes where you want to follow every step. The cloud agent suits well-defined tasks that can run independently, such as adding tests or fixing smaller bugs. You can start several of these in parallel and review each one as a pull request.
What belongs in a good AGENTS.md?
A good AGENTS.md explains how the project is built, tested and checked, which conventions apply and which areas must not be touched. It is concise, concrete and kept up to date. Notes on architecture and common pitfalls also help. During the course you write an AGENTS.md for a project of your own and test how it changes the agent’s behaviour.
How safe is it to let Codex run commands?
By default Codex works inside a sandbox with restricted file and network access and asks for approval before risky steps. You decide how much autonomy to grant through approval modes and configuration. In the course you learn to choose these settings deliberately and to limit risks such as prompt injection or running unfamiliar dependencies.
Can AI make architecture decisions?
AI is a strong sparring partner: it offers options, names trade-offs, finds gaps in reasoning and documents decisions in a structured way. Responsibility stays with people, because architecture depends on business context, team skills, budget and risk appetite. In the course you learn to use AI so that decisions are better reasoned and made faster.
How do we stop AI agents from eroding the architecture?
Through a combination of clear context and automated checks: rule files and ADRs describe module boundaries and patterns, fitness functions and architecture tests in CI block violations, and reviews focus on structural changes. Architecture thus turns from documentation into a verifiable guardrail for humans and agents alike.
How much does “OpenAI Codex for Software Architects” cost?
The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.
Can I suggest my own date?
Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.
Is the course online or on-site?
Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.
More courses for Software Architects
- Claude Code for Software Architects
- Vibe Coding for Software Architects
- Agentic Coding for Software Architects
- Cursor for Software Architects
- GitHub Copilot for Software Architects
- Windsurf for Software Architects
- Model Context Protocol (MCP) for Software Architects
- AI Agent Development for Software Architects
- RAG & LLM Applications for Software Architects
More OpenAI Codex courses
- OpenAI Codex for Startups and MVP Development
- OpenAI Codex for Mobile Developers
- OpenAI Codex for Node.js Back-End Developers
- OpenAI Codex for PHP Developers
- OpenAI Codex for Python Developers
- OpenAI Codex for React and Front-End Developers
- OpenAI Codex for Rust Developers
- OpenAI Codex for SAP ABAP Developers
- OpenAI Codex for SQL and Database Professionals
- OpenAI Codex for Salesforce Developers
- OpenAI Codex for Security and DevSecOps Teams
- OpenAI Codex for Game Developers
OpenAI Codex · MunichOpenAI Codex · SalzburgOpenAI Codex · BerlinOpenAI Codex · AugsburgOpenAI Codex · HanoverOpenAI Codex · BremenOpenAI Codex · StuttgartOpenAI Codex · KaiserslauternOpenAI Codex · Online