What attachments do
Every file you attach to an issue is forwarded to the AI agent as part of its first run. The agent receives the attachments alongside your issue body, giving it richer context before it touches a single line of code.Two kinds of attachment
Gentic keeps issue files and chat files apart, because they are useful for different things:Issue attachments
Files added on the New issue page or from the Files card on an issue. They belong to the issue itself, appear in the Files card, and survive an agent or conversation reset. Adding one writes no chat message and does not requeue or wake the agent — the agent picks them up at the start of its next run.
Message attachments
Files sent with the message composer under an existing issue’s activity. They belong to that one message, are shown inline with it in the transcript, and are delivered with that prompt turn — which also wakes the agent, exactly as sending a message does.
Files attached before this split stay message attachments; they are not reclassified.
How attachments are delivered to the agent
Gentic handles different file types differently to give the agent the most useful representation of each file:Images
PNG, JPG, GIF, WebP, and other image files are base64-encoded and embedded directly in the agent’s prompt as image content blocks. The agent can see the full image.
Text files
Plain text, Markdown, JSON, XML, YAML, and other text-based formats are read as UTF-8 and embedded inline as text resource blocks. No disk access required by the agent.
Other file types
PDFs, spreadsheets, binaries, and anything else are downloaded next to (not inside) the repository clone and referenced by their local file path. The agent can read them from disk during its run.
File size limit
Each individual file must be 25 MB or smaller. Uploads that exceed this limit are rejected before they are stored.
Attachments are fetched when a host prepares the prompt. The issue’s own files are handed over on the first prompt of each run, so a reset session sees them again; files added to a follow-up message are delivered on that message’s prompt turn. To rebuild an issue from its original body and current attachments, use Retry with… on the issue detail page.
How to upload attachments
Attachments stay once the issue is submitted
Remove a file while you are still composing — from the New issue page or the message composer, before you save, run, or send. After that the file is part of what the agent was handed, so the Files card lists it for download only and offers no way to delete it.Good use cases for attachments
Screenshots of UI bugs
Screenshots of UI bugs
Attach a screenshot directly to a bug issue instead of describing the visual problem in words. The agent can inspect the screenshot and target the exact element or layout that looks wrong.Supported formats: PNG, JPG, GIF, WebP, BMP, TIFF
Log files showing errors
Log files showing errors
Paste long stack traces or server logs as a
.txt or .log file rather than cramming them into the issue body. The agent receives the full log as an inline text block.Supported formats: .txt, .log, .csv (any text/* MIME type)Design mockups
Design mockups
Attach a design mockup when asking the agent to implement a new UI component. Give the agent both the image and a prompt like “implement the card component shown in the attachment using Tailwind CSS.”Supported formats: formats uploaded with an
image/* MIME type. SVG files are often uploaded as image/svg+xml, but handling depends on the selected agent client.Specification documents
Specification documents
Upload a spec or RFC document to keep the issue body short while still giving the agent the full requirements. Markdown and plain text files are embedded inline; PDFs are downloaded alongside the repo and read from disk.Supported formats:
.md, .txt, .pdf