mirror of
https://github.com/spacedriveapp/spacedrive.git
synced 2026-11-02 21:35:12 -05:00
Two agents, and only one is the interface. The interface is a person and their agent in a harness over MCP. Filesystem intelligence is a Spacedrive-native loop over a local model, headless, producing rows. Reverses the earlier call that it should be a stateless batch pass. The arithmetic says otherwise: a few hundred thousand directories at local inference speed is days of continuous work, so uniform coverage is not affordable and choosing where to spend attention is the feature rather than an optimisation. Hierarchy pushes the same way, since a parent's annotation wants its children's first. The loop calls the same tools shipped over MCP. One definition, two consumers, so it is a client of the public surface with no privileged access and swapping in a frontier model is configuration. That also makes it a completeness test: if the native agent needs something MCP does not expose, the surface is wrong and it fails loudly. MCP therefore lands before the loop rather than beside it. LM Studio and Ollama first, both over OpenAI-compatible chat completions.