Cursor Mobile App: Guide Your Coding Agent from Your Phone
Cursor has released a mobile app called Cursor Mobile, allowing developers to prompt and interact with coding agents directly from their phone. The app ties into the Cursor 2.0 changes from October 2025, which shifted the service toward independent coding agents. With the mobile app, users can spin up new coding agents or interact with agents initiated from the desktop client.
Key Details
- Cursor Mobile lets you spin up new coding agents or continue existing agent sessions started on the desktop.
- The app is designed for continuous conversations with remote agents—no need to access large code bases from the phone.
- Cursor follows similar mobile apps from Anthropic (Claude Code works on mobile) and OpenAI, reflecting a broader shift toward mobile-first AI coding.
- Anthropic’s head of Claude Code, Boris Cherny, confirmed he now does most of his coding on a phone: “I would have said ‘you’re crazy’ if you told me that six months ago, but yeah, here we are.”
- Cursor was recently acquired by SpaceX for $60 billion, but the company continues to ship new features.
Who It's For
Developers already using Cursor’s agentic coding features who want to oversee or prompt agents while away from their desk, enabling a mobile-first workflow.
📖 Read the full source: HN LLM Tools
👀 See Also
Senior Government AI Lead Lacks Local LLM Awareness: A Developer's Account
A local LLM developer reports that a senior government AI leader was unaware of why businesses would choose local LLMs over cloud APIs, despite understanding technical basics.
The AI Ping-Pong: When Every Reply Is a ChatGPT Screenshot
Developers report being flooded with AI-generated answers — from coworkers, bosses, and even GitHub commenters — that ignore context and waste time. The HN discussion captures a growing frustration.
Stanford CS 25 Transformers Course Opens to Public with Live Streaming
Stanford's CS 25 Transformers seminar is now open to the public with lectures starting January 23, 2025, at 4:30-5:50pm PDT, available in-person at Skilling Auditorium or via Zoom, with recordings posted online.
Critique of MCP's Abstraction Boundary and Service Integration Approach
A Reddit discussion critiques MCP for bundling API access, efficient tooling, and domain knowledge into one layer, arguing this creates limited interfaces compared to underlying APIs. The post uses Lattice as an example where their public API only covers HR admin workflows despite having a full GraphQL API.