Cross-Agent Context & Omni-Channel Handoff

​

How it works

• session(name) loads the cloud index with that name into a local session (no re-embedding).
• push_index() writes the session back to the cloud, creating or replacing that index.

​

Example

from moss import DocumentInfo, MossClient

client = MossClient(MOSS_PROJECT_ID, MOSS_PROJECT_KEY)

session = await client.session(index_name="conv-123")
await session.add_docs([
    DocumentInfo(id="turn-1", text="Customer reported a duplicate $49.99 charge."),
    DocumentInfo(id="turn-2", text="Agent confirmed a refund in 3-5 business days."),
])
await session.push_index()

session = await client.session(index_name="conv-123")
print(f"{session.doc_count} documents loaded")

results = await session.query("status of the refund", QueryOptions(top_k=3))
for doc in results.docs:
    print(f"{doc.id} score={doc.score:.3f} {doc.text}")

await session.add_docs([
    DocumentInfo(id="turn-3", text="Customer confirmed the refund posted to their statement."),
])
await session.push_index()

​

Semantics

• push_index() creates or replaces the cloud index of that name. Readers see the most recent completed push.
• session(name) loads the stored index directly; documents keep their pushed embeddings, with no re-embedding.
• All participants must use the same embedding model. Passing a model_id that differs from the stored index raises an error.

​

Use cases

• Omni-channel - voice, chat, and email handlers share one index keyed by conversation or customer ID.
• Agent escalation - a frontline agent pushes; a specialist or human agent opens the same index with the full history.
• Multi-device - a session continues when the user moves from one device to another.
• Multi-agent pipelines - specialized agents (router, retrieval, reasoning, review) pass state through one named index; each read and write is a local in-memory operation rather than a network call.

​

Related