Roadmap

Small steps. Stable foundations.

---

Vision

Rune aims to become the standard repository understanding layer for coding agents.

Just as Git standardized source control, Rune aims to standardize repository context.

The long-term vision is:

.git/
.rune/

where:

.git/

answers:

What changed?

and:

.rune/

answers:

What does the codebase mean?

---

Guiding Principles

Rune prioritizes:

• simplicity
• local-first design
• human-readable formats
• deterministic outputs
• cross-platform support

Complexity should be added slowly.

---

v0.1 — Foundation

Goal:

Build the smallest useful version.

Status:

🚧 In Progress

---

Core CLI

Commands:

rune init
rune index
rune update
rune context
rune doctor

---

Repository Format

Introduce:

.rune/

including:

spec.md
architecture.md
conventions.md
graph.json
files/
features/

---

Dependency Graph

Generate:

graph.json

to support selective loading.

---

Incremental Updates

Support:

rune update

without full reindexing.

---

Platform Support

• Linux
• macOS
• Windows

Architectures:

• amd64
• arm64

---

Single Binary

No dependency on:

• Python
• Node.js
• Docker

Installation:

curl -fsSL ... | sh

---

v0.2 — Language Plugins

Goal:

Move language complexity outside the core.

Status:

Planned

---

Plugins

Initial support:

• Python
• TypeScript
• Go

Examples:

rune-python
rune-typescript
rune-go

---

Framework Detection

Python:

• Django
• FastAPI

TypeScript:

• React
• Next.js

Go:

• Gin
• Echo

---

Improved Symbol Extraction

Support:

• functions
• classes
• interfaces
• methods

---

v0.3 — Feature Understanding

Goal:

Understand behavior, not just files.

Status:

Planned

---

Feature Maps

Generate:

.rune/features/

Example:

login
subscription
billing

---

Ownership Maps

Generate:

.rune/ownership/

Examples:

• frontend
• backend
• infrastructure

---

Session Memory

Track recently touched files.

Example:

{
  "files": [
    "auth.py",
    "user.py"
  ]
}

---

v0.4 — Repository Intelligence

Goal:

Improve context quality.

Status:

Planned

---

Context Ranking

Given:

Add Google OAuth

Rune should prioritize:

auth.py
user.py
settings.py

instead of traversing the entire graph.

---

Impact Analysis

Questions like:

What breaks if I change billing.py?

should become answerable.

---

Architectural Boundaries

Detect:

• cyclic dependencies
• layering violations
• anti-patterns

---

v0.5 — Multi-Agent Support

Goal:

Enable collaboration between coding agents.

Status:

Exploration

---

Ownership Metadata

Examples:

frontend/*
backend/*
database/*

---

Agent Boundaries

Possible agents:

• frontend
• backend
• infrastructure
• testing

---

Shared Context

Allow multiple agents to consume the same .rune/.

---

v0.6 — Ecosystem

Goal:

Integrate broadly.

Status:

Future

---

Compatible with:

• Claude Code
• Cursor
• Codex
• Gemini CLI
• Aider
• Roo Code

No special APIs should be required.

The interface is:

.rune/

---

v0.7 — Performance

Goal:

Handle very large repositories.

Status:

Future

---

Targets:

Repository size:

100,000+ files

Cold indexing:

<30 seconds

Incremental update:

<1 second

Memory usage:

<200 MB

---

v1.0 — Stable Specification

Goal:

Define the Rune Context Protocol.

Status:

Long-Term

---

Stable Format

Guarantee compatibility for:

spec.md
graph.json
files/
features/
ownership/

---

Plugin Ecosystem

Support dozens of languages.

---

Formal Specification

Document:

• repository format
• plugin protocol
• graph format
• summary structure

---

Broad Adoption

Target:

.git/
.rune/

becoming a familiar pattern in repositories.

---

Explicit Non-Goals

Rune will never become:

• an IDE
• a code editor
• a cloud service
• a vector database
• an agent framework
• an LLM provider

Rune provides context.

Agents provide intelligence.

---

Future Possibilities

These ideas are interesting but intentionally deferred:

• visual dependency graphs
• GitHub integrations
• VSCode extensions
• MCP adapters
• web interfaces

The core should mature first.

---

Success Criteria

Rune succeeds if developers stop thinking about it.

Just as developers rarely think about Git internals today, repository understanding should become ordinary infrastructure.

---

Philosophy

Git made history portable.

Rune aims to make understanding portable.

Git stores history.

Rune stores understanding.