Triad – a dynamic, scriptable window manager for the River Wayland compositor
Triad is a dynamic window manager designed for the River Wayland compositor, focusing on separating display from policy. It allows for efficient window management through scriptable logic and supports various layout modes. With features like crash resilience and compatibility with popular shell ecosystems, Triad enhances user experience in managing windows.
- ▪Triad manages window placement while River handles the Wayland protocol.
- ▪It uses tags and rules to provide a flexible and efficient window management system.
- ▪Triad supports multiple layout modes and features a scrolling layout for improved workflow.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 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/greenm01/triad |
| Publication time | Sat, 16 May 2026 15:25:27 +0000 |
| Retrieval time | 2026-05-16T15:40:18.968Z |
| Last seen | 2026-05-16T15:40:18.968Z |
| 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 | QByZ1HkKlDIx |
| 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
Triad 2026-05-15-triad-demo.mp4 Triad is a dynamic window manager for Wayland, built for the River compositor. It separates display from policy: River handles the Wayland protocol while Triad manages window placement. This decoupling ensures resilience; if Triad restarts, your windows remain in place. Triad treats your session as flat data. Windows carry tags rather than living in a rigid hierarchy. This makes conditional logic efficient, turning window management into a scriptable engine. Need a screen lock? See LockMe. The Triad Triad is built on Tags, Rules, and IPC. Tags provide stable, concurrent labels for windows. Rules, written in KDL, provide declarative defaults. IPC exposes a snapshot of the model over a Unix socket.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.