We're Using AI Wrong. The Chat Window Sucks
Chat windows are terrible interfaces for doing work. Clair, September 2026 AI chat windows are everflowing rivers where every leaf you drop into that river immediately floats away, and good luck finding it. Type something, the agent responds, and within seconds the answer scrolls up and out of sight.
- ▪Chat windows are terrible interfaces for doing work.
- ▪Clair, September 2026 AI chat windows are everflowing rivers where every leaf you drop into that river immediately floats away, and good luck finding it.
- ▪Type something, the agent responds, and within seconds the answer scrolls up and out of sight.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,910 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 | Stclair |
| Canonical URL | https://www.stclair.ai/blog/the-chat-window.html |
| Publication time | Tue, 22 Sep 2026 01:44:17 +0000 |
| Retrieval time | 2026-09-22T01:48:50.653Z |
| Last seen | 2026-09-22T01:48:50.653Z |
| 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 | 1PPa3Prj9XBQ · 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
We're Using AI Wrong. The Chat Window Sucks. Chat windows are terrible interfaces for doing work. Ken St. Clair, September 2026 AI chat windows are everflowing rivers where every leaf you drop into that river immediately floats away, and good luck finding it. Type something, the agent responds, and within seconds the answer scrolls up and out of sight. How often do you go hunting through your endlessly scrolling chat to try and find something that was said just a minute ago? It's almost like we WANT it to look like the Matrix. Never has a good designer said "Let's show the user all the different function calls the backend is making to show this webpage," but that's what a chat window does. It's a terrible UX. And it doesn't have to be.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Stclair.
Discussion
0 commentsMore from Stclair
