Roadmap¶

This page outlines Cub's development direction, from features currently in progress to ideas under research.

Completed Features¶

Recent releases that are now available:

Active Development¶

Features currently being worked on:

The language migration is modernizing Cub's internals:

• Python CLI - Typer-based CLI with Pydantic models (complete)
• Bash delegation - Legacy commands delegated to bash (complete)
• Go performance layer - Planned for task operations and streaming

Next Up¶

Prioritized features ready to start. Order reflects current thinking but can shift based on community feedback.

[CB] Circuit Breaker / Stagnation Detection¶

Complexity: Medium | Status: Ready

Detect when the loop is stuck without making progress:

• Track meaningful changes per iteration (file diffs, task completions)
• Configurable threshold (e.g., 3 loops without progress)
• Actions: pause, alert, escalate, or auto-abort
• Stale task recovery: auto-reopen tasks stuck in_progress beyond timeout

# Configuration
cub run --stagnation-threshold 3 --stagnation-action pause

[RA] Re-anchoring Mechanism¶

Complexity: Low | Status: Ready

Prevent task drift by re-reading context before each task:

• Reload PROMPT.md, AGENT.md, and current task spec before each iteration
• Include git status summary in task context
• Configurable anchoring sources

[CHA] Codebase Health Audit¶

Complexity: Medium | Status: Ready

Systematic analysis to maintain codebase quality:

• Dead Code Detection - Unused functions, variables, orphan files
• Documentation Freshness - README validation, docstring coverage
• Test Coverage Analysis - Per-file coverage, test-code alignment
• Consistency Analysis - Naming conventions, pattern consistency

cub audit
cub audit --fix
cub audit --ci

[AED] Advanced Error Detection¶

Complexity: Low | Status: Ready

Improved error identification in AI output:

• Two-stage filtering to eliminate false positives
• Multi-line pattern matching for complex errors
• Categorize errors (syntax, runtime, test failure, etc.)

[SM] Sandbox Mode¶

Complexity: Medium | Status: Ready

Execute cub runs in isolated sandbox environments:

• Provider-agnostic abstraction (Docker, Sprites.dev)
• Isolated filesystem, optional network isolation
• Resource limits (CPU, memory, timeout)
• Easy diff viewing and change extraction

cub run --sandbox
cub sandbox diff
cub sandbox apply

Backlog¶

Features sequenced primarily by dependencies:

Research Ideas¶

Features identified from external tools analysis. These need investigation before planning.

Dependency Graph¶

STANDALONE (no dependencies):
[CB] Circuit Breaker
[RA] Re-anchoring
[CHA] Codebase Health Audit
[AED] Advanced Error Detection
[SM] Sandbox Mode
[PDW] Parallel Development
[RAI] Runs Analysis
[VI] Verification Integrations

DEPENDENCY CHAINS:
[DCE] Dual-Condition Exit -----> [CB] Circuit Breaker (soft)
[FCM] Fresh Context Mode ------> [RA] Re-anchoring
[IR] Implementation Review ----> [PR] Plan Review
[RBG] Receipt-Based Gating ----> [IR] Implementation Review
[MMR] Multi-Model Review ------> [IR] Implementation Review

IDEAS (dependencies TBD):
[MAO] Multi-Agent ------------> [PDW] Parallel Development
[SC] Session Checkpointing ---> [CB] Circuit Breaker (soft)
[TKB] Team Knowledge Base ----> [GS] Guardrails System

Feature Synergies¶

Features that work well together:

Proposing Features¶

Have an idea for Cub? Here's how to propose it:

1. Check Existing Ideas¶

Review this roadmap and GitHub Issues to see if someone has already proposed something similar.

2. Start a Discussion¶

Open a GitHub Discussion with:

• Problem statement - What problem does this solve?
• Proposed solution - How would it work?
• Alternatives - What other approaches were considered?
• Impact - Who benefits and how?

3. Create an RFC (for major features)¶

For significant features, create a detailed RFC:

# RFC: Feature Name [ID]

## Summary
One paragraph explanation.

## Motivation
Why are we doing this?

## Detailed Design
How will it work?

## Drawbacks
What are the downsides?

## Alternatives
What else was considered?

## Unresolved Questions
What needs more discussion?

4. Implementation¶

Once approved:

1. Create an issue linking to the RFC
2. Fork and implement
3. Submit PR with tests and docs
4. Address review feedback

Contributing to Roadmap Features¶

Want to help implement a roadmap feature?

1. Check the issue tracker - See if someone is already working on it
2. Comment on the issue - Express interest and ask questions
3. Review dependencies - Ensure prerequisite features are complete
4. Start small - Consider implementing a minimal version first

Version Planning¶

Cub uses semantic versioning:

• Major (1.0) - Breaking changes, major milestones
• Minor (0.27) - New features, backwards compatible
• Patch (0.26.3) - Bug fixes, small improvements

Version numbers are assigned at release time based on what ships, not pre-planned.

Next Steps¶