Show HN: Segue – Save context in one AI, load it in another by a short handle
Works with Claude · ChatGPT · any MCP client Hand context fromone AI to the next. Save a block of context in one assistant and get a short handle back. Load it by that handle in another — no copy-paste, no re-explaining.
- ▪Works with Claude · ChatGPT · any MCP client Hand context fromone AI to the next.
- ▪Save a block of context in one assistant and get a short handle back.
- ▪Load it by that handle in another — no copy-paste, no re-explaining.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,586 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
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 | Segue |
| Canonical URL | https://segue.ai/ |
| Publication time | Tue, 28 Jul 2026 12:27:05 +0000 |
| Retrieval time | 2026-07-28T12:34:46.737Z |
| Last seen | 2026-07-28T12:34:46.737Z |
| 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 | MuhLGamPRm4E · 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
Works with Claude · ChatGPT · any MCP client Hand context fromone AI to the next. Save a block of context in one assistant and get a short handle back. Load it by that handle in another — no copy-paste, no re-explaining. Your context, carried across tools. Start free How it works Claude ChatGPT Cursor Any MCP client The problem Every AI keeps your work in its own silo You plan in one assistant, build in another, and draft in a third. Each one holds real working state — the brief, the constraints, the decisions so far. None of them will hand it to the next. So the state of your work gets rebuilt from memory, every time you switch tools. That tax is small enough to pay once and large enough to feel every day.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Segue.
Discussion
0 commentsMore from Segue
