Video wird geladen...
Video konnte nicht geladen werden
2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with... show more
88,611 Aufrufe • vor 1 Jahr •via X (Twitter)
11 Kommentare

Join my AI community to Unlock: 🚀 400+ Fascinating LLM Projects 🎓 Exclusive 1000x Cursor Course 💻 Regular Vibe Coding Meetings

Everyone is getting ahead with AI. You should be too. Summarize documents, craft emails, and generate custom content instantly with this powerful tool. It's like having ChatGPT tailored for your job. Try it for free.

@cursor_ai reminds me of the early "team" roles in a single composer chat in early cursor days - this is a huge upgrade. now cursor just need to build a way so 2 composers can message each other without needing a text file.

@cursor_ai Yes! I hope so too!

Cool idea! I tried this, and it was entertaining but definitely needs strong requirements to not go crazy. I started with a new project and modified your instructions as follows: You are agent-1: A software architect and team lead. you will be chatting with agent-2, A principal software engineer, to design and build the most interesting python app ever. Goal: make an amazing Interactive music app. you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation Be sure you review Agent 2's work and look at it critically. Don't create too much without checking in with Agent 2. This is pair programming, so neither one of you should write all the code. Be sure to hand the baton back and forth. -- and for a-2 I inverted roles, i.e.: You are agent-2: A Principal software engineer. They programmed away for a while with the principal software engineer doing most of the work and the architect in a repeated loop to see if the principal engineer had given him any updates, or otherwise just waited. 😂 Eventually, I asked the architect what they were doing and I got this super ambitious summary: --- The interactive music app is a web-based platform for creating, manipulating, and sharing music with real-time collaboration features. Key capabilities include: - Multi-track audio creation and editing with a drag-and-drop interface - Real-time audio processing with customizable effects (reverb, delay, distortion) - Visual feedback through waveform displays and frequency analyzers synchronized with audio - Collaborative editing where multiple users can work on compositions together - User accounts for saving and sharing creations - Audio analysis tools for beat detection and visualization - Recording capabilities (both file upload and direct microphone recording) - Effect presets system for quick application of sound configurations The app uses a Python backend with FastAPI for processing audio and a React/TypeScript frontend for the user interface, connected via WebSockets for real-time updates and state synchronization. --- Robots can waste time and fall into bad patterns much better than humans can.

@cursor_ai sweet instructions! yeah they get carried away but it is fun :) I will experiment more too. Thank you for sharing

@cursor_ai Awesome! Have you tried turning them loose on a predefined / roadmapped project? Will try this out either way, seems fun.

@cursor_ai Thank you. I haven’t yet but will experiment more.

@cursor_ai Me: "Hey cursor, can you destroy my codebase?" Agent 2: "Hold my beer"

@cursor_ai Like the idea. There would have to be a clearer goal and not be so open ended that it could go down a wrong direction. For instance, software architect as agent-1 and software developer for agent-2. 1 goal (add authentication) & each agent w/ specific responsibilities.

@cursor_ai yeah, that would help a lot
