01 FILEOPS

2024 • DEV TOOLS

FILEOPS

Orchestrating agentic context by giving LLMs safe, structured access to the filesystem.

Context Engineering Node.js AST Parsing Local LLMs

Use arrow keys or buttons below to navigate

02 The Context Silo

PART I: THE PROBLEM 02 / 09

The Context Silo

Agents are smart but forgetful. Working across multiple projects (Context A -> Context B) meant manually copying context. There was no "Clipboard Manager" for AI memory.

The "Daisy Chain" Problem

You find an insight in a PDF report (Agent A) but want to apply it to your code (Agent B). Moving this insight is manual friction.

Ephemeral Memory

Agents have no persistence. Once you close the session, the knowledge is gone.

03 MCP for Power Users

PART II: THE SOLUTION 03 / 09

MCP for Power Users

Elevator Pitch:
A Model Context Protocol (MCP) tool allowing agents to Read/Write/Zip/Search and "Teleport" context between sessions via a persistent SQLite memory.

Capability	Traditional Context	FileOps (MCP)
Persistence	Session only.	SQLite Backed Meta-Memory
Cross-Project	Impossible.	"Quick Save" / "Quick Load"

Core Verbs

`learn(meta)`: Save insight to DB.
`remember(query)`: Vector search DB.
`teleport(ctx)`: Move context between agents.

04 Architecture

PART III: TECHNOLOGY 04 / 09

Architecture

A Node.js server exposing JSON-RPC endpoints to the Agent.

Interface: MCP (Model Context Protocol).
Storage: Local SQLite for file metadata & memory.
Action: NodeJS `fs` module for actual file ops.

// The "Teleport" Logic
/*
User: "FileOps, save this TSLA report comparison."
Agent -> FileOps.save("tsla_report_q3", content);

... switch to Cursor IDE ...

User: "FileOps, load the TSLA report."
Agent -> FileOps.load("tsla_report_q3");
> Returns structured summary from SQLite
*/

05 The MCP Era

PART IV: EVOLUTION 05 / 09

The MCP Era

Standardization

"FileOps was a precursor to the Model Context Protocol (MCP). What I hackily built in Node.js is now a standardized JSON-RPC spec supported by Anthropic and others, validating the need for 'Tool Use' as a first-class citizen."

06 Power User Impact

PART V: RESULTS 06 / 09

Power User Impact

Efficiency

10x

Faster context switching.

Control

Full

Granular file access.

Status

Tech Demo

Proving ground for MCPs.

07 Architecture Diagram

PART VI: VISUALS 07 / 09

Architecture Diagram

🕸️

(Diagram archived)

08 Technical Stack

APPENDIX 08 / 09

Technical Stack

Runtime

Node.js

Async I/O for filesystem ops.

Parsing

Babel

AST manipulation.

Integrations

OpenAI SDK

Tool calling interface.

09 STATUS: ARCHIVED

STATUS: ARCHIVED

Superseded by MCP servers, but foundational for my understanding of agent inputs.

Back to Playground

FileOps

Project presentation