The next AI interface may not be a chatbot
Most AI agents today still live inside fixed surfaces. A web UI with buttons and screens someone designed in advance. They can answer questions, call tools, edit files, run commands, and generate content.
- ▪Most AI agents today still live inside fixed surfaces.
- ▪A web UI with buttons and screens someone designed in advance.
- ▪They can answer questions, call tools, edit files, run commands, and generate content.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,376 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 | Tomas Hajek |
| Canonical URL | https://hajek.no/posts/2026/next-ai-interface-not-chatbot |
| Publication time | Thu, 13 Aug 2026 02:37:27 +0000 |
| Retrieval time | 2026-08-13T03:59:17.528Z |
| Last seen | 2026-08-13T03:59:17.528Z |
| 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 | R6MxIIHddyp- · 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
The next AI interface may not be a chatbot. Most AI agents today still live inside fixed surfaces. A chat window. A terminal. A messaging app. A web UI with buttons and screens someone designed in advance. They can answer questions, call tools, edit files, run commands, and generate content. But the interface itself usually stays the same. I think that will change. The more interesting future is not just AI operating inside existing software. It is AI helping create the interface needed for the task in real time. Ask for a summary, and you get text. Ask to compare data, and the workspace turns into a table or chart. Ask to monitor something, and it creates a dashboard. Ask to organize a project, and it builds a small task board, note view, or custom workspace.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Tomas Hajek.
Discussion
0 commentsMore from Tomas Hajek
