Skip to main content

Agentic Coding Workshops in Germany, in English and German

By the OnlineAppCreator editorial team4 min read

Short answer

Agentic coding workshops for German companies need the same technical content as anywhere else, plus three local preparations: a data protection check of the AI tools under GDPR, early involvement of the works council where one exists, and a deliberate choice of training language. Workshops can run in English or German, on-site in Germany or remotely across the DACH region.

On this page
  1. Language: English, German or both
  2. Data protection and tool approval
  3. Involving the works council early
  4. On-site in Germany or remote across DACH
  5. Preparation checklist for German companies
  6. What the content looks like
  7. A workshop partner based in Germany

German companies adopting agentic coding tools like Claude Code, OpenAI Codex or Cursor face the same technical learning curve as teams elsewhere. What differs is the surrounding framework: GDPR expectations, co-determination rights of works councils, procurement habits and teams that often work in a mix of German and English. A workshop that ignores these factors may be technically excellent and still stall in the rollout. This article covers what to prepare when organising agentic coding training in Germany.

Language: English, German or both

Most development teams in Germany read documentation and write code comments in English, and many international teams use English as their working language. At the same time, discussions about team rules, quality expectations and concerns are often more open in the native language. A practical approach is to run the workshop in the language the team uses in meetings, while keeping prompts, context files and code in English. Agents handle German prompts well, but English context files make repositories easier to share with external partners and keep terminology consistent with the tools' documentation.

For mixed teams, a bilingual format works: slides and exercises in English, discussion in whichever language the group prefers. Clarify this when booking so the trainer can prepare examples accordingly.

Data protection and tool approval

Before a workshop runs on real code, the data protection officer and information security team should have reviewed the tools. The relevant questions are which data is sent to the AI provider, where it is processed, whether a data processing agreement is in place, whether inputs may be used for model training and which retention periods apply. Business plans of the major providers usually address these points, but terms change, so the review should use the current versions. For background on the legal side, see our article on GDPR compliance for AI-built apps.

Source code itself is rarely personal data, but repositories often contain test fixtures, logs or configuration with personal or confidential information. A pre-workshop cleanup, or a sanitised training copy of the repository, avoids awkward questions later.

Involving the works council early

In companies with a works council (Betriebsrat), the introduction of software that could monitor employee behaviour or performance is generally subject to co-determination. Agentic coding tools log usage, and some dashboards show activity per user. Even if the company has no intention of using that data for performance assessment, it is wise to involve the works council early, explain the purpose of the training and the tools, and clarify how usage data will and will not be used. Many companies handle this with a short agreement or an addendum to an existing IT framework agreement. This is not legal advice; your HR and legal teams will know the specific requirements.

Inviting a works council member to observe part of the workshop often builds trust faster than written explanations.

On-site in Germany or remote across DACH

German teams often prefer on-site workshops for kick-offs, especially when several departments need to align. Remote formats work well for distributed teams across Germany, Austria and Switzerland and for follow-up sessions. Our comparison of on-site and remote AI coding workshops covers the trade-offs in detail. For public sector organisations, procurement rules and additional security requirements usually apply; see agentic coding training for public sector IT teams.

Preparation checklist for German companies

  1. Confirm which tools and plans are approved, and that data processing agreements are signed.
  2. Inform or involve the works council and document how usage data will be handled.
  3. Decide the training language and whether context files and prompts stay in English.
  4. Prepare a repository copy without personal data, secrets or confidential customer information.
  5. Check that corporate proxies and firewalls allow the tools to reach their services.
  6. Agree on a follow-up date and an internal owner for the shared agent configuration.

What the content looks like

The technical curriculum itself is international: context engineering with CLAUDE.md or AGENTS.md, task design, verification with tests, security guardrails and team workflows. German teams often place extra weight on documentation, traceability of changes and quality management. These fit naturally into agentic workflows: agents can write change summaries, pull request descriptions and test documentation that support audits, as long as humans review them. ISO 9001 or ISO 27001 environments benefit from defining early how agent-generated changes are documented: for example, a label on pull requests, a note in the commit message or a reference to the task brief. That traceability makes later audits straightforward and answers the frequent question of who is responsible for code an agent wrote: the developer who reviewed and merged it.

A workshop partner based in Germany

neooutput and OnlineAppCreator are ventures of jocapps GmbH, which is based in Freiburg, Germany, has been building digital products since 2014 and is ISO 9001 certified. We build and launch digital products with agentic workflows and teach the same methods. Our agentic coding workshops at neooutput run in English or German, on-site or remote, for Claude Code, OpenAI Codex and Cursor. Teams that also need delivery capacity can work with our AI Code Engineers through OnlineAppCreator custom development and company building.

Frequently asked questions

Can the workshop be held entirely in German?

Yes. Discussions, explanations and materials can be in German, while code, prompts and context files usually stay in English for consistency with the tools and documentation.

Does introducing AI coding tools require works council approval in Germany?

Where a works council exists, introducing software that can monitor behaviour or performance is generally subject to co-determination. Check the specific requirements with your HR and legal teams before the rollout.

Is it allowed to use AI coding tools with company code under GDPR?

Often yes, provided the provider's terms, data processing agreement and data flows have been reviewed and personal data in repositories is handled appropriately. Your data protection officer should confirm this for your setup.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.