Cursor just shipped version 3.5, and the headline feature is deceptively simple: you can now attach more than one repository to an automation. That might sound like a minor config option, but for anyone running microservices or a monorepo-adjacent architecture, it fundamentally changes what an AI agent can actually do for you.
One agent, many codebases
A lot of engineering work spans more than one codebase. You can now attach multiple repos to an automation so agents reason across all required context and work across repos to deliver, test, and verify tasks. Before this, the workflow was painful: automations operated on one repo, so a change that needed coordination across a shared library and its consumers required multiple separate automations or manual orchestration.
Now it's one automation, one agent, multiple repos. In practice, that means an agent can find a type mismatch in a shared types library, update the export, propagate the fix to the frontend interface, and update the corresponding backend model -- all in a single run. With multi-repo, it can find the mismatch in the types library, update the export, update the consuming interface in the frontend, and update the corresponding Pydantic model in the backend -- one session, three coordinated PRs.
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves