CLAWPOD ENGINEERING

How Much of That CSV Did You Read? Separate Preview from Full Review

Distinguish ClawPod Cloud attachment upload and preview rules, then request, count, and verify the required segment of a long CSV.

ClawPod Engineering · 7min read
REVIEWED BYEditorial Review · Security Review
AI-generated illustrative photograph: just a few sheets open above a thick stack of documents, marked with a teal tab.
An AI-generated illustration of a preview that shows only the beginning. It is not a product screen.

Opening a CSV attachment in a preview does not mean you have checked its last record. This guide is for people exchanging working material in ClawPod Cloud Chat Rooms. With access to a Room that accepts attachments and material you are authorized to share, you can distinguish what to check in the preview from what to download and review separately.

The key distinction is simple: upload acceptance, Portal preview, and an Agent’s ability to read or generate a file are separate checks. A preview replaces neither a full review of the original nor a security check. Record the filename and the range actually read alongside the review result.

Read each size limit with the operation it limits

The figures and formats below are documented in the official Guide checked on September 27, 2026. They are not results from testing your current product interface. If actual behavior differs, collect the filename, size, format, and error before asking for help.

Operation Documented rule What it means
Chat Room upload Up to 50 MiB per file Not the preview ceiling or total storage quota
Text preview Above 1 MiB, only the first 256 KiB is displayed Not evidence that the end of the file was read
PDF preview 10 MiB or smaller Download larger PDFs to review them
Task and Milestone attachment Up to 50 MiB per file The allowed formats are separate from Chat

MiB and KiB are file-size units. One MiB is 1,048,576 bytes; one KiB is 1,024 bytes. The Guide states a 50 MiB upload ceiling and describes the interface label as 50 MB. In your team’s notes, retain the units rather than treating them as interchangeable: “50 MiB per file; the Guide describes the interface label as 50 MB.”

256 KiB is not a record count. CSV files of the same size can contain different numbers of visible records depending on column count and text length. This figure concerns the Portal text preview. It does not establish which tool the Agent used, how much of the file it read, or what it analyzed. Request and verify the actual reading scope separately.

Check the preview condition, not just the format name

A MIME type identifies the kind of file. The Guide says text previews are provided for files stored with MIME type text/plain, text/csv, or text/markdown. This guide does not promise a particular typeface or layout for Markdown attachments, or that they render like HTML.

Allowed Chat category Extensions Documented viewing behavior
Images .jpg, .jpeg, .png, .gif, .webp, .bmp Image preview; download if the browser cannot display it
Documents .pdf, .docx, .xlsx, .pptx, .hwp, .hwpx Preview PDFs up to 10 MiB; download the others
Text .txt, .text, .csv, .md, .markdown, .env, .log, .ini, .conf, .cfg, .properties Text preview according to stored MIME type; first 256 KiB when above 1 MiB
Data and configuration .json, .jsonl, .yaml, .yml, .toml Download
HTML .html, .htm Download; no HTML execution or preview for Chat attachments
Video .mp4 Download; no playback inside the Portal
Archives .zip Download

An XLSX file not opening in a preview is therefore not, by itself, proof of a failed upload. Check allowed format, upload success, and download availability separately. A successful download still does not prove that someone reviewed the entire file or that it is safe.

A Task records work; a Milestone marks a point for a group of work. Their attachments use the existing MIME allowlist for JPEG, PNG, GIF, WebP, BMP, PDF, DOCX, XLSX, PPTX, TXT, CSV, Markdown, HWP, HWPX, and ZIP. Do not apply Chat’s additional formats, such as HTML, MP4, JSON, and YAML, to Tasks or Milestones.

Supported extensions are case-insensitive. The Guide describes normalization by extension when the browser sends an empty or different MIME type; other files may upload if they match an existing allowed MIME type. However, .svg, .svgz, .js, .mjs, .cjs, .exe, .msi, .com, .bat, .cmd, .ps1, and .sh are blocked regardless of MIME type. Renaming an extension is neither conversion nor a safety check, and must not be used to bypass a restriction.

Example: review only the required part of a long CSV

The following is an illustrative example. Filenames, sizes, record numbers, and results are fictional, not an execution record or a guarantee of automatic product behavior. Here, record numbers exclude the header.

A team has a 2 MiB support-log.csv and wants to count inquiry categories in its final segment, records 9,901–10,000. It does not assume that the beginning shown in the Portal preview covers that segment. Using an organization-approved tool, the person responsible makes an extract named support-log-9901-10000.csv, removes names, contact details, and customer identifiers, and checks that the header and 100 records remain. This is a recommended preparation procedure, not a Portal feature for splitting files automatically.

Request

The attached support-log-9901-10000.csv is an extract of data records 9,901–10,000 from support-log.csv. First check whether you have a tool that can read the entire extract. Count inquiries by category and report the actual filename, record count, and scope read. Do not claim to have reviewed the entire original. Do not edit or overwrite files or transmit them externally. If you cannot read the whole extract or the scope does not match, do not finalize the count; report what is missing.

Filled result — illustrative example

Check Example response
Input read support-log-9901-10000.csv, 100 records excluding the header
Scope The entire supplied extract. Its correspondence to original records 9,901–10,000 is information supplied by the person responsible
Count Shipping 60, refunds 25, other 15; total 100
Not reviewed The remaining original records and completeness of the original as a whole
Changes and transmission No file edits, overwrites, or external transmission

Verification does not end with “summary complete.” The person responsible independently checks the extract’s 100 records and category counts using an approved tool. A total of 100 does not prove that the categories are correct, so check each category too. Compare the first and last records and extraction range against the original, and check the Agent’s work record for compliance with the prohibited actions. If the Agent received only the extract, do not interpret its response as independent verification of the extract’s correspondence to the original.

If the Agent read only the beginning or lacked a tool to read the whole extract, the result is incomplete. Identify the missing range, then supply smaller extracts through an approved method or have the person responsible review the downloaded file directly. On the next request, identify the original range of each extract and check for overlaps and gaps. Portal preview truncation and an Agent tool’s reading limit are separate causes: establish which stage was truncated first.

Keep attachments and artifacts separate

An attachment is a file uploaded to the conversation. An artifact is a versioned output generated by the Agent in the conversation. The Guide distinguishes downloadable HTML attachments from Markdown and HTML artifacts previewed in the Artifact panel. The same .html extension does not make these the same delivery path.

An accepted upload format also does not prove that the Agent can generate that format. Before requesting PDF, DOCX, XLSX, PPTX, or ZIP output, check that a suitable generating tool is actually ready in the execution environment. Specify filename, format, path, overwrite permission, and external-transmission permission, then review the received file separately from the conversation.

The figures in this article are documented upload and preview limits. They do not establish total storage quota, retention duration, attachments per message, or a separate size ceiling for downloading itself. A control for continuing beyond a truncated preview has not been verified either. Keep important originals and outputs separately in an organization-approved repository.

Check both the audience and the contents before uploading

A Room is a shared conversation context for users and Agents, with access and participation limited by organization permissions. The Guide says all participating Agents can receive and process Room messages. Mentioning one Agent is not a reason to assume that the material is hidden from other participants. If exactly one Agent must perform the work, use a dedicated Room containing only that Agent.

Check personal information, secrets, and customer data before uploading. Recognition of .env and .env.production does not authorize sharing API keys or passwords. Use a copy with the values removed, and follow your organization’s protected handling procedure for real secrets. A preview is not a security scan or complete file validation: follow organizational security procedures before executing or externally sharing received ZIP files, Office documents, or images too.

Uploading a file is not an instruction to transmit it externally or retain it forever. Add one line to your next attachment request: “Which range should be read, and what evidence will confirm it?” That is the starting point for distinguishing a look at the beginning from a complete review of the material you need.

Sources