Blob Reading

ci-blob:// URIs appear in graph query results when a payload is too large to inline. This skill covers safe resolution patterns to extract only the data you need.

---

When to Use blob_read

Use blob_read only when you need a specific payload from a graph node. Most Cypher queries return structured metadata that is sufficient without resolving any blobs.

Do resolve a blob when:

• You need the full input or output of a specific tool call
• You need the content of a specific assistant turn
• You need a specific field that is stored as a blob URI

Do NOT resolve a blob when:

• You are counting events, listing sessions, or summarizing metadata
• The graph query already returned the structured fields you need
• You are doing broad exploration — scan metadata first, resolve only if required

Most queries don't need blobs. Always exhaust what the graph returns before resolving.

---

How to Resolve a Blob

Follow these four steps to safely resolve a ci-blob:// URI:

Step 1 — Identify the URI Locate the ci-blob:// URI in the graph query result. It will appear as a string value in a node property.

Step 2 — Call blob_read Pass the full URI to the blob_read tool:

blob_read(uri="ci-blob://session_id/key")

Step 3 — Get the file path back blob_read returns {"path": "...", "source": {"name", "url", "origin"}} on success — a local file path where the blob content has been written, plus the endpoint that answered (origin is source, destination, or ). The file is temporary and exists only for this session. ALWAYS state which a blob was fetched from when reporting.