volcengine's OpenViking Climbs +804 Stars to 30,754 Selling a Filesystem Instead of a Vector Store — Agents Browse Their Own Memory With ls, tree and find

GitHub·high signalXBlueskyLinkedInCopy link

OpenViking exposes memory, resources and skills as one virtual filesystem under a viking:// protocol, so an agent navigates its context with directory commands rather than opaque similarity queries, with content tiered into L0 abstract, L1 overview and L2 detail and loaded on demand. Release v0.4.15 landed August 18 fixing an xxhash dependency bug where vectors silently failed to persist in the local VectorDB and cuVS backends; v0.4.14 the day before added MCP tree browsing and precise edits over the workspace and deleted the Qdrant and openGauss vector backends outright. Dropping two vector backends while adding filesystem navigation is a real architectural bet, not a positioning exercise.