Context Attachment Manager plugin
Plugin for Codex and Claude Desktop that keeps old images out of requests so a long chat with pictures does not stall
- 560 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- A local proxy sits between the client and the API and sees whole requests, images and auth headers included
- The installer edits ~/.codex/config.toml and a proxy block in ~/.codex/.env
- A bundled MCP server and hooks run inside every session where the plugin is enabled
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/context-attachment-managerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A local proxy sits between the client and the API and sees whole requests, images and auth headers included
- The installer edits ~/.codex/config.toml and a proxy block in ~/.codex/.env
- A bundled MCP server and hooks run inside every session where the plugin is enabled
This is third-party code. Review the repository files before installing.
What it does
Context Attachment Manager is a plugin that adds an image panel to long chats in Codex and Claude Desktop. When you iterate on images one after another, every message resends all the earlier ones, and after about a dozen the chat keeps reconnecting and never gets through. The plugin keeps old images out of the request and the model pulls back the ones it needs. Pinned images, such as a character reference, go with every message. The model briefly notes what each image shows and what you said about it, such as "too dark" or "best face". You can find an earlier image by description, filter by place or browse by turn, and a click opens it at full size. The notes stay available after the chat is compacted. A local engine on a loopback address does the work. It passes requests to the same endpoint the client used, with the same model and credentials. In the author's example a 24.9 MB request shrinks to 212 KB.
Who it is for. For people who iterate on generated images in Codex or in the Code tab of Claude Desktop and hit stalls in long chats.
Good fit when
- You refine frames or illustrations over dozens of iterations in one Codex chat and each message takes longer to send
- You need a picture from three days ago and only remember that it showed a rainy night
- A Codex chat with images keeps reconnecting and you cannot continue working in it
- The chat gets compacted and you want the model to keep its index of earlier images
Not a fit when
- Your chats have no images or just one or two: nothing accumulates, so there is nothing to save
- You reach Claude Code through Bedrock, Vertex or Foundry: the plugin does not handle that transport
- Ports 17891 and 17892 on your machine are taken by other programs and cannot be freed
- You use Claude Code in a plain terminal without the Claude Desktop app: the panel lives in the app's Code tab
Example request
Install Context Attachment Manager following INSTALL.md and tell me what I have to do by hand afterwardsLimitations
- The plugin targets the Codex app and the Code tab in Claude Desktop. The author tested Codex desktop 26.1013 and Claude Desktop with Claude Code 2.1.299.
- Claude Desktop without an installed Codex needs Node.js 24 or newer.
- A custom gateway must accept image input and tool calls and speak the client's native format: Responses for Codex, Anthropic Messages for Claude Code. There is no conversion between formats.
- Bedrock, Vertex and Foundry keep their own transport and are not managed by the plugin.
- Ports 17891 and 17892 on the local address must be free. An older plugin copy cannot serve the registered routes, so update both platform versions.
- The project is young: the manifest says version 0.9.0.
How to disable. The repository ships scripts/uninstall.sh and scripts/uninstall.ps1, and INSTALL.md describes the removal. For Codex the plugin edits ~/.codex/config.toml after backing the file up, and disabling restores the original endpoint. In Claude Desktop it is installed with `claude plugin install` and can be removed from the Plugins tab.
FAQ
How do I install Context Attachment Manager in Codex?
On macOS and Linux run `curl -fsSL https://github.com/chipfighter/context-attachment-manager/releases/latest/download/install.sh | sh`, on Windows in PowerShell `irm https://github.com/chipfighter/context-attachment-manager/releases/latest/download/install.ps1 | iex`. Without a terminal, add the marketplace `chipfighter/context-attachment-manager` on the Plugins page, install the plugin and click Enable plugin in the panel. Then restart Codex.
How do I open the image panel?
In Codex open the task's side panel, add a tab with the plus and pick Context Assets under Plugins and MCPs. In Claude Desktop the panel opens by itself next to the chat in the Code tab once the session has images, and /cam brings it back.
How do I pin an image so it goes with every message?
Click the image in the panel and tick Send every turn. To choose images yourself, turn off the Auto-select switch at the bottom of the panel.
Where does the plugin send my images?
Requests go to the same endpoint as without the plugin, with the client's model and credentials. The plugin sends nothing beyond the usual Codex and Claude requests. The engine listens on loopback only.
Does it work through a custom gateway?
Yes, if the gateway accepts images, tool calls and the client's native format. For Codex, single-line openai_base_url and provider base_url settings in the user's config.toml are supported. For Claude Code it uses the original ANTHROPIC_BASE_URL, or Anthropic's official endpoint when none is set.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin that prunes stale tool calls instead of summarizing old history and keeps everything else verbatim
Local context compression for agents: tool outputs, logs, files and RAG chunks shrink before reaching the LLM. Proxy, CLI, library and MCP
An OpenClaw plugin that keeps the whole conversation in SQLite instead of trimming it, condenses it into summaries and lets the agent search history
A long-term memory plugin that keeps decisions, preferences and task state across sessions and injects only what a query needs
A persistent memory plugin: stores observations from agent sessions and injects relevant context into new ones
A CLI that strips ballast from Claude Code sessions, watches context with a background guard and preserves Agent Teams state
README in short
The project grew out of the author's own problem: a Codex chat stopped getting through after a dozen image iterations because each message resent about 44 MB. A separate paragraph covers privacy, and detailed installation is in INSTALL.md.