Cursor 3 is a layered system: .cursorrules for policy, the plugin marketplace for distribution, Team Marketplaces for centralised governance, MCP servers for external context, MCP Apps for interactive output in chat, Background Agents for long-running work, Bugbot for review, Cursor Automations for scheduled or event-triggered runs, JetBrains ACP support for non-VS-Code teams. The Composer 2 plus Opus 4.6 plus GPT-5.4 plus Gemini 3 Pro model selector adds another axis. Most teams use a quarter of this surface area and pay for the rest.
Course objectives
Target audienceSenior engineers, staff engineers, tech leads, platform and DevEx teams, internal AI champions.
Prerequisites
Module 1.
Cursor 3 as a layered system. The Cursor Feature Matrix as a day-one handout: rules, plugins, Team Marketplaces, MCP servers, MCP Apps, Background Agents, Bugbot, Automations, model selector.
Module 2.
Model selection. Composer 2 for speed and IDE responsiveness. Opus 4.6 for codebase-wide refactors and architectural reasoning. GPT-5.4 for OpenAI-aligned shops. Gemini 3 Pro for very long context windows. Auto mode handles most routine work. Lab: write a per-task model policy for the team.
Module 3.
Plugins, Team Marketplaces, MCP , MCP Apps. Plugins (one-command install) for personal extensions. Team Marketplaces for centralised governance. MCP servers for external context. MCP Apps for interactive charts, diagrams, whiteboards inside agent chats. Lab: select three MCP servers and one MCP App for the team's stack, justify each.
Module 4.
Background Agents and Cursor Automations. Background Agents for long-horizon tasks with visual demos. Automations for scheduled or event-triggered cloud runs (Bugbot Autofix is one exampleof this architecture). When the asynchronous flow earns its credit cost, when it does not. Lab: build one Cursor Automation for the team's actual workflow.
Module 5.
Bugbot at scale. Tuning rules for the team's domain. MCP integration for Bugbot context. Bugbot Autofix economics: when it saves cycles, when it produces noise. Bugbot's learned rules and how the team can shape them. Lab: configure Bugbot with team-specific rules and validate against historical PRs.
Module 6.
Capstone. 90-day rollout: pilot, expansion, standard practice. Named owners. Success criteria. Kill switch. Must include at least one Automation pattern in production by phase 3. Plan defended to the room.
Duration: 1 day
Price: 10 900 NOK
Language: English
Format: Classroom, virtual classroom, or in-company
Hva er Cursor Advanced?
Cursor Advanced er et videregående kurs for utviklere som ønsker å bruke Cursor som en integrert del av utviklingsprosessen i større og mer komplekse prosjekter.
Hvem passer kurset for?
Kurset passer for erfarne utviklere, tech leads og arkitekter som allerede har jobbet med Cursor eller lignende AI-verktøy, og som ønsker å bruke det mer systematisk i team og organisasjon.
Trenger jeg forkunnskaper for å delta?
Ja, det forutsettes erfaring med programmering og praktisk bruk av Cursor eller tilsvarende AI-assistert utviklingsverktøy.
Er kurset praktisk rettet?
Ja, kurset er hands-on og tar utgangspunkt i realistiske utviklingsscenarioer, hvor du jobber med større kodebaser og mer avanserte arbeidsflyter.
Hva lærer jeg som er nyttig i praksis?
Du lærer hvordan du strukturerer avanserte arbeidsflyter, håndterer komplekse kodebaser, forbedrer kvalitet og testdekning, og integrerer AI-verktøy i teamets utviklingsprosess. Dette inkluderer også hvordan AI kan brukes i debugging, refaktorering og automatisering av utviklingsoppgaver
