Training course · Agentic Coding · Rust

Agentic Coding for Rust Developers

Use autonomous coding agents effectively: specs instead of prompts, task decomposition, test-driven loops, multi-agent setups and governance.

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 Agentic Coding with the everyday processes of Rust. Participants work on realistic scenarios and leave with prompts, workflows and checklists they can use straight away.

Agentic coding means working with AI agents that carry out development tasks largely on their own: they read code, plan changes, run commands and tests, and correct themselves based on the results. Tools such as Claude Code, OpenAI Codex, the GitHub Copilot coding agent and Cursor’s agent mode have made this way of working practical for everyday use. This vendor-neutral course teaches the underlying methodology so that you achieve reliable results whatever the tool, and redefine the developer’s role within your engineering team.

The core shift is from ad hoc prompts to robust specifications. You will learn to decompose and describe tasks so that agents solve them reliably, to set up test-driven loops in which tests act as objective acceptance criteria, and to run several agents in parallel or with a division of labour. We also cover review strategies for agent-generated code and team governance: permissions, security boundaries, accountability, cost control and the gradual introduction of agentic workflows into your existing development processes.

Rust is gaining ground wherever memory safety and performance have to go hand in hand: in systems software, embedded projects, network services, WebAssembly and security-critical components. The learning curve is steep – ownership, lifetimes, traits and async runtimes challenge even experienced developers. AI coding assistants and agents prove to be patient sparring partners here: they explain borrow checker errors, suggest suitable ownership structures, write tests and property-based tests, port C or C++ modules incrementally and work through Clippy lints. Because the compiler gives very precise feedback, agents can iterate all the way to compiling, safe code. This course teaches you to exploit that feedback loop and to scrutinise unsafe code with particular care.

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?

  • Rust developers working on systems and back-end projects
  • C and C++ developers moving to Rust or porting modules
  • Embedded and IoT developers using Rust
  • Security and platform teams focused on memory safety

Typical challenges we address

  • Hard-to-understand borrow checker and lifetime errors
  • Complex trait hierarchies, generics and async code with Tokio
  • Laborious porting of existing C or C++ codebases across FFI boundaries
  • Handling unsafe blocks responsibly and justifying each one

What you will be able to do

  • You understand how coding agents work and choose the right tool and level of autonomy.
  • You write specifications and project context that agents can work with reliably.
  • You break initiatives into verifiable sub-tasks and steer agents through test-driven loops.
  • You use multi-agent setups and parallel work in a controlled way.
  • Use AI agents as sparring partners for ownership, lifetimes, traits and async Rust.
  • Generate tests, ports and services and verify them with the compiler, Clippy and Miri.
  • Systematically assess generated unsafe and FFI code for memory safety.

Course outline

Day 1

Module 1 Foundations of agentic development
  • How coding agents work: tool calls, context windows and feedback loops
  • Comparing tools: terminal agents, IDE agents and cloud agents
  • Recognising suitable tasks and choosing levels of autonomy deliberately
  • The new role in the team: from implementation to steering and acceptance
Module 2 Specifications instead of prompts
  • Describing tasks with goal, context, constraints and acceptance criteria
  • Keeping project context in files such as CLAUDE.md, AGENTS.md or rules
  • Plan-first approach: let the agent draft a solution and review it before implementation
  • Versioning specifications and maintaining them as part of the repository
Module 3 Task decomposition and test-driven agent loops
  • Breaking large initiatives into independent, verifiable sub-tasks
  • Having tests written first and using them as an objective stopping criterion
  • Using linters, type checks and builds as automatic feedback
  • Recognising stuck loops and restarting with a new strategy
Module 4 Multi-agent setups and parallel work
  • Defining specialised subagents for research, implementation, testing and review
  • Organising parallel work with branches, worktrees and isolated environments
  • Orchestration: merging results and resolving conflicts
  • Sharing tools and data sources through MCP

Day 2

Module 5 Review, security and team governance
  • Review strategies for large, agent-generated changes
  • Defining permissions, sandboxing and protection against prompt injection
  • Embedding agents in CI pipelines and pull request processes
  • Planning team guidelines, accountability, costs and a phased rollout
Module 6 Practice lab: Rust
  • Understanding and fixing compiler errors
  • Tests and property-based tests
  • Porting C and C++ modules
  • Async services with Tokio
  • Clippy and idiomatic code
  • Reviewing unsafe code
Module 7 Data protection, quality & transfer to daily work
  • Rust is often used in security-critical components for which the Cyber Resilience Act sets requirements on vulnerability handling and SBOMs. Check new crates for vulnerabilities and licences with cargo-audit or cargo-deny, and treat proprietary systems code as confidential when using cloud-hosted models.
  • 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

Understanding and fixing compiler errors

The assistant explains borrow checker and lifetime errors in plain language, deliberately proposes alternative ownership structures such as references, Rc or cloning, and iterates with cargo check until the build is clean.

Tests and property-based tests

The AI writes unit and integration tests, doc tests and property-based tests with proptest that check invariants over many generated inputs, uncovering edge cases in parsers or algorithms.

Porting C and C++ modules

Existing code is moved to Rust module by module, FFI bindings are created with bindgen or cbindgen and behaviour is safeguarded by shared tests run against the old and new implementations.

Async services with Tokio

Specifications become HTTP or gRPC services built with Axum or Tonic, including structured error types, graceful shutdown, tracing and sensible handling of cancellation and timeouts.

Clippy and idiomatic code

Clippy lints are worked through systematically, error handling standardised with thiserror or anyhow, and iterators, pattern matching and traits used idiomatically. Existing tests safeguard every change.

Reviewing unsafe code

The agent inventories unsafe blocks, documents their safety invariants, proposes safe alternatives and runs Miri to detect undefined behaviour. Each justification is recorded as a SAFETY comment in the code.

Possible hands-on projects

Fast log parser

A Rust CLI that streams large log files, detects patterns with regular expressions and outputs statistics – with benchmarks comparing it against a scripting-language version.

Axum microservice

A small REST service using Axum, SQLx, structured tracing and integration tests, planned and implemented end to end by an AI agent.

WebAssembly module

A compute-heavy function, such as image processing or validation, packaged as a WebAssembly module with wasm-bindgen and embedded in a simple web page.

Prerequisites

You have several years of development experience, are confident with Git, testing and CI, and ideally have already used AI coding tools. Basic Rust experience with Cargo, ownership and traits, plus experience in at least one other systems or back-end language.

Technical requirements

Your own laptop with Git, a terminal and your development environment, plus access to at least one coding agent such as Claude Code, Codex, Copilot or Cursor.

Data protection & compliance

Rust is often used in security-critical components for which the Cyber Resilience Act sets requirements on vulnerability handling and SBOMs. Check new crates for vulnerabilities and licences with cargo-audit or cargo-deny, and treat proprietary systems code as confidential when using cloud-hosted models.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Tue, 24 November 2026 – Wed, 25 November 2026 Online Request
  • Mon, 30 November 2026 – Tue, 1 December 2026 Munich Request
  • Thu, 10 December 2026 – Fri, 11 December 2026 Online Request
  • Tue, 19 January 2027 – Wed, 20 January 2027 Hanover Request
  • Thu, 4 February 2027 – Fri, 5 February 2027 Online Request
  • Mon, 8 February 2027 – Tue, 9 February 2027 Berlin Request

Frequently asked questions

How does agentic coding differ from vibe coding?

Vibe coding relies on fast, intuitive iteration in natural language and is particularly suited to prototypes. Agentic coding is an engineering discipline for professional codebases: precise specifications, tests as acceptance criteria, clear permissions and structured reviews ensure that agents deliver reliable, maintainable results even in complex, long-lived projects.

Is the course tied to a specific tool?

No. The course teaches methods that work with Claude Code, OpenAI Codex, the GitHub Copilot coding agent, Cursor and comparable tools. The exercises highlight differences and common ground, for example in context files, permissions and subagents. You can work with whichever tool your organisation already uses or plans to adopt.

How do we stay in control of quality and security with autonomous agents?

Control comes from several layers: tightly scoped permissions and sandboxing, tests and static analysis as automatic checks, mandatory human review before merging, and clear team rules on accountability. During the course you develop a governance concept that fits your processes, security requirements and regulatory obligations.

Can AI help me get started with Rust?

Very much so. AI assistants explain compiler errors patiently and in the context of your own code, show alternative approaches and explain why the borrow checker rejects a construct. The key is to understand the explanations rather than accept suggestions blindly, so the course relies on hands-on exercises in which you work out solutions together with the AI.

How reliable are AI ports from C++ to Rust?

They work well for clearly bounded modules when behaviour is protected by tests. The tricky parts are pointer arithmetic, shared mutable state or undefined behaviour in the original. On the course you learn to port incrementally, run differential tests against the old implementation and keep unsafe code to a deliberate minimum.

How much does “Agentic Coding for Rust Developers” 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 Rust Developers

More Agentic Coding courses

All 32 Agentic Coding courses

Agentic Coding · MunichAgentic Coding · SalzburgAgentic Coding · BerlinAgentic Coding · AugsburgAgentic Coding · HanoverAgentic Coding · BremenAgentic Coding · StuttgartAgentic Coding · KaiserslauternAgentic Coding · Online