Genie v6: CLI Agent for Automated Code Generation and Review

What changed

Genie has introduced version 6, a significant update to its command-line interface (CLI) agent focused on automating the software development lifecycle. The core functionality remains centered around transforming a user's high-level request, described in a single sentence, into a fully planned and executed set of tasks, culminating in a merge-ready pull request. This process involves Genie interviewing the user to create a detailed plan, then dispatching parallel AI agents to execute tasks within isolated worktrees. A key feature is the agent's ability to review the generated code against acceptance criteria before presenting it to the developer.

Several legacy components have been retired in v6. The Orca plugin, its adapter, and the one-way card mirror are no longer supported. While a stub for genie orca commands remains visible for one release, these calls will now print a retirement notice and exit with an error code. Similarly, the legacy Genie MCP server is retired, and the genie mcp command has been removed entirely. Developers are directed to use the standalone genie task and genie board commands instead. The upgrade process has also been simplified; the one-shot, backup-first retirement script for plugin-era releases, which ran from v5.260711.6 through the last 5.x release, has been removed in v6. Hosts that updated through any 5.x release are already clean, while those migrating directly from the plugin era to v6 will need to manually remove leftover files.

Genie v6 emphasizes a lightweight architecture, consisting of a set of skills, plain Markdown documents stored in Git, and a single SQLite file per repository for state management. It avoids persistent daemons or external databases like Postgres. Installation is handled via a curl command piping to bash, and updates are managed through genie update. The release process is secured with keyless OIDC signing and SLSA provenance, allowing for offline verification of releases without requiring GitHub credentials. The genie update command verifies the release's signed delivery evidence against an embedded Sigstore trust root.

Why it matters for builders

Genie v6 offers builders a more streamlined and automated path from idea to production-ready code. By handling the planning, parallel execution, and code review stages, it significantly reduces the manual overhead typically associated with these tasks. This allows developers to focus more on creative problem-solving and less on the repetitive aspects of code generation and initial quality checks. The retirement of legacy components also means a cleaner, more focused toolset for developers working with the latest version.

Practical impact

Developers can install Genie v6 using the provided curl command. After installation, genie init can be run within a trusted repository to scaffold state and retire historical project registrations. Running genie doctor is recommended post-installation or update to verify the setup and identify any missing or outdated skills. For new projects, a simple /wish command can initiate the process, transforming a stated goal into a pull request. Builders should note that Windows is not officially supported, though WSL2 is functional. The migration from older plugin-era releases requires manual cleanup of residual files.

Caveats and source limits

The source material indicates that Windows is not a supported operating system, although WSL2 is functional. The retirement of legacy components like the Orca plugin and MCP server means that users still relying on these features will need to migrate to alternative solutions or manage them independently. The exact process for manual cleanup of plugin-era leftovers is detailed in the source but requires careful attention from the developer. No pricing information or specific performance benchmarks for v6 were provided in the source material. The release date is indicated as August 15, 2026, which is in the future.