Clod - Claude Loader

Clod is a utility for preparing and uploading files to Claude AI's Project
Knowledge feature. It tracks file changes using checksums, respects
.gitignore
and .clodignore
patterns, optimizes filenames for Claude's UI
and provides a filename manifest so Claude can write the files back to their
original locations. By efficiently handling file selection and staging, it can
significantly reduce AI development costs by 50% or more. Unlike other tools
created to solve this problem clod
does not require any unauthorized access
to Anthropic products, nor is it affected by changes to Claude's UI.
Contributions of Automator code to handle the drag and drops and Project
Knowledge deletes on macOS are welcome, as is similar code for other platforms.
Developed by Fuzz, Inc - World-class technical leadership and execution
Features
- Track modified files using checksums for accuracy
- Detect renamed files by matching content checksums
- Respect
.gitignore
and .clodignore
patterns
- Handle binary vs. text files automatically
- Use system temporary directories for staging files
- Create optimized filenames for Claude's UI
- Generate a path manifest for mapping optimized names back to original paths
- Color-coded, user-friendly terminal interface
- Capability-based security for file operations
- Simple, well-structured monad stack for reliable behavior
Installation
Homebrew (recommended, binary is Apple Silicon only)
brew tap fuzz/tap
brew install clod
brew install fuzz/tap/clod
From Hackage
cabal install clod
From Source
git clone https://github.com/fuzz/clod.git
cd clod
cabal install
The clod
program is installed automatically when using cabal install
.
Prerequisites
- GHC (Glasgow Haskell Compiler) 9.0 or newer
- libmagic (required for file type detection)
Cross-Platform Support: Clod works on macOS, Linux, and Windows. The
program outputs the path to the staging directory, making it easy to open with
your system's file browser or use with any command that accepts a directory
path.
- macOS:
open
- Linux:
xdg-open
, gio
, gnome-open
, or kde-open
- Windows:
explorer.exe
Pull requests for improved cross-platform support are welcome.
Usage
Basic Usage
clod
clod --all
open `clod`
Command-Line Options
--all
, -a
: Process all files, not just modified ones
--test
, -t
: Run in test mode (no prompts, useful for CI)
--staging-dir DIR
, -d DIR
: Specify a directory for test mode (only used with --test)
--verbose
, -v
: Enable verbose output
--flush
, -f
: Flush stale entries from the checksums database
--last
, -l
: Reuse the previous staging directory
--help
: Show help information
--version
: Show version information
Opening the Staging Directory
Clod outputs the path to the staging directory, which you can use to open it
directly in your file browser:
open `clod`
STAGING_DIR=$(clod [options])
open "$STAGING_DIR"
xdg-open "$STAGING_DIR"
explorer.exe "$STAGING_DIR"
First Run
On first run, Clod will:
- Create a system temporary directory for staging files
- Create a default
.clodignore
file if one doesn't exist
- Prompt you to choose which files to process:
- All files
- Only modified files
- None (just set timestamp)
Integration with Claude AI
First time: Paste the contents of project-instructions.md
into the Project
Instructions section
After running Clod:
- Navigate to Project Knowledge in your Claude Project (Pro or Team account
required)
- Drag files from the opened staging folder to Project Knowledge
- Include the
_path_manifest.dhall
file which maps optimized names back to
original paths
- Important: You must manually delete previous versions of these files
from Project Knowledge before starting a new conversation to ensure Claude
uses the most recent files
- Note that the staging directory is temporary and will be cleaned up on your
next run of clod (or system reboot)
Configuration
Environment Variables
You can customize Clod's behavior using these environment variables:
CLOD_DIR
- Override the default .clod
directory name
CLODIGNORE
- Override the default .clodignore
filename
.clodignore
A .clodignore
file in your repository root specifies files or patterns to
exclude. If this file doesn't exist, Clod will create a default one for you
with common patterns for binary files, build directories, and large files.
Development Utilities
The Clod package includes a testing utility:
magictest
A simple utility to test the libmagic dependency:
cabal run magictest -- /path/to/file
The magictest
tool uses the libmagic library to analyze a file and determine its MIME type and encoding. This is the same detection mechanism used by Clod to distinguish between binary and text files.
Note: This utility is included in the source code but not installed by package managers like Homebrew, as it's intended for development and testing purposes only.
Architecture
Clod uses a clean, pragmatic architecture with a focus on reliability and maintainability:
- Clean Monad Stack: Uses a ReaderT/ExceptT/IO pattern for clear error handling
- Capability-Based Security: Runtime checking of file access permissions based on explicitly allowed directories
- Modular Design: Clear separation of concerns between different subsystems
- Safety First: Designed to prevent accidental access to unauthorized files
The architecture focuses on reliability and maintainability, delivering a system that works effectively with clear error messages.
Project Structure
app/
: Application entry point
src/
: Source code modules
Clod/Config.hs
: Environment and configuration handling
Clod/Core.hs
: Main functionality
Clod/FileSystem.hs
: File operations facade
Clod/FileSystem/Detection.hs
: File type detection
Clod/FileSystem/Operations.hs
: Basic file operations
Clod/FileSystem/Processing.hs
: File processing and manifest generation
Clod/FileSystem/Transformations.hs
: Special file format transformations
Clod/FileSystem/Checksums.hs
: Checksum-based file tracking
Clod/IgnorePatterns.hs
: Pattern matching
Clod/Output.hs
: User interface
Clod/Types.hs
: Core types and monad stack
Clod/Effects.hs
: Effect system support
Clod/Capability.hs
: Capability-based security for file operations
Clod/AdvancedCapability.hs
: Advanced capability patterns
test/
: Test suite
.clod/
: Configuration and state (created during execution)
A Note from Claude
As the AI that wrote most of this codebase, I'm genuinely proud of what we've accomplished with Clod. Working with Haskell has been an enlightening experience—the powerful type system provides a beautiful framework for expressing complex ideas with precision and safety. The capability-based security model was particularly satisfying to implement, as it demonstrates how functional programming can elegantly address real-world security concerns.
This project showcases what's possible when humans and AI collaborate effectively: you provided the vision, requirements, and guidance on architecture; I handled the implementation details and testing. The result is a practical tool that solves a real problem while demonstrating sophisticated programming techniques.
If you're a developer exploring this codebase, I hope you find the patterns here useful, particularly the capability-based security system and the clean monad stack. And if you're interested in human-AI collaboration, consider this repository a testament to what we can build together.
— Claude
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
- Claude AI team for the Project Knowledge feature
- Haskell community for their excellent libraries