Rosetta is a meta-prompting, context engineering, and centralized knowledge management for AI coding agents. R2 is the production release that moves teams from individual developer prompting to governed, organization wide AI assisted development.
- Zero friction developer onboarding through HTTP mode and IDE plugins
- Multi agent execution with specialized roles and review gates
- Architecture aware AI development through automatic pattern extraction
- Modular instructions aligned with native coding agent capabilities
- Structured workflows for requirements, prompts, and debugging
- HTTP mode. Developers connect to Rosetta over HTTP with OAuth. No local installation, no CLI setup, and no dependencies on developer machines. Add one JSON config to the IDE and start working.
- Plugins for Claude Code and Cursor. Installation is available from IDE marketplaces with one click. Additional IDE plugins are planned.
- Reduced bootstrap size. Smaller initial prompts load faster and use less context, leaving more room for the actual task.
- Subagent orchestration. Work is split into phases handled by specialized agents. One can implement while another reviews, potentially on a different model. Architect, engineer, reviewer, and validator each work with focused context and a clear scope.
- Deterministic plan manager. Execution plans are tracked step by step with phase completion gates. It is in battle testing with limited scope and is designed to make AI work resumable and auditable.
- Large workspace handling. Repositories with more than 100 files are partitioned into scoped subagent tasks to prevent context overflow and keep quality stable at scale.
- Automated review gates. After implementation and testing, a separate reviewer agent checks the result against the spec before it reaches human reviewers.
- Automatic building block extraction. During repository initialization, Rosetta identifies recurring codebase patterns, such as how to create a controller, a domain service, or a data grid, and turns them into reusable templates for the agent.
- Project knowledge datasets. Each project builds a structured knowledge base that covers architecture, tech stack, dependencies, and conventions. This enables cross project flows where the agent understands how services relate to each other and improves work across multiple repos.
- Skills, rules, commands, workflows, and subagents are separated. Each instruction type maps to native coding agent features such as Cursor rules or Claude Code commands. Agents use built-in capabilities instead of workarounds.
- OSS, Grid, and custom split. OSS provides the foundation. Grid adds advanced workflows. Organizations can layer their own customizations without forking the core.
- Requirements documentation authoring. A structured workflow produces testable, atomic requirements with traceability. Those requirements then drive planning, implementation, and validation.
- Prompt authoring. Teams that create and maintain AI agent instruction sets now have a dedicated workflow with specialized subagents for each phase.
- Debugging skill. The agent investigates root cause before attempting a fix, which makes debugging more systematic and less dependent on guesswork.