-
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Git stores history. Rune stores understanding.
Rune Context is a lightweight, local-first repository context protocol for code LLMs.
Rune helps coding agents understand large codebases without repeatedly consuming thousands of lines of source code.
Humans do not understand repositories by reading every file.
Instead, developers rely on:
- architecture documents
- dependency relationships
- coding conventions
- feature maps
- recent changes
Modern code LLMs often lack these layers and repeatedly re-read the same files, consuming massive amounts of context.
Rune provides a persistent understanding layer for repositories.
Every repository should contain two important folders:
.git/
.rune/
.git/ explains:
What changed?
.rune/ explains:
What does the codebase mean?
Git stores history.
Rune stores understanding.
Rune works offline.
No cloud.
No accounts.
No servers.
Everything inside .rune/ uses:
- Markdown
- JSON
Nothing is hidden behind proprietary formats.
Rune itself does not depend on:
- Python
- Node.js
- Java
Language support is provided by plugins.
Rune updates only changed files.
Avoid full reindexing whenever possible.
Rune is intentionally small.
It is not:
- an IDE
- an agent framework
- a vector database
- a SaaS platform
- a replacement for Git
Rune provides context.
Agents provide intelligence.
.rune/
├── spec.md
├── architecture.md
├── conventions.md
├── graph.json
├── files/
├── features/
├── ownership/
├── sessions/
└── cache/
Initialize a repository:
rune initBuild context:
rune indexRefresh changed files:
rune updateRetrieve context:
rune context "Add Google OAuth"Validate repository health:
rune doctor- Core CLI
- Linux support
- macOS support
- Windows support
- Dependency graph
- Incremental indexing
- Python plugin
- TypeScript plugin
- Go plugin
- Feature maps
- Session memory
- Ownership maps
- Stable specification
- Plugin ecosystem
- Broad agent compatibility
- Why Rune Exists
- Installation
- Getting Started
- Commands
- Repository Format
- Architecture
- Plugin System
- Roadmap
- FAQ
- Contributing
Git answers:
What happened?
Rune answers:
What does it mean?
.git/ explains what changed.
.rune/ explains what the codebase means.
Rune Context — Git for repository understanding.
Git for repository understanding.
- RCP-001 — Repository Format
- RCP-002 — Plugin Protocol
- RCP-003 — Graph Format
- RCP-004 — File Summary Format
- RCP-005 — Feature Map Format
- RCP-006 — Ownership Metadata
- RCP-007 — Session Memory
- RCP-008 — Context Retrieval API
- RCP-009 — Incremental Indexing
- RCP-010 — Multi-Agent Coordination
Git stores history.
Rune stores understanding.