Support non-image uploads in the composer
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by finding where the composer currently handles uploads, especially image paste/drop paths (search the TypeScript source for upload, clipboard, or paste handling), and read parent issue #6 plus the linked TODO.md for the intended behavior. Decide what 'done' means for non-image files — accepted, not rendered as an image preview, and correctly attached — and use that as your acceptance check, since no tests or files are named in the issue.
Written by the indexing model from the issue text.
Description
Support non-image uploads in the composer.
Tracked by #6. Migrated from TODO.md — Port from old Ace.
Progress
- Text files: sent with the message as
filesand read by every model (#469) - PDFs: the app extracts their text with pdf.js and sends it as a text file. No protocol or storage change (#479)
- Open an attached file's contents from the timeline: the file block opens
FileViewin a dialog (#479) - Scanned PDFs and other binary files (zip, docx, xlsx, …). pi-ai 1.0.0 has no document content block, so this needs one in pi, or OCR, or workspace placement plus a tool that can read the file
- Guard against attachments larger than the model's context. The 1.5 MB budget counts bytes, and ~1 MB of multilingual PDF text came to 466K tokens. That run fails, and so does every later run in the chat, until the message is deleted
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from githubnext/ace2
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
githubnext/ace2#440 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
githubnext/ace2#430 ·
Similar issues
-
backend priority:P3 privacy-fix
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#13697 · 1 comment ·
Maintainers usually reply within 1 day
-
area:security documentation effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100