Skip to main content

cloud-prep: Getting Local Cursor Workspaces Ready for Cloud Agents

ยท 2 min read
Mike Homol
Director of Innovation @ ThreeWill

I want more of my repo work going to Cursor cloud agents. The catch: a cloud agent only sees the repo and its brief. The decisions behind the code mostly live in my local Cursor chats and plans, where no cloud agent can read them. So I built cloud-prep, a repeatable skill that moves that context into the repo once.

How it worksโ€‹

  • Harvest: read the workspace's local Cursor chat history and plan files, read-only, and draft a context doc: purpose, architecture, key decisions with dates and reasons, conventions, known pitfalls, open issues, and environments (secret names only, never values)
  • Review: I read the draft and fix it before anything goes into the repo
  • Docs-only PR: a cloud agent checks the draft against the code and opens one PR. It adds the context doc, a decision log, the original plans, an AGENTS.md read-first list, and a copy of the ThreeWill engineering standards, including the plan-first rule. No source code changes
  • After that, the rule that docs get updated in the same PR keeps the context current

What happenedโ€‹

  • My Grok Bot Gongi and I ran it on three repos this week: an internal HR app and two client solutions
  • One of the client solutions wasn't on GitHub yet, so it moved there with the context docs in its first commit
  • The review caught stale docs along the way, like wrong environment variable names in a runbook and an outdated package version, and I fixed them