Method: Download Standalone Executable

Download the latest standalone executable for your platform from GitHub Releases. These executables have no dependencies and work out of the box.

Method: Install Executable Script

Install via the uv tool command:

uv tool install mimeogram

or, run directly with uvx:

uvx mimeogram

Or, install via pipx:

pipx install mimeogram

Method: Install Python Package

Install via uv pip command:

uv pip install mimeogram

Or, install via pip:

pip install mimeogram

Working with Simple LLM Interfaces

Use with browser chat interfaces and API workbenches when you want explicit, portable control over exactly which files are shared with a model. This is useful for interfaces with limited repository tooling and for workflows where uploaded files may have favorable pricing (for example, some project-oriented plans in provider-hosted web interfaces).

• Bundle files with mimeogram format instructions into clipboard.

  mimeogram create src/*.py tests/*.py --prepend-prompt

• Paste instructions and mimeogram into prompt text area in browser.

• Interact with LLM until you are ready to apply results.

• Request mimeogram from LLM and copy it from browser to clipboard.

  • Example: Claude Artifact

• Apply mimeogram parts from clipboard. (On a terminal, this will be interactive by default.)

  mimeogram apply

Note that, if you do not want the LLM to return mimeograms to you, most of the current generation of LLMs are smart enough to understand the format without instructions. Thus, you can save tokens by not explicitly providing mimeogram instructions.

Working with LLM Project Interfaces

Many LLM service providers now offer project-style workspaces that persist instructions and uploaded context across chats. When available, this pairs well with mimeogram by reducing prompt overhead while preserving structured file exchange.

In these cases, you can take advantage of the project instructions so that you do not need to include mimeogram instructions with each new chat:

• Copy mimeogram format instructions into clipboard.

  mimeogram provide-prompt

• Paste mimeogram prompt into project instructions and save the update. Any new chats will be able to reuse the project instructions hereafter.

• Simply create mimeograms for new chats without prepending instructions.

  mimeogram create src/*.py tests/*.py

• Same workflow as chats without project support at this point: interact with LLM, request mimeogram (as necessary), apply mimeogram (as necessary).

Remote URLs

You can also create mimeograms from remote URLs:

mimeogram create https://raw.githubusercontent.com/BurntSushi/aho-corasick/refs/heads/master/src/dfa.rs

Both local and remote files may be bundled together in the same mimeogram.

However, there is no ability to apply a mimeogram to remote URLs.

Interactive Review

During application of a mimeogram, you will be, by default, presented with the chance to review each part to apply. For each part, you will see a menu like this:

src/example.py [2.5K]
Action? (a)pply, (d)iff, (e)dit, (i)gnore, (s)elect hunks, (v)iew >

Choosing a to select the apply action will cause the part to be queued for application once the reivew of all parts is complete. All queued parts are applied simultaneously to prevent thrash in IDEs and language servers as interdependent files are reevaluated.

Filesystem Protection

If an LLM proposes the alteration of a sensitive file, such as one which may contain credentials or affect the operating system, then the program makes an attempt to flag this:

~/.config/sensitive.conf [1.2K] [PROTECTED]
Action? (d)iff, (i)gnore, (p)ermit changes, (v)iew >

If, upon review of the proposed changes, you believe that they are safe, then you can choose p to permit them, followed by a to apply them.

We take AI safety seriously. Please review all LLM-generated content, whether it is flagged for a sensitive destination or not.

Default Location

Mimeogram creates a configuration file on first run. You can find it at:

• Linux: ~/.config/mimeogram/general.toml

• macOS: ~/Library/Application Support/mimeogram/general.toml

• Windows: %LOCALAPPDATA%\\mimeogram\\general.toml

Default Settings

[apply]
from-clipboard = true    # Read from clipboard by default

[create]
to-clipboard = true      # Copy to clipboard by default

[prompt]
to-clipboard = true      # Copy prompts to clipboard

[acquire-parts]
fail-on-invalid = false  # Skip invalid files
recurse-directories = false

[update-parts]
disable-protections = false

Why Mimeogram in an Agentic World 💡

• Portable, provider-agnostic format for sharing and applying multi-file changes.

• Works in web interfaces and chat surfaces that do not expose local filesystem tools.

• Useful when you want explicit, auditable context selection instead of full-repository agent access.

• Supports batch exchange workflows, including scenarios where uploaded files can be cheaper than repeated API context transmission.

Technical Benefits ✅

• Preserves hierarchical directory structure.

• Version control friendly. (I.e., honors Git ignore files.)

• Supports async/batch workflows.

Platform Neutrality ☁️

• IDE and platform agnostic.

• Works with and without provider-specific agent tooling.

• Useful with both project-enabled and non-project chat interfaces.

Comparison of General Approaches ⚖️

Notes:

• No single column is universally best.

• Mimeogram is designed to complement agentic tools, especially when you need explicit scope control or provider portability.

Comparison with Similar Tools ⚖️

• ai-digest

• dump_dir

• Gitingest

• Repomix

Mimeogram is unique among file collection tools for LLMs in offering round-trip support - the ability to not just collect files but also apply changes proposed by LLMs.

Full Comparison of Tools