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.
This reinforces a shared, persistent context layer as separate infrastructure from individual prompts, with domain-owned updates and a compact agent interface. Nexus adds manifests, tables, indexes, and budget controls to that pattern, but its large efficiency and accuracy gains remain vendor-reported early-access results without task-level evaluation.