Allow Appshot attachments to have user-visible identifiers/labels for multi-Appshot prompts
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Allow Appshot attachments to have user-visible identifiers/labels
What feature would you like to see?
I capture several UI bugs using Appshots before submitting my prompt. Currently the attachments have no stable user-visible identifier, so I have to refer to them as “1st Appshot”, “2nd Appshot”, etc. This becomes ambiguous and error-prone when batching multiple UI issues.
It would be useful if each Appshot automatically received an identifier such as Appshot 1, Appshot 2, etc., visible both to the user and to Codex, or if the user could rename/label an Appshot before sending.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how Appshot attachments are created, displayed to the user, and included in prompts. Done means multiple Appshots have stable, user-visible identifiers that Codex can also distinguish, or a clearly supported way for users to label them before sending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100