Show HN: Open-artifact – view and share your LLM docs and artifacts
Open Artifact Your coding agent writes a report, a design doc, a dashboard. Right now that lands as a file on your laptop that nobody else can see. The agent publishes, you get a link, you share it with the people who need to read it.
- ▪Open Artifact Your coding agent writes a report, a design doc, a dashboard.
- ▪Right now that lands as a file on your laptop that nobody else can see.
- ▪The agent publishes, you get a link, you share it with the people who need to read it.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,341 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/iBala/open-artifact |
| Publication time | Thu, 23 Jul 2026 20:03:44 +0000 |
| Retrieval time | 2026-07-23T20:11:52.789Z |
| Last seen | 2026-07-23T20:11:52.789Z |
| 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 | CG-sElnGv4of |
| 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
Open Artifact Your coding agent writes a report, a design doc, a dashboard. Right now that lands as a file on your laptop that nobody else can see. Open Artifact gives it a URL. The agent publishes, you get a link, you share it with the people who need to read it. They comment on the exact paragraph they are reacting to, and the agent reads those comments back and revises. You host all of it yourself. Publish from the agent. One command, or the bundled skill so the agent does it without being asked. HTML and Markdown. HTML runs in a sandbox with no access to your session. Markdown is rendered with headings, tables and syntax highlighting. Share deliberately. Private by default. Open it to named people, to everyone at your email domain, or to anyone with the link.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.