Hi HN Rune – A software intelligence runtime for AI coding assistants
Cursor, Codex, Claude Code — they all read your codebase cold, every session, and forget everything when it ends. Rune is the thing that runs underneath them, continuously, so every session starts already knowing your codebase instead of re-deriving it. Persistent — understanding survives past any single session.
- ▪Cursor, Codex, Claude Code — they all read your codebase cold, every session, and forget everything when it ends.
- ▪Rune is the thing that runs underneath them, continuously, so every session starts already knowing your codebase instead of re-deriving it.
- ▪Persistent — understanding survives past any single session.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,328 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/thecolourfoundation/rune |
| Publication time | Mon, 10 Aug 2026 17:39:22 +0000 |
| Retrieval time | 2026-08-10T17:50:42.056Z |
| Last seen | 2026-08-10T17:50:42.056Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | QduwsxIT5-Dv · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Rune The Software Intelligence Runtime. Cursor, Codex, Claude Code — they all read your codebase cold, every session, and forget everything when it ends. Rune is the thing that runs underneath them, continuously, so every session starts already knowing your codebase instead of re-deriving it. Without Rune: flowchart LR A1["New AI session"] --> A2["Reads files cold"] A2 --> A3["Reasons, answers"] A3 --> A4["Session ends"] A4 -.->|"understanding lost"| A1 Loading With Rune: flowchart LR B1["Code changes"] --> B2["rune watch rebuilds automatically"] B2 --> B3["Understanding always current"] B3 --> B4["New AI session"] B4 --> B5["Queries Rune over MCP"] B5 --> B6["Evidence-backed answer, cited to file + line"] B6 -.->|"stays current"| B3 Loading What it does · How it works · Install ·…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.