Pinecone 2.0 — Edo Liberty, Pinecone
Pinecone’s Nexus packages persistent company context behind an agent-facing query layer. The useful idea is to maintain goals, decisions, tables, and indexes once instead of rediscovering them per session.
Pinecone presents Nexus as a persistent knowledge layer with connectors, topic-specific contexts, manifests, knowledge files, tables, indexes, and NoQL queries. Its code-oriented interface reportedly reduced tool instructions from **about 150,000 tokens** to **under 1,000**.
For company agents, separate durable organizational knowledge from each task prompt. Let domain owners define what must be tracked, update stale facts as sources change, and give agents a compact interface with explicit time or token budgets.
Pinecone presents Nexus as a persistent knowledge layer with connectors, topic-specific contexts, manifests, knowledge files, tables, indexes, and NoQL queries. Its code-oriented interface reportedly reduced tool instructions from **about 150,000 tokens** to **under 1,000**. For company agents, separate durable organizational knowledge from each task prompt. Let domain owners define what must be tracked, update stale facts as sources change, and give agents a compact interface with explicit time or token budgets. The reported early-access results include **77–90% token reduction** and **20–77% faster execution**, plus accuracy gains, but the transcript provides no evaluation design or task-level breakdown. Nexus was moving from early access to public preview.
Nexus turns the shared-context proposal into a concrete persistent knowledge service and suggests that a compact code interface can sharply reduce prompt overhead. The reported efficiency and accuracy gains strengthen the operational case, but remain provisional without evaluation detail. Against prior candidates, it leaves provenance, retention policy, permissions, and human ownership of updates as necessary surrounding controls.