Skip to content

brain_daemon_reingest

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever

Tool

brain_daemon_reingest

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever

Behavior

HTTP
POST /brain/daemons/:id/reingest

Arguments

Name
Type
Required
Description
id
string
•
Id of the ingestion daemon that owns these documents, as returned by brain_daemons_list
paths
array
•
Source paths to re-ingest, exactly as the daemon recorded them (a repo path such as docs/spec.md, a Drive file id, a ClickUp item id). 1-100 per call.

Response

Field
Type
Always
Description
runId
string
•
The run started to pick the cleared paths up — brain/daemon.run-completed for this id is what finishes the step. Null when no run was started (see triggered/triggerError).
cleared
array
•
Paths whose ingest state was cleared, so the next run will read them again from scratch
notFound
array
•
Paths this daemon has no ingest record for — usually a typo, or a document it never ingested
triggered
boolean
•
True when a run was started to pick the cleared paths up; false when the daemon is paused, a run is already in flight, or nothing was eligible
triggerError
string
—
Why no run was started; absent when one was
skippedPending
array
•
Paths left alone because they are in an unfinished batch; re-ask once that run has finished

Try it

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever.

When to use

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever

Example

Ask your agent something like this:

Force re-ingest of specific document paths for a daemon: clears their stored content hash and triggers a realtime run, so degraded or never-measured documents are re-extracted instead of hash-skipped forever.

The agent will invoke brain_daemon_reingest with these arguments:

{
  "id": "<id>",
  "paths": "<paths>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select