# How to read large Oysterun Tool results Distinguish a long Tool run from one oversized result, then use View details, paging, and bounded content to read what is currently available. Use this guide when a Session has a long sequence of Tool activity or a Tool result that is too large to show in full. You will identify which case you have, open the supported detail view, page through bounded content, and stop without repeating a command that may have side effects. The short rule: a long Tool run and one oversized Tool result are different limits. View details can group and page through many Tool invocations, but it does not make the full content of an individual oversized result available. ## Before you start - Your Oysterun Host is connected and you can open the relevant Session. - The Session contains a visible **Tool Call**, **Tool Update**, **Tool Output**, **Tool Result**, **Tool Error**, or grouped Tool row. - You know whether the original command could change files, accounts, services, or other external state. If it could, do not run it again merely to get a different display. **Starting screen:** open the Session chat and scroll to the Tool row associated with the result you need to inspect. ## 1. Identify which large-result case you have What you see What it means Supported reading path One retained Tool row represents a long sequence of calls, updates, outputs, results, or failures This is a long multi-event Tool run. Later events can be grouped outside the main chat timeline. Choose View details , then use the invocation pages. One Tool result shows only a summary, preview, or size-limit state That individual result is bounded. Its full content may be too large for Oysterun to display. Read the available preview or detail. Do not expect long-run paging to reveal the rest of that one result. A normal historical Tool row has no View details action It may be an older single event with no supported continuation. Use the content visible in the row and do not treat the missing action as evidence that the command failed. Do not infer success from length. A long run can end in a failed or incomplete invocation, and a short preview can belong to a successful result. Read the visible state and result for the selected invocation. ## 2. Open the supported Tool detail view ![Same Session Tool row with its title, preview, and View details action visible before the detail dialog opens.](../assets/publication/tool-row-view-details.jpg) Visible checkpoint: the intended Tool row, its preview, and View details are visible together before opening the detail dialog. 1. Find the first retained Tool row for the run you want to inspect. 1. Read its title and preview so that you do not open a neighboring result by mistake. 1. Choose **View details**. Checkpoint: a detail dialog opens with a title such as Tool Usage , Tool Message Group , or Tool Output Batch . If the row has no View details action, stop at the visible row; there is no supported continuation to open from that event. ## 3. Read a long Tool run one invocation at a time ![Tool Usage on Page 2 of 2 showing invocation 11, its succeeded state, Call, Output, Result, Previous, and disabled Next.](../assets/publication/tool-detail-page-two.jpg) Visible checkpoint: page 2 selects invocation 11 and keeps its state, available sections, and both paging controls in one complete dialog. 1. Start with the selected **Tool Invocation**. Its state may be active, succeeded, failed, or incomplete. 1. Read the sections that are present: **Call**, **Updates**, **Output**, and **Result**. A section can be absent when that invocation did not produce that kind of event. 1. If the dialog shows page controls, use PreviousPage N of MNext to move through the run. Each page contains at most 10 logical invocations. 1. On each page, select the invocation whose content you need, then read its currently available sections. Checkpoint: the page label changes when you move to another page, and the selected invocation's visible Call, Updates, Output, or Result belongs to that page. A disabled Previous or Next control means you are at that end of the available pages. ## 4. Understand the boundary for one oversized result ![Oversized Tool detail showing a command that produces 2,100,000 bytes, bounded output, and the exact 1,051,424 bytes omitted marker.](../assets/publication/oversized-result.jpg) Visible checkpoint: the detail stays bounded and explicitly marks 1,051,424 bytes omitted ; it does not claim a continuation. Oysterun keeps Tool detail bounded so that one result cannot overwhelm the Session view. The collapsed row may contain only a summary or preview, and **View details** shows only the portion that is currently available for display. 1 MiB display boundary: when the selected Call or Output for one Tool invocation exceeds 1 MiB (1,048,576 bytes), Oysterun displays only the first 1 MiB in this detail view. The 2,100,000-byte fixture therefore marks exactly 1,051,424 bytes omitted . Invocation paging does not reveal the omitted remainder, and this view does not provide a continuation or download for it. Use the visible summary, preview, state, and bounded detail to decide what happened. Do not rely on a provider-local path or hidden storage location as a public recovery route. ## 5. Recover without repeating the Tool action - **The wrong detail opened:** choose **Close**, locate the intended Tool row, and choose its **View details** action. - **The detail is still loading:** wait for the current request to settle. If it does not, close the dialog and reopen the same row once. - **The dialog reports an incomplete or older Tool Detail pipeline:** close it, reopen the same Session once, and try the same row once. If the message remains, preserve the visible error and ask the person who manages the Host for help. Do not restart the Host yourself unless that person explicitly directs you to do so. - **The result is bounded by size:** treat the missing remainder as unavailable in this view. If you need a future result to be readable here, ask for a smaller summary or clearly bounded chunks before running the task again. - **The original command might have side effects:** do not rerun it just to obtain more detail. Confirm its visible final state first, then ask the Host manager or task owner how to proceed. Safe stop point: after one reopen, an unavailable continuation or persistent detail error is not fixed by sending the same work again. Preserve the visible Tool row and error state, then stop. ## 6. Close the detail view and confirm your place ![Original Tool rows and FIXTURE READY completion remain visible in the same Session after Close, with no second Tool action.](../assets/publication/tool-row-after-close.jpg) Visible checkpoint: after Close , the original Tool rows and terminal completion remain in place without another Tool execution. 1. Choose **Close**. 1. Confirm that you are back in the same Session and that the original Tool row is still visible. 1. Record the invocation state and the bounded information you actually read. Do not describe unseen content as recovered. Finished: you have distinguished a long multi-event run from one oversized result, read every supported page or bounded section needed, and left the original Tool action unchanged.