# View Large Tool Runs

Oysterun keeps long consecutive tool activity readable by showing one tool
event in the chat timeline and storing the remaining continuation details
outside the main timeline. This page helps you understand what you should see,
where to open the details, and what to do when a continuation is unavailable.

Continuation here means ordered Tool activity records. It does not promise the
full content of an oversized individual Tool result. Full Tool result content
over 2 MiB (2,097,152 bytes) is intentionally not displayed, even when the surrounding Tool run
has continuation pages; a bounded preview or size-limit notice may remain.

## Prerequisites

- You are signed in to Oysterun.
- A Session chat is open.
- The provider has produced a consecutive run of tool activity, such as tool
  calls, updates, output, results, or failures.
- The first tool event for the run is visible in the chat timeline.

Starting screen: the Session chat timeline, with the first tool event for the
large tool run visible.

## Open The Tool Details

1. Select the visible tool event in the chat timeline.
2. Open the event's detail view when Oysterun shows that option.
3. Review the grouped sections for the tool run.

Expected result: you should see the retained first tool event plus continuation
details grouped into Call, Updates, Output, and Result or Failure sections.
Owner-facing detail pages show at most 10 logical invocations at a time.

## Open Continuation Pages

1. From the large tool output or detail view, use the visible continuation page
   controls when more output is available.
2. Move through the pages in order.

Expected result: page 1 represents the Matrix-backed timeline event, and later
pages show the continuation rows in physical order. Oysterun keeps the order of
the provider's tool activity instead of merging it into unrelated messages.

## What The Timeline Shows

A new large tool run appears as one Matrix-backed tool event in the timeline.
Later tool activity from the same consecutive run is stored as continuation
detail and is not inserted as separate Matrix timeline events.

The run can include:

- tool calls;
- tool updates;
- tool output;
- tool results;
- tool failures.

Hidden thinking deltas do not end the run. The run ends after the provider
commits a non-tool event or reaches a terminal provider-turn boundary.

There is no continuation lifecycle notice, timeline count, or badge. Timeline
pagination still follows the raw Matrix event count, so a long tool run should
not make the chat look like many separate timeline messages.

Checkpoint: the chat shows one visible tool event for the large run, and the
expanded detail view is where you inspect the continuation content.

## Historical Tool Events

Older tool events without the current continuation marker remain as normal
single-event tool boxes. They do not use the combined continuation detail view.
Historical recovery records are not imported into the product view, used as a
fallback resolver, or exposed as combined detail.

## If The Detail View Is Unavailable

Oysterun opens continuation detail only from a supported first tool event for a
large run. If the selected event is older, unmarked, unrelated to the current
run, or no longer available, Oysterun should fail closed instead of combining
unrelated output.

Bounded recovery:

1. Return to the Session chat and select the first visible tool event for the
   run.
2. If the detail view shows no continuation, check whether the event is an
   older single-event tool box.
3. If continuation page controls are disabled, use the currently visible page;
   there may be no more continuation rows for that run.
4. If the chat changed rooms or Sessions, reopen the intended Session chat and
   select the tool event again.
5. If the login screen appears, sign in and reopen the Session from the
   Sessions list.