Your team gets more out of Cursor's agent, and every engineer uses it the same way.
Cursor training for engineering teams: two hands-on days in the editor and the Cursor CLI, then mentoring in your team's own work.
Written by
-
Benedikt Stemmildt Founder & Co-CEO
Updated:
- Format
- Two days, remote or on site, in German or English
- Group
- 8 to 12 participants
- Price
-
EUR 1,500 per participant
Up to 12 people attend, and you pay for 10 at most (EUR 15,000)
Net, plus VAT. On site, plus travel at cost.
- Who delivers it
- AboutOne of our 70+ trainers
- Tailored
- Adapted to your team and stack in a preparation call
- Mentoring
- As needed after the training, EUR 250 per hour, typically EUR 2,000 to 12,000 in total
How the training runs in Cursor
hackers&wizards runs Cursor training for engineering teams as an in-house team training: two days, remote or on site across Germany, Austria and Switzerland, in German or English, then mentoring while your team applies it to real work. It is our Agentic Engineering for Developers and QA training, run in Cursor.
EUR 1,500 per participant. Team training, EUR 15,000 at most for the two days: up to 12 people attend, and you pay for 10 at most. Net, plus VAT. On site, plus travel at cost.
Teams have run every one of our trainings for engineering, product and leadership in Cursor. Exercises, review steps and mentoring work the same way in every agent. What changes are the instruction files and the settings, and we set those up with you on day one.
What's different in Cursor
After the training, your team writes rules that load only where they apply, keeps the skills and subagents it built for Claude Code and picks a run mode your security team allows.
-
Project rules in .cursor/rules
Rules are
.mdcfiles with frontmatter. Cursor ignores a plain.mdfile in that folder. A rule applies always, when the agent decides it's relevant, to the files matching its globs, or when someone mentions it by name. Cursor also readsAGENTS.mdat the root and in subfolders, and Team Rules take precedence over project rules. -
Claude's skills and subagents load too
Skills live in
.cursor/skillsor.agents/skills, subagents in.cursor/agents. Cursor also loads.claude/skillsand.claude/agents, so a team moving over from Claude Code keeps everything it built. -
Hooks and MCP per project
.cursor/hooks.jsonruns scripts on events likebeforeShellExecution,afterFileEditandstop. MCP servers go in.cursor/mcp.jsonfor one project or~/.cursor/mcp.jsonfor all of them. -
Run modes and the sandbox
The agent runs in Auto-review, Allowlist or Run Everything, with Auto-review as Cursor's recommended default. The sandbox blocks any file or network access it wasn't granted, using Seatbelt on macOS and Landlock on Linux kernel 6.2 or later, configured per project in
.cursor/sandbox.json. -
The editor first, the CLI too
Cursor is the editor, so the agent sees whatever the engineer has open. The agent command brings the same agent to the terminal, with Agent, Plan and Ask modes.
What you set up on your side
- Cursor on every participant's machine, on a Teams or Enterprise plan, with privacy mode set by your admin if your company requires it.
- Our hosted training environment is a browser editor with Claude Code, while Cursor is a desktop app, so a Cursor training runs on your machines and licences. Your code stays put: the trainer works with your team on screen.
- In the prep call we agree which run mode your security team allows, and which repository the team practises on, ours or yours.
That way day one starts in Cursor on your machines, with a run mode already agreed.
A sample first day in Cursor
By the end of the day, your team turns repeated corrections into rules and has the tests run every time the agent finishes.
This is how the first day typically runs in Cursor. Your trainer cuts it to your codebase in the preparation call.
-
Rules from the agent's mistakes
The team has the agent work on a real task, notes every correction it has to make, and turns the repeat offenders into scoped
.mdcrules with globs. The usual mistake is one huge always-apply rule, or a rule saved as.mdthat never loads. The trainer has the team check which rules the agent actually used. -
Keep your Claude Code setup
Teams that already have
.claude/skillsand.claude/agentsopen the repository in Cursor and find both already loaded. The team then writes one new skill for a step it keeps repeating and has a subagent use it. -
Allowlist, sandbox and a stop hook
Participants switch to Allowlist with the sandbox on, add the test command, and write a stop hook in
.cursor/hooks.jsonthat runs the tests when the agent finishes. Run Everything stays off.
What stays the same
The practice is the same in every agent: how the agent loop works, what context it needs, how to delegate so it checks its own work, and how the whole team keeps one way of working. The agenda, the trainers and the mentoring are those of the training you book.
Questions before you book
Can we run the training in Cursor?
Yes. Every engineering, product and leadership training runs in Cursor, on your Teams or Enterprise licences. Your team works in the editor and, where it makes sense, in the Cursor CLI.
Do we need Claude Code licences?
No. Your team trains on its Cursor licences. Cursor is a desktop app, so the training runs on your machines instead of our hosted environment.
What's different about Cursor?
Instructions are .mdc project rules in .cursor/rules or AGENTS.md, hooks go in .cursor/hooks.json, MCP in .cursor/mcp.json, and terminal commands follow run modes with a sandbox. Cursor loads Claude Code's skills and subagents, and the agent loop, context engineering and the review steps stay the same.
Our team already uses Cursor every day. What does the training add?
Licences put the editor on every machine, but the way the team delivers often doesn't change. The training changes how the team works: what context the agent needs, how to delegate so it checks its own work, and how the whole team keeps one setup in the repository.
What does it cost?
EUR 1,500 per participant. Team training, EUR 15,000 at most for the two days: up to 12 people attend, and you pay for 10 at most. Net, plus VAT. On site, plus travel at cost. Mentoring is on call after every two-day team training: you book the hours your team needs, typically 2 to 4 a week over 4 to 12 weeks, at EUR 250 per hour, billed monthly as delivered. At those hours that is about EUR 2,000 to EUR 12,000 on top of the training.
Sources
Vendor facts on this page, checked against the vendor's documentation on 27 October 2026.
Not sure where to start? Take the self-check