Show HN: Dev-loop – parallel coding agents, supervised not just spawned

In a significant development for coding and project management, a new plugin named Dev-loop has emerged, integrating advanced orchestration capabilities for coding agents. This tool, which operates as a Claude Code plugin, enhances the existing loop-orchestrator by introducing a multi-session orchestrator that effectively manages coding tasks across various projects. The Dev-loop plugin not only streamlines the coding process but also incorporates a knowledge-capture mechanism that allows users to document insights and best practices automatically, creating a living repository of information that evolves with each coding session.

Enhanced Orchestration Features

The Dev-loop plugin introduces a sophisticated orchestrate skill that decomposes project goals into a dependency graph. This graph allows for the scheduling of parallel workers using a ready-set scheduler, which optimizes the workflow by ensuring that tasks are executed concurrently where possible. Furthermore, the plugin supervises these tasks using Orca, a command-line interface (CLI) that enhances the coordination of coding efforts. If Orca is not installed, the plugin defaults to using tmux, a terminal multiplexer that allows multiple terminal sessions to be accessed simultaneously.

One notable change from the upstream loop-orchestrator is the fixed plan step, which is now integrated with a wiki-plan methodology. This means that every non-trivial coding task must route its design decisions to a corresponding page in a bundled wiki before any actual coding begins. This structured approach ensures that decisions are documented and accessible, reducing ambiguity and enhancing clarity in the development process.

Additionally, Dev-loop introduces a knowledge-capture loop that automatically generates verified insights during coding sessions. This feature allows users to document significant findings and best practices, which are then processed through a knowledge-flush mechanism that organizes and stores these insights in a reviewed pull request (PR). This growing repository of knowledge not only benefits the individual user but also contributes to the collective intelligence of the coding community.

Seamless Integration and Configuration

The installation of the Dev-loop plugin is straightforward, as it is available through the Claude Code plugin marketplace. Once installed, its features are universally applicable across all projects, eliminating the need for repository-specific configurations. The plugin operates generically without requiring extensive setup, although users can map its capabilities to their existing tools for enhanced functionality.

To configure Dev-loop, users can execute a simple command that generates a configuration file, allowing for both global and repository-specific settings. This flexibility ensures that teams can share configurations while also accommodating individual preferences. The plugin also includes a SessionStart hook that nudges users to configure their settings, promoting a proactive approach to setup.

The orchestration capabilities of Dev-loop treat Orca as a fundamental component rather than merely a terminal spawner. When the Orca CLI is available, it becomes integral to the task-splitting process, ensuring that the orchestration flows smoothly. In the absence of Orca, the plugin retains its functionality through tmux, providing a reliable fallback that maintains the integrity of the coding process.

Why it matters

The introduction of the Dev-loop plugin represents a significant advancement in the realm of coding tools and project management. For creators and technologists, the implications are profound. The structured approach to planning and decision-making ensures that developers are not only writing code but also documenting their thought processes and decisions in real time. This practice fosters a culture of transparency and collaboration, as team members can easily access the rationale behind coding decisions.

Moreover, the automated knowledge capture and flush mechanisms reduce the burden on developers to manually document their insights, allowing them to focus more on coding and less on administrative tasks. This shift not only enhances productivity but also encourages continuous learning and improvement within teams. As the knowledge repository grows, it becomes a valuable resource for both current and future projects, facilitating onboarding for new team members and serving as a reference for best practices.

In conclusion, the Dev-loop plugin is poised to transform the way developers approach coding and project management. By integrating advanced orchestration features with a robust knowledge-capture system, it empowers creators and technologists to work more efficiently and collaboratively, paving the way for more innovative and successful projects in the future.