Skip to main content
Glama
context-attachment-manager

context-attachment-manager

What it does

An agent normally sends every earlier image again with each message, so a long chat with many images gets slow and can stop going through. This plugin numbers each image (IMG-001, IMG-002, …) and sends earlier ones as short placeholders instead:

  • The model fetches what it needs: when it has to look at an earlier image again, it gets the original back by its ID.

  • It can tell images apart: the model notes one line on what each image shows, plus your comments on it. These stay in the placeholders, also after the chat is compacted.

  • The cache keeps working: a placeholder is written once and then stays the same, so the earlier chat is still read from the model's prompt cache. See the design.

  • Nothing is deleted: your original images and chat history stay as they are.

It is on by default; you do not need to open the panel. Typical uses: image and video creation, scanned documents, computer and browser use.

Related MCP server: multimodal-mcp

Install

Send this to your agent. It identifies its platform and installs the right setup:

Install Context Attachment Manager for me, following https://github.com/chipfighter/context-attachment-manager/blob/main/INSTALL.md

Then restart the agent (in Claude Desktop, start a new Code session). See supported agents and installation, updates and uninstall.

The panel, when you want control

  • Find an image by a detail or a comment you remember, like "rainy night" or "best face".

  • Keep a reference in view: open an image and check Send every turn.

  • Choose images yourself: turn off Auto-select and pick what goes with your next message.

In Codex, open Context Assets in the task's side panel. In Claude Desktop's Code tab, the panel opens automatically when there are images; type /cam to bring it back.

Privacy

The plugin runs locally. Your original images and chat history stay on your computer; requests go to the service your agent already uses.

How we tested

In Codex, a chat with nine keyframes grew to 42.4 MB and could not be sent after a restart or a compaction; with the plugin the same requests were 0.12 MB. See the Codex comparison and Claude Code long-task comparison for the results and reproduction steps.

Design: keep the cache working

Model services cache the start of a chat. When a request begins exactly like the one before, that part is read from the cache, which is faster and much cheaper. When something early in the chat changes, everything after the change is processed again.

Any way of making a long chat smaller has to change something. The plugin makes its change as late in the chat as it can:

  • A placeholder is written once: an image becomes a placeholder in the turn after it appeared, so only the rest of that one turn is processed again. After that the placeholder stays the same from request to request.

  • Fetching changes nothing earlier: the original is added at the end of the current turn, and its placeholder stays where it is. Whichever image the model picks, and however many the chat holds, everything before the current turn is still read from the cache.

  • The model gets the original back: not a smaller copy, and not a summary of it.

This is not free. After a turn with images, the rest of that turn is processed again once, and the model writes a short line for each new image. Changing an old image in the panel (unchecking it, checking it again, Send every turn) changes the chat at that image, so what follows it is processed again once. In our long-task comparison in Claude Code, 87% of the input was read from the cache with the plugin and 91% without it.

The third row of the first figure is also what an agent's own compaction does, and what clearing old tool results on the API side does (Anthropic's context editing, for example): early content is removed, and what follows is processed again.

Works with

Codex and Claude Code are tested, and Codex and Claude Desktop also have the panel. The other agents below are supported through adapters written from their code and docs, but we have not tested them live yet. If you use one of them, please tell us how it went, whether it worked or not.

Agent

What it is

Support

Codex

OpenAI's coding agent, desktop and CLI

Auto-select + panel, tested

Claude Code

Anthropic's coding agent, desktop and CLI

Auto-select + panel (desktop), tested

WorkBuddy

Tencent's desktop AI work assistant, with CodeBuddy inside

Auto-select, not tested yet

OpenCode

Open-source terminal coding agent for any model provider

Auto-select, not tested yet

Gemini CLI

Google's open-source terminal agent

Auto-select, not tested yet

pi

Minimal, extensible terminal coding agent

Auto-select (pi extension), not tested yet

DeepSeek Harness

DeepSeek's agent harness where everything is a plugin

Auto-select (dsh plugin), not tested yet

Qwen Code

Qwen's open-source terminal agent

Auto-select, not tested yet

Cline

Open-source coding agent for VS Code, JetBrains and the terminal

Auto-select, not tested yet

Kilo Code

Open-source coding agent for VS Code, JetBrains and the terminal

Auto-select, not tested yet

goose

Open-source agent for desktop and terminal, extended with MCP

Auto-select, not tested yet

Cherry Studio

Open-source desktop chat client for many models

Auto-select, not tested yet

Setup for these agents: INSTALL.md. To connect another agent, see ADAPTERS.md.

FAQ

Why do Codex and Claude Code get slow in a long chat with many images?

The agent sends every earlier image again with each message, so a long chat with many images gets slow and can stop going through. In Codex, a chat with nine keyframes grew to 42.4 MB and could not be sent after a restart or a compaction; with Context Attachment Manager the same requests were 0.12 MB.

Does Context Attachment Manager break the prompt cache?

Only a little. A placeholder is written once and then stays the same, and a fetched image is added at the end of the current turn, so earlier turns are still read from the cache. After a turn with images, the rest of that turn is processed again once. In our long-task comparison in Claude Code, 87% of the input was read from the cache with the plugin and 91% without it.

How is it different from compaction, or from shrinking the images?

Compaction and dropping early history remove the early part of the chat, and shrinking the images changes it. Either way nearly the whole chat is processed again, and the model is left with a summary or a smaller copy. With Context Attachment Manager, only the rest of the previous turn is processed again, and the model gets the original image back by its ID.

Can the model still see an earlier image?

Yes. Every image has an ID such as IMG-001, and the model fetches the original when it needs to look at it again, also after the chat is compacted.

Are my images deleted, or sent anywhere else?

No. The plugin runs on your computer. Your original images and chat history stay as they are, and requests go to the service your agent already uses.

Which agents does it work with, and is it free?

Codex and Claude Code are tested. WorkBuddy, OpenCode, Gemini CLI, pi, DeepSeek Harness, Qwen Code, Cline, Kilo Code, goose and Cherry Studio are supported through adapters that we have not tested live yet. It is free and open source under the MIT license.

How do I install Context Attachment Manager? Do I need a terminal?

No. Send your agent the one sentence in Install above: it identifies its platform and runs the setup itself, and you only restart the agent afterwards (in Claude Desktop, start a new Code session). In Codex you can also install it from the Plugins page with a few clicks. If you prefer to do it by hand, it takes one command in Codex and two claude commands in Claude Desktop; see INSTALL.md.

Available Tools

1 tool
cam_view_imageView omitted imagesA
Read-only

View the originals of one or more omitted images in this task. Omitted images appear in the conversation as "[Image IMG-xxx omitted…]". Call it only when an answer needs to look at an image and what you said about it before is not enough; the originals are included only in this turn.

Inputs: ids (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (retrieving original image content for omitted images) is stated precisely, including when not to call it.

    Naming Consistency4/5

    The name follows a clean namespaced verb_noun snake_case pattern (cam_view_image) with a clear prefix. With a single tool there is no cross-tool consistency to verify, so it cannot be judged fully predictable as a set.

    Tool Count2/5

    A single tool is very thin for a server whose name implies managing context attachments. There is no way to enumerate omitted images or inspect their metadata, so the surface feels under-scoped rather than deliberately minimal.

    Completeness2/5

    The only operation is viewing an image's original content; there is no listing of omitted images, no metadata or dimension lookup, and no lifecycle operations for attachments. Agents hitting an omitted image that they cannot reference by ID have no fallback path.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Gives any MCP client (OpenCode, Claude Code, Claude Desktop, Cursor, etc.) the ability to process images by automatically converting them to text descriptions using a vision model, so that text-only LLMs can handle image-based queries.
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      A local MCP server that enables Claude Code and Claude Desktop to generate and edit images via OpenAI's Images API, saving finished files into the project and returning previews for iterative refinement.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to generate and edit images with GPT Image by relaying prompts through a local Codex CLI signed in with a ChatGPT plan, saving results to disk and returning them inline with no OpenAI API key required.
      48 npm
      1
      MIT