Then ask Cursor to either start working on the open MagicPath file, create a new one, or point to an existing one. Cursor will know what to do.
@skirano
-
Integrating MagicPath AI Skill with Cursor Code Editor
By
–
We are going to work together with Cursor soon to make this more seamless, but here are the instructions on how to do it. First, install the MagicPath skill following the instructions here: https://
magicpath.ai/documentation/
features/external-agents
…, then open MagicPath in the Cursor browser and connect to your -
Using External AI Agents with MagicPath, Cursor, and Claude Code
By
–
Here are all the instructions on how you can use external agents in MagicPath with Cursor, Codex, Claude Code, etc.
-
MagicPath: A Visual Canvas for AI-Powered Interface Design and App Production
By
–
Composer 2.5 Fast, it's almost instant how you can see in the video! Definitely great to explore quickly. MagicPath gives Cursor a visual canvas where you can design interfaces, use product context, collaborate with humans, and produce live apps your team can review.
-
Cursor Composer 2.5 Swarms Agents to Build Web Pages and Mobile Apps
By
–
Watch Cursor Composer 2.5 swarm 10 agents inside MagicPath, building functional pages, a mobile app, and a bunch of components for the same project.
— Pietro Schirano (@skirano) 26 mai 2026
Then I export whatever I want into Figma.
Pretty crazy.
(video is not sped up) pic.twitter.com/DvdZa57iJiWatch Cursor Composer 2.5 swarm 10 agents inside MagicPath, building functional pages, a mobile app, and a bunch of components for the same project. Then I export whatever I want into Figma. Pretty crazy.
(video is not sped up) -
MagicPath Introduces Figma Export with AI Agent Integration
By
–
Introducing Figma export in MagicPath.
— Pietro Schirano (@skirano) 26 mai 2026
Design and build with our native agent, or your favorite external one (Codex, Claude Code, etc.).
Explore tons of different directions, then bring your work into Figma as fully editable designs.
As simple as a copy-paste. pic.twitter.com/ON9h0UCXpuIntroducing Figma export in MagicPath. Design and build with our native agent, or your favorite external one (Codex, Claude Code, etc.). Explore tons of different directions, then bring your work into Figma as fully editable designs. As simple as a copy-paste.
-
Automating Software Design and Implementation with AI Agents
By
–
Tired: open the design, read PM feedback, push pixels for 3 hours
— Pietro Schirano (@skirano) 19 mai 2026
Wired: go for a walk, pull the Linear ticket in Codex, have it build the design in MagicPath, share the link, back to your walk https://t.co/yY4ni9doTFTired: open the design, read PM feedback, push pixels for 3 hours Wired: go for a walk, pull the Linear ticket in Codex, have it build the design in MagicPath, share the link, back to your walk
-
Optimizing Workflows with AI Coding Agents and Tools
By
–
Working with Codex gives you access to tons of things like your entire local context (files, notes, repo) skills, MCPs and of course an overall really strong agent. Once Codex makes stuff, you can still use the MagicPath native agent to improve it to your liking. As I shown in
-
Codex Model’s Role in Autonomous Design Execution
By
–
No, Codex actually communicates with MagicPat, like it’s Codex that is making the designs. Having it running in the app is a nicer addition to the experience, but the real magic is that it’s Codex that is in control. In their video, it is just a browser lmao.
-
Using Codex for multi-agent workflows and function calls
By
–
Yes, so Codex can actually run multiple MagicPath calls, or you can also ask Codex to spawn multiple agents if you want to do that more efficiently!