Session Summary and resources

Check a session's working directory, review changes, and find files and images shared during the conversation.

Session Summary brings together the current session’s working directory, Git actions, shared files, and results. Use it to find something from the conversation without scrolling back through every message.

1. Open a session where you have sent at least one message.
2. Click Open Session Summary in the header. If a right sidebar is open, close it first.
3. Choose Changes to review file edits, or Show all under Sources or Outputs to browse resources.

The Summary floats over the conversation rather than narrowing it. It may open automatically when there is enough room. Use the header button to hide it again. Sessions in a Hive, or with workspace action or preparation activity, can show it before their first message.

What the Summary shows

Sections appear when relevant, except Sources, which keeps its add action available even when empty. Extensions can add sections of their own. An error in one extension section does not prevent the others from working.

A URL mentioned in ordinary prose is not automatically a Source. A modified file is not automatically an Output either. All working-tree changes are available under Environment > Changes, including changes the session did not record as a result.

Agent access and context usage remain beside the message box, not in the Summary.

Project actions and preparation

Running and recent project actions appear in Actions. Select a row to inspect output and controls in the right sidebar. Starting the same action normally opens its existing active run rather than launching another copy. Use Restart deliberately when you want to replace it. These managed runs are separate from interactive terminal tabs.

Workspace preparation shows setup progress, retained output, review decisions, and recovery controls. Configured setup must succeed before the first agent turn in a new managed worktree. If it fails, inspect Setup output, then choose Retry setup or deliberately Continue anyway. Stop setup stops an active attempt. Existing local checkouts run setup only when you choose Run setup. See Project actions.

Environment and Git actions

Check the environment row before running Git commands. It identifies the current checkout or worktree used by this session. The original environment choice is fixed after the first message.

• Choose Changes to open the diff panel.
• Click the branch row to search and check out a branch, create one from an unmatched search, or copy its name.
• Use the Environment plus menu to open the working folder, copy its path, or toggle the terminal.
• Choose Commit or push to open the commit and push panel.

In Commit or push, check the staged and unstaged totals, the target branch, and Include unstaged changes. With that option off, a commit uses only the existing Git index. With it on, OpenWaggle also stages working-tree content. You can use the current branch or enter a validated new branch.

Enter a commit message before choosing Commit or Commit & push. OpenWaggle does not generate one for this panel. Push is also available when the repository state allows it. Disabled actions explain what is missing. Cmd+Enter on macOS or Ctrl+Enter on Windows and Linux runs the first available action.

Stop after current step prevents the next step of a multi-step action. It does not cancel a commit or network push already in progress. Creating a pull or merge request is a separate action.

For the full diff and commit controls, see Git integration.

Creating a pull or merge request

1. Choose Create PR for GitHub or Create MR for GitLab.
2. Check the source and target branches. If you are on the default branch, review the proposed feature-branch name.
3. Edit the title and description. The title starts with the session title.
4. If local changes need to be included, review Commit and push local changes.
5. Choose the draft or ready-for-review action. Cmd+Enter or Ctrl+Enter runs the primary action.

Creation inside OpenWaggle needs an installed and authenticated provider CLI: gh for GitHub or glab for GitLab. OpenWaggle checks access to the remote’s exact host before creating a branch, committing, or pushing. When access is unavailable, it explains why and disables those actions.

Open PR/MR in browser is a separate fallback where the remote supports it. It carries the branch, target, title, and description to the provider’s page. It does not commit, push, or create the request inside OpenWaggle.

Leaving the description blank creates a short Summary and includes changed-file totals if local changes will be committed. After successful creation, View PR or View MR replaces the create action and opens the request in OpenWaggle’s right sidebar.

Inspect and merge a request

The request inspector shows the title, provider link, base and head refs, open/draft/merged state, changed-file totals, and a branch-diff link. It also shows checks, reviews, mergeability, and comment counts when the provider CLI supplies them. Refresh manually when you need an update, or switch to another request recorded by the same session.

Choose Open in browser to use the provider’s site. When the provider reports that merging is available, the inspector offers merge, squash, or rebase. OpenWaggle asks for confirmation and checks the request and exact head commit again before invoking the provider CLI. Disabled actions explain blockers such as checks, reviews, conflicts, draft status, provider rules, or missing information.

If the provider creates the request but OpenWaggle cannot record it under Outputs, keep the creation panel open. Use Retry adding PR/MR to Outputs when offered. That retries recording the existing request, not creating another one. Closing the panel leaves the provider request valid, but it may remain absent from this session’s Outputs.

Following a Hive

A Hive is a group of related sessions working on one task. The parent, called the Queen, can delegate work to Worker sessions. The Summary shows only the opened session’s immediate parent and direct Workers, not every descendant.

Workers are grouped as Active, Review, Done, and Archived. Ready for review means the Worker submitted a result that its parent has not accepted or sent back for revision. This does not mean its Run has stopped. Open the Worker session to check whether it is still running. Accepted or cancelled work appears under Done. Finished Workers you never interacted with are archived automatically and move to Archived. Use the restore button beside an archived Worker to return it to the sidebar.

Select a row to open that session. The section opens automatically while work is active, needs attention, or awaits review. For a Queen, it collapses shortly after all direct work is accepted or cancelled unless you have chosen to keep it expanded. Your manual choice is remembered.

Large Hives have Load more workers. Counts still cover the whole direct Hive, and a failed page can be retried without losing rows already shown. Live updates refresh the list; a reconnect may restart it at the first page.

See Hives and sessions for delegating and reviewing work.

Browsing Sources and Outputs

Select Show all under Sources or Outputs to open the Resource Browser on the right. It groups resources by kind and shows who provided, read, created, or updated each item, along with its conversation branch.

Selecting a non-image item in the Summary opens the browser with that item selected. Selecting an image opens the image viewer. The browser replaces the floating Summary; closing it restores the Summary when it was previously open.

Use Show more for the next page of a large catalog. The total counts all items, not just the loaded page. If the catalog changes while you browse, it restarts from the first page to avoid skipped or duplicated items. A direct resource link opens its item without loading every earlier page.

File and link actions depend on the resource:

• A local non-image file can open in its normal desktop app.
• Open original and Reveal original use the recorded file path when available.
• A managed non-image file downloads a copy.
• Links and sites open in the system browser.
• Missing saved content shows its unavailable state and offers Retry when recovery is possible.

If a resource appeared at several paths or URLs, its row uses the occurrence on the visible conversation path, or the latest matching occurrence if none is on that path.

Resources from background sessions keep updating without mixing into the session you are viewing. Stopping an agent or Waggle run allows partial results to finish saving before completion is reported. Those saved results remain available.

Viewing images

Click an image in chat to browse that message’s images. Open an image from the Summary or Resource Browser to browse all images in the session. The session gallery lists images on the active conversation path first, including shared history, then images exclusive to other branches.

The viewer supports:

• previous and next buttons, or ArrowLeft and ArrowRight, with wraparound;
• fit-to-window and 25, 50, 100, 150, or 200 percent zoom;
• zoom buttons, Cmd/Ctrl + mouse wheel, and supported trackpad pinch zoom;
• drag-to-pan;
• copying the image, adding it to the current message draft, or downloading it;
• opening or revealing an available local original;
• Source/Output and branch details;
• Escape to close.

Copy, add-to-chat, and download become available after the image loads. Adding to chat creates an attachment with the same size limits as the file picker. Use Retry image if content is unavailable or cannot be decoded.

Local PNG, JPEG, GIF, and WebP images embedded in an agent’s Markdown with file: URLs can be copied into the session’s Outputs. The source must be inside the session’s working directory or a supported temporary evidence folder, such as electron-qa-evidence or openwaggle-evidence under the system temporary directory. OpenWaggle validates the file and keeps its saved copy, so deleting the temporary original does not remove an image already captured. Other local paths are not automatically authorized. Older messages can recover these images while their originals are still available; otherwise the item remains unavailable and can be retried.

Remote Markdown images are not fetched merely because you read a message or see a catalog entry. Opening the viewer authorizes an HTTPS fetch with redirect, size, content, and local-network checks. OpenWaggle validates and saves a copy for that session. Failed fetches show an error rather than silently opening the URL in a browser.

The viewer closes when you switch sessions. Pending actions cannot add an image to a different session’s draft, and temporary image and download links are revoked.

Session ownership and persistence

Every resource belongs to one session, including resources from its alternate conversation branches. Parents and Workers have separate catalogs. Archiving retains resources; permanently deleting a session removes its catalog and managed files.

A Queen cannot be permanently deleted while it still has direct Workers, including completed or archived Workers. Delete the Workers first. An active Worker must be stopped before deletion. If either condition blocks deletion, OpenWaggle leaves the session intact and explains what to do.

Removing a project checks the whole Hive before deleting from Workers toward their Queen. Active work, a missing descendant, or an invalid parent relationship blocks removal without deleting siblings. If the session list changed while confirmation was open, review it and confirm again. A later deletion error stops further deletion and refreshes the sidebar while keeping project references available.

Older sessions can recover their resources in batches while the Summary and browser remain usable. Extension authors can add Sources, Outputs, and Summary sections through OpenWaggle extensions.

Panel and tab behavior

At wide widths, OpenWaggle remembers whether the Summary is open and which sections you expanded for each session. At narrow widths, opening it is temporary. Press Escape or click outside to dismiss it without changing the saved wide-layout preference. Resizing does not clear your draft, command chips, or interactive visualizations.

A right sidebar takes precedence over the Summary. Its header button stays visible but is disabled until that sidebar closes. A floating browser preview also takes precedence over automatic Summary display. Explicitly opening the Summary hides that session’s preview without closing the tab. Resource and other inspectors keep it hidden; closing an inspector restores the Summary if previously open, and hiding the Summary restores the preview.

Before the first message, Diff and file inspectors hide an unsent draft’s floating preview. Closing the inspector restores the preview without creating an empty Summary.

Draft and existing-session terminal and browser tabs stay separate. Only sending the draft’s first message moves its tabs into the new session. Tab creation and moves pause during that transfer. If browser tabs cannot move safely, they stay in the project draft and an error explains the failure. Use that project’s New session action to return to them. Terminals already moved remain in the new session.

A browser tab stays visible if its page fails to close, so you can retry. Closing several tabs removes only those that closed successfully. Switching sessions during a close does not open a sidebar in the new session.

If a Summary action is missing

• Send an ordinary session’s first message. Existing Hive sessions and sessions with workspace activity can open the Summary earlier; an ordinary empty draft cannot. Running a Project action also requires an existing session.
• Close the right sidebar, then click Open Session Summary in the header.
• For pull and merge requests, check for a supported GitHub or GitLab remote and authenticated gh or glab access to that host.
• Create or check out a branch if the repository is on a detached HEAD. A new feature branch also needs at least one commit, or local changes selected for Commit and push local changes, before request creation.
• If a request exists at the provider but is missing from Outputs, use the record-only retry in the creation panel when offered.
• Check Environment > Changes for modified files that were not explicitly recorded as Outputs. Ordinary URL text is not automatically a Source.
• Use the section’s Retry for catalog or subscription failures, or Retry image in the viewer for missing image content.

An open Resource Browser clears its old selection when you switch sessions. If it ever shows the previous session’s content after a switch, report it with the two session titles and the steps that reproduced it.