Interactive demo: pinned sources only. Imports and visitor keys are off.
This host has no durable database, so anything stored here can disappear on the next cold start.
This shared demo accepts no visitor imports or model keys. The seeded source remains available without a key, and its extracts are cited. A generated answer is only available on a properly configured product host. Do not submit private data to this demo.
Ask a source. See exactly where the answer came from.
Ask the pinned p-queue README anything. Every sentence of the answer cites a passage you can open, and when the README doesn’t say, it tells you.
Every sentence cited
Refuses when the source is silent
Cited extracts without a model key
How do I change shared configuration while jobs are still queued?
sindresorhus/p-queue, README.md
.pause()
Put queue execution on hold.
.onPendingZero()
Returns a promise that settles when all currently running tasks have completed.
Useful when you want to drain in-flight tasks before mutating shared state.
queue.pause(); await queue.onPendingZero();
.onIdle()
Settles when the queue is empty and all promises have completed.
Answer
Pause the queue so nothing new starts2, then wait for the tasks already running to finish before you change shared configuration1. Queued jobs stay queued until you call queue.start().
1.onPendingZero(), README
2.pause(), README
Two README passages were used, and every sentence of the answer points at one of them.
Example: asked “How do I change shared configuration while jobs are still queued?”, IntelliRAG answers that you should pause the queue, then await onPendingZero before changing shared configuration, citing the README’s .pause() and .onPendingZero() sections.
What’s inside
Each feature plays what it does. Pick one to open it for real.
Ask
Call queue.pause() so no new task starts2, then await queue.onPendingZero() until the running ones settle1.
1
.onPendingZero()Drain in-flight tasks before mutating shared state.
2
.pause()Put queue execution on hold.
Runs on the pinned p-queue README.
Questions people ask this source
Predicted from the document and from what visitors ask most. Or type your own below.
How an answer earns its citations.
Every passage gets a score.
Meaning (dense vectors) and exact words (BM25) are scored separately, then fused by rank.
A gate decides what may be cited.
A calibrated floor, plus a cut where scores fall away from the best match. Passages under it stay open for inspection, never for citation.
Each sentence points at its passage.
Generated answers cite [1], [2] for the passages above the gate. Without a model key you get those passages as extracts.
Or it refuses.
Ask something the source doesn’t cover and nothing clears the gate. You get “Not in the indexed corpus”, not a confident guess.
Retrieval, p-queue README
.add(fn, options?)
.pause()
.start()
.onEmpty()
.onIdle()
.onPendingZero()
.clear()
timeout
Gate
Not in the indexed corpus. Nothing cleared the gate, so nothing is cited.