Quick hello from India. On 1 August I’m running a full-day AI Workflow Mastery session for around 250 final-year engineering students, and Cursor is one of the main tools they’ll build in. Most will be first-time users.
Two things I’d value input on from the team and anyone who’s run this:
For a big first-time group, any setup or workflow that makes a one-day format go smoothly? Things that trip beginners up, or a project shape that works well in a day.
Is there an official path for temporary access or event credits for a student session like this? I saw Cursor is investing more in campus this year, so figured I’d ask here. I’ve also filled out the education form.
Keeping the org details light for now. Mostly want the day to be a great first Cursor experience for the students. Thanks.
About event credits and student access. This year Cursor is expanding campus support, and there’s an official path for sessions like yours. Check the announcement New Campus Community Launches. For the event, fill out the separate event inquiry form Host a Campus Event at Cursor. That’s the right channel to request credits or support for a workshop. The education form you already filled out is for a different track. There’s also an MLH partnership for workshops and credits, plus a campus newsletter for early access Join Cursor's Campus Newsletter.
For context, the legacy student discount is closed for new sign-ups, so student access now goes through events and credits. Your case fits that path.
Looping in @Fiona_Whittington. She’s the Campus Community Lead and can help with timing and details for August 1.
About a one-day format for beginners. A few things that usually help:
Ask students to install Cursor and log in ahead of time at home, so you don’t lose time on setup at the start of the day. Start with Quickstart | Cursor Docs.
Pick one shared starter project that’s small enough to finish in a day. One repo or template for everyone reduces variance and setup issues.
Prepare .cursor/rules in advance for the project, so everyone gets consistent agent behavior and fewer why-is-mine-different issues.
A common beginner trap is sending requests that are too big or too vague. Show how to give specific context, like referencing files with @ and stating a clear task. That usually improves results right away.
Thanks, this is really helpful, and good to know the education form was the wrong track.
One snag. The Host a Campus Event form looks scoped to a couple of cities, and I’m in Gandhinagar, India. I filled it in anyway rather than assume a no, but flagging it here in case there’s a better route for events outside those cities.
Worth noting Cursor already has a footprint here. There’s been a Cursor Mumbai meetup, and the Cursor x Anthropic hackathon in Malaysia gave every participant credits. So a supported student session in India wouldn’t be new ground, just a new city.
For context on scale: LDRP is the flagship engineering institute of Kadi Sarva Vishwavidyalaya, a UGC-approved university with 20+ constituent colleges. 250 final-year students on 1 August, most opening Cursor for the first time.
@Fiona_Whittington, if the event form isn’t the right path for India, is there another way to get credits or access for the session? Happy to go through the hackathon credits form, [email protected], or whatever fits. I’d also like to look at the Ambassadors program, since I run sessions like this regularly.
Also, thank you for the format advice. Pre-install and login at home, one shared starter repo, and committed .cursor/rules are going straight into the plan. The point about vague prompts and teaching @ file references is exactly the beginner trap I was worried about.