Copper now supports file attachments. This has changed how I work. It’s become my prompt backlog: I queue work and prompts as they come up, then route them to their agents when ready. Here’s me capturing prompts for a component’s docs review.

Pls make it available for linux soonest; so I don't get to build it myself 😪

I love the app, don't get me wrong, but I really wish something like this was integrated directly into Codex/Claude Although I guess you wouldn't be able to use it with other apps so 🤷‍♂️

Is this an issue tracker

I understand how this was couched, in the original post— but even the terminology that's being used here ("backlog", "queue work") makes it feel like this is quickly becoming an issue tracker invented from first principles.

It's good to havw this kind of app, but why can't we have superapp like codex or claude code have default feature to store these as prompt or prompkit. Seems very simple feature & doesn't need dedicated app for it.

It will still be limited to the app. Copper works everywhere. So you can capture from Codex, Chrome, Terminal anything

Agree on that part✅️

@iamncdai This is insanely useful How this looks & how simple it is, its awesome!

wow, i was using clipboard for keeping my queue but assuming you are using the clipboard api

this is like a curated clipboard

got it, fun.. will try

Need this. Thank you!

saving a prompt is easy; preserving versions, variables, and

Amazing, was thiking about that.

@theo can you add a feature like this into @t3dotcodes

could you add support for pasting screenshots from clipboard?

is it possible to get metadata e.g. from which app/browser url i've copied the elements? could provide auto-categorization

The app collects metadata like source apps etc. I’m still working on a way to expose this through the UI in a useful way. Soon.

:fire:

This I was using Mac Notes app for this problem, but mostly because that is synced across my devices and mobile, that would be killer for me!

seen queued prompts use stale files after handoff, attachment versioning matters more than capture

@iamncdai Pretty neat.

Please do Windows 🙏

fyi selecting N+ items and right click → delete only deletes the right clicked item

This is pretty dope. Any chance it comes to Windows ?

Mobile app wen

needed this! thank you 🫡

So it's kind of a todo app? Why can't we just use the notes app?

In Windows when?

prompt backlog is such a good idea<|eos|>

you could add tabs so one can have one tab per project? would be amazing and I would start using it for sure

i usually just create a numbered list and have the agent walk through it are there benefits from sending a single request each time?

What is copper? I only know the material

Treating it as a prompt backlog is a clever workflow.

BOOM! 💥 Dishy has been out-🚢'ed! 😮 Good! We have a superintelligence to build! All hands on deck! Great UI/UX makes the entire 🌎 move faster! One more Copper power-💪-up 👇

Does the drag and drop work for TUI?

the prompt backlog is the task backlog with better latency. same discipline problem: prioritization, staleness, stuff that sits a week and stops being relevant.

I’ve been using Copper and find it convenient, but pressing Enter to confirm Japanese conversion in the form unintentionally saves the entry, causing instability. Please fix this in a future update.

We fixed this in the recent release. Is it still happening?

Thanks for your reply. It has been fixed perfectly! Thank you for the fix. I didn't notice that there were two updates coming.

This sounds like a natural next step for agent workflows: capture → add context → prioritize → route → verify

The queue is the part people underrate. A prompt written on Tuesday assumes a repo state that is gone by Thursday, so the item has to carry its own context or the first two turns get spent re-explaining. Attachments fix exactly that. The intent and the evidence travel together.

This has convinced me to buy copper. WP This looks insanely useful and slots into my existing workflow super well