WeSearch

Show HN: nbpipe – A lightweight workflow runner for Jupyter notebooks

·1 min read · 0 reactions · 0 comments · 33 views
Show HN: nbpipe – A lightweight workflow runner for Jupyter notebooks
TL;DR · WeSearch summary

nbpipe is a tool designed to run sequences of Jupyter notebooks as workflows from the command line or JupyterLab. Users can create a workflow by defining a YAML file that specifies the order of notebook execution and expected outputs. The tool simplifies the process of managing and executing multiple notebooks in a structured manner.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
GitHub
Read full at GitHub →

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 publisherGitHub
Canonical URLhttps://github.com/ngafar/nbpipe
Publication timeSat, 16 May 2026 20:49:55 +0000
Retrieval time2026-05-16T21:10:19.063Z
Last seen2026-05-16T21:10:19.063Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterhB-z-9cWxxkJ
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

nbpipe Run sequences of Jupyter notebooks as a workflow from the command line or the JupyterLab sidebar. Installation pip install nbpipe Usage Create a .nbpipe/ directory at the root of your project and add a workflow YAML file inside it. # .nbpipe/my_workflow.yaml # Notebook paths are relative to the project root name: my_workflow steps: - notebook: prepare_data.ipynb output: data/processed.csv - notebook: train_model.ipynb Run it from the CLI: nbpipe run .nbpipe/my_workflow.yaml or from JupyterLab: Step fields Field Required Description notebook yes Notebook to run, relative to the project root output no File the notebook must produce — workflow fails if absent

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub