Hi Product Hunt! 👋 I'm Ersin, the creator of Ersinis. As developers, we spend way too much time navigating between AI chat windows, copying/pasting code, and manually fixing file structures. I wanted to build something that actually *does the work* directly where the work happens: in the terminal. That’s why I built Ersinis. It’s not just an AI assistant; it’s an autonomous multi-agent ecosystem. 🧠 It uses a 3-agent orchestration system: - Artemis: The voice-first orchestrator and main interface. - Ersinis: The "Brain" that handles QA, architectural planning, and deep RAG analysis. - İşçi (Worker): The "Muscle" that writes code and executes multi-file refactors. You simply give a command, and they plan, execute, review, and report back to you. No more copy-pasting. I built this to scratch my own itch, but I believe it will fundamentally change how developers interact with their codebases. I’d love for you to try it out, tear it apart, and tell me what you think. I'm here all day to answer your questions! Let's chat in the comments. 👇

Forum Threads

p/ersinis

•

1d ago

Terminal vs IDE: Where do you prefer your AI coding agents?

Hey everyone! I m launching Ersinis tomorrow (an autonomous multi-agent developer system), and I had a huge debate with myself during the build process.

Tools like Cursor and Copilot live directly in the IDE or browser. But I decided to build Ersinis as a terminal-native agent because I feel the terminal is where the real "magic" and file executions happen.

Do you prefer your AI assistants strictly inside your code editor (like VS Code/Cursor), or do you like having a terminal-based autonomous agent that acts like a standalone team member?

Would love to hear your thoughts before my launch tomorrow!

View all

ersinis

Autonomous AI developer agent that actually codes for you.

Autonomous AI developer agent that actually codes for you.

Forum Threads

Terminal vs IDE: Where do you prefer your AI coding agents?

Forum Threads

Terminal vs IDE: Where do you prefer your AI coding agents?