所有資料存放在 Supabase 的 pgvector 上,upsert 以穩定的文件 ID 為鍵,重新匯入時直接取代舊切片,而非層層堆疊。每次操作都記錄來源 ID,隨時都能追溯哪些內容被嵌入、發生在什麼時間點。
運作方式
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
依據穩定的文件 ID 進行 Upsert,確保重新匯入文件時替換舊的分塊而非產生重複。
pending
使用餘弦距離與元數據篩選條件,檢索與查詢最相近的分塊。
pending
記錄每一次插入、更新與檢索及其來源 ID,確保整個流程的可審計性。
pending
輸出範例
json
// Sample output
// (generated when the pipeline finishes)
Run insert, upsert, and retrieval over a Supabase pgvector store with stable IDs and a logged audit trail.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.