Filesystem Tools Through MCP
Once the system can work with real files, the interaction starts to feel less like prompting a chatbot and more like collaborating with a software environment.
I added an Electron wrapper so the prototype can expose filesystem capabilities to the LLM through the MCP layer.
This changes the interaction in a concrete way. The system is no longer only responding on screen; it can create and manipulate persistent local artifacts.
In one example, I asked the system to create a Hello World ASP page like it was 1996 and save it to a folder. The prototype shows the whole path: the prompt, the available tools, the model's reasoning and tool calls, and the final folder contents card.
Clicking default.asp opens another card with the generated file contents. From there, the file can be opened in the default editor, downloaded, or zipped together with the rest of the folder.
Navigation is still restricted to the agent-files directory, but even with that constraint the prototype is doing work a standard chat interface usually leaves outside the system.
