u/welsh_cthulhu

I AM THE GREAT CORNHOLIO!

I NEED SURREPTITIOUS LETTERS FOR MY BUNGHOLE!

My public Cursor profile isn't fully displaying the models I've used. I mostly use Composer, Grok and Auto mode, but I've used various Sonnets a fair bit too, and the odd GPT.

I'll be applying for jobs soon if my employer doesn't get their head out of their ass, and I want to make sure prospective employers know I'm not a two-trick model pony!

Really liking this profile feature though. Cool idea. I can see them expanding this with the upcoming source control stuff.

Good snooker player too. Never paid for the lights though.

Evening all!

I'm an Cursor Enterprise Admin. I just finished a "Drift Robot" (no idea what to call it, but that sounds cool, so why not) that automatically scrapes Cursor's docs and raises MRs in our GitLab to update our internal Cursor docs (governance, admin and user guides) - we've got an admin guide and a standard user guide (both hosted on ADO). Not sure if anyone will find it useful, but thought I'd post it here just in case.

It's basically a docs-as-code pipeline that uses a cloud agent (singular), CI pipelines, Cursor automation, and various other bits and bobs. We edit in Cursor, push to GitLab which sends a read-only mirror to various ADO repos and project wikis.

Here is how it works:

1. A Python script runs on a cron schedule in GitLab. It pulls the raw markdown files from cursor.com/docs and diffs it against our last known snapshot. If there's factual changes, it fires a webhook.
2. The webhook wakes up a Team-owned Cloud Agent via Cursor Automations. I wrote a strict prompt that maps specific Cursor doc pages to our internal files. The agent analyses the drift - ignoring marketing fluff, and focusing on catching actual workflow changes.
3. The agent automatically updates our internal markdown files to match Cursor's new features. It then writes a plain-English report (kind of like an exec summary) explaining exactly what Cursor changed upstream and what it updated internally. It then creates a new branch and opens a GitLab Merge Request for a human to review.

I'm still testing it but I'm hoping it'll signal the end of manual runbook updates. When Cursor drops a new feature or changes UI elements, or model availability, we just get an MR with the exact docs-as-code changes needed to keep our team up to speed.

I can't post the GitLab repo as it's private, but happy to chat if needs be :) There's various other config tasks we've managed to automate in the same workflow too, mostly involving YAML snapshots, linting and changelog entries.

I feel old.

I still remember his debut against South Africa. He only had a few games for the Scarlets I think, but Gats being Gats he saw the potential. 18 years old and knocking Springboks off him like it was nothing. Two tries. Easy.

Have a good one George boy. What a player he was.