AI agents love markdown. Your project folder....Not so much
Today, I’m excited to share a project I’ve been working on—well, v1 at least. I have a laundry list of ideas for where to take this next, but let’s start with the "why."
The Problem: Markdown Clutter
When I work with AI coding agents, I have a specific workflow: I use Markdown files as the intermediary.
Requirements/Ideas: I write them in Markdown for the agent to generate proposals.
Investigations: I ask the agent to output bugs, proposals or findings into a Markdown file.
This process is addresses a lot of issues in working with AI—it drastically reduces AI hallucinations and provides a clearer picture to me as to what will be accompllised. The drawback? My project directories quickly become a digital junk drawer. It gets tedious constantly moving, copying, or deleting files I don't want checked into version control.
The Solution: The Briefcase
I needed a way to keep my workspace clean without losing the benefits of my Markdown workflow. So, I built The Briefcase.
The Briefcase is an MCP server that runs as process within the Agent itself. It acts as a file courier. It exposes a curated set of files to your agents through a structured API, without them ever needing to touch your underlying local directory structure.
Key Features:
Decoupled Storage: Agents can read, create, and update files that don't live in your project’s local directory.
Cross-Project Sharing: Use the same context files across multiple projects and different agents.
Universal Compatibility: Works with Claude Code, GitHub Copilot, or any MCP-compatible client.
Try It Out
You can grab the code here and take a look at how it works:
I’m already using this in both my personal and professional workflows, and it has made a huge difference. If you give it a spin, let me know what you think—I’m eager to hear your feedback!
No comments yet. Be the first to comment!
To leave a comment, please log in.