This post is exactly what the title says: how I use Cursor from my phone to write blog posts, and what the flow looks like end to end.
Why I tried it
I had stacks of travel notes and rough memos and wanted to turn them into real posts on the site.
You might find this useful if you
- Publish posts with Astro
- Want to drive Cursor from your phone
Context
This site is built with Astro and deployed to Cloudflare Pages.
Posts live in Markdown in a Git repo: push to GitHub and a pipeline builds and publishes.
Cursor can take instructions through Slack, so from my phone I can ask Cursor to shape a draft and open a PR toward that repo.
I walk through the pieces below. A proper CMS would be nicer; for now everything is plain Markdown in GitHub.
Screenshot of a phone memo covering setup and where writing happens:
Where the draft lives
I use Obsidian and keep things in Markdown.
I export that content as a text file (still Markdown inside) so it becomes the handoff payload for Cursor.
When you attach images in Obsidian you often get wikilinks like this:
![[IMG_4156.jpeg]]Use the same filenames when you upload assets to GitHub so paths stay aligned. Later you can ask Cursor to swap wikilinks for normal Markdown image paths.
Save the exported .txt with Save to Files so you can attach it easily from Slack.
Putting images in the repo (phone → GitHub)
I could not upload images through Cursor (at least in my setup), so images go in by another path.
On mobile, open GitHub in the browser with the desktop site — that is the reliable way to add files and commit.
Upload the photos you referenced in Obsidian, then keep working.
You can also have Cursor create the post, folders, and placeholder images first, then add real images later and ask for path fixes.
Target folder should match what the Markdown will use, e.g. src/assets/cursor-smartphone-blog-workflow/ for this article.
If filenames match the names in your Obsidian note, wikilinks like ![[IMG_4156.jpeg]] line up with real files and Cursor understands the swap to  more easily.
Asking Cursor from Slack
In Slack, @Cursor with something like: please turn the attached file into a blog post.
Agent settings (repository and branch)
Mention @Cursor settings in Slack to change configuration.
Under Change Settings you can set Model, Repository, and Branch. In my case I use composer-2, repository testkun08080/blog, and branch main.
Set the branch explicitly so work does not land on the wrong branch by accident.
Build and preview (Cloudflare Pages)
After a push, the Cloudflare Pages bot often comments on the PR with Deploy successful! and a preview URL — that is where I sanity-check the result.
Publishing
If the preview looks good, merge the PR and you are done.
Takeaways
- Preview on Cloudflare still took time for me — image wiring was the fiddly part.
- If I do this more often, I would either build a small editor workflow or harden the image step.
- Obsidian → export as
.md/ text → Cursor via Slack worked fine as a drafting handoff.
Thanks for reading.
For Cursor’s newer agent UI (Japanese article): Cursor 3: Agents Window and the April 2026 update
New to Cursor? Try Cursor (50% off for a limited time) (referral link).
