feat(cli): add HTML session export with an interactive viewer by salman1993 · Pull Request #11977 · aaif-goose/goose

salman1993 · 2026-09-10T03:00:38Z

What

Adds goose session export --format html, producing a single self-contained
HTML file with the session embedded as base64 JSON and rendered client-side
(markdown via marked, syntax highlighting via highlight.js).

Highlights:

Table-of-contents sidebar with scroll-spy for jumping between turns
Semantic tool-call rendering: shell $ prompt, write/todo_write content,
computed edit diffs, collapsible output with a "show more" button
Dense, scannable layout; internal/turn-context messages hidden by default

goose session export --session-id <id> --format html -o session.html

Credit / prior art

The viewer is highly inspired by Pi's HTML session exporter — the overall
approach (one self-contained file, base64-embedded session, client-side
rendering) and the visual language of the transcript follow Pi.

Directly copied from Pi: only the vendored third-party libraries
(marked.min.js, highlight.min.js). The Rust module, template.html,
template.css, and template.js were written for goose's own session schema —
Pi's renderer targets a different, branching session model and was not reused.

Verification

cargo test -p goose --lib session::export_html
cargo fmt / cargo clippy clean
Rendered representative sessions (write/edit/shell/todo_write, thinking,
tool errors) via headless Chrome

Closes #11978

Add `goose session export --format html`, producing a single self-contained HTML file with the session embedded as base64 JSON and rendered client-side (markdown via marked, syntax highlighting via highlight.js). Includes a table-of-contents sidebar with scroll-spy, semantic tool-call rendering (shell `$` prompt, write/todo_write content, computed edit diffs), and collapsible output. The viewer is highly inspired by Pi's HTML session exporter: the overall approach (one self-contained file, base64-embedded session, client-side rendering) and the visual language of the transcript follow Pi. Directly copied from Pi: only the vendored third-party libraries (marked.min.js, highlight.min.js). The Rust module, template.html, template.css, and template.js were written for goose's own session schema — Pi's renderer targets a different, branching session model and was not reused.

chatgpt-codex-connector · 2026-09-10T03:00:48Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-10T03:24:50.669275Z	`eda98fc`	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

salman1993 · 2026-09-10T03:02:53Z

screenshots of what the session viewer looks like:

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8dded84e3b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-09-10T03:05:54Z

+          const response = responsesById.get(block.id);
+          if (response) {
+            const result = response.toolResult;
+            status = result && result.status === 'error' ? 'error' : 'success';


Treat MCP isError results as failures

When a tool returns Ok(CallToolResult::error(...)), its serialized wrapper has status: "success" and the actual failure flag is value.isError: true, so this marks the call as successful. For write, edit, and todo_write, the following suppression also hides the error output entirely, making a failed filesystem operation appear as a successful change in the exported transcript. Determine status from both the wrapper and result.value.isError before suppressing output.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-09-10T03:05:54Z

+    const blocks = Array.isArray(msg.content) ? msg.content : [];
+    const bodyParts = blocks.map(renderContentBlock).filter((h) => h);


Filter assistant-only blocks before rendering visible messages

When a user-visible message contains text, image, or tool-result content annotated for the Assistant audience, this renders every block in the default transcript. Goose normally applies Message::user_visible_content and filters nested tool-result content by audience, so sessions containing model-only MCP or chat-recall content will display that internal content even before the user selects “Show internal messages.” Apply the user-audience projection before mapping blocks to HTML.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-09-10T03:05:54Z

+  function formatTimestamp(unixSeconds) {
+    if (!unixSeconds) return '';
+    const d = new Date(unixSeconds * 1000);
+    if (isNaN(d.getTime())) return '';


Normalize millisecond message timestamps

For persisted sessions whose message timestamps are in milliseconds, multiplying by 1000 again produces dates tens of thousands of years in the future instead of the actual message time. SessionManager::message_timestamp_to_datetime explicitly supports both seconds and milliseconds using MILLISECOND_TIMESTAMP_THRESHOLD, so the HTML formatter needs the same normalization for older or imported sessions.

Useful? React with 👍 / 👎.

DOsinga · 2026-09-10T03:16:30Z

Thanks for contributing. Goose uses an issue-first workflow. Please open or identify the issue for this work, wait until it reaches Ready, and link it from this pull request with Closes #ISSUE_NUMBER.

See From Issue to Pull Request. If no issue is linked and nobody replies here, this pull request will be closed after three days.

salman1993 · 2026-09-10T03:23:16Z

Thanks for contributing. Goose uses an issue-first workflow. Please open or identify the issue for this work, wait until it reaches Ready, and link it from this pull request with Closes #ISSUE_NUMBER.

See From Issue to Pull Request. If no issue is linked and nobody replies here, this pull request will be closed after three days.

put in an issue here: #11978

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eda98fc6f3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-09-10T03:24:48Z

+      default:
+        return '';


Render action-required blocks in exported transcripts

When a persisted message contains actionRequired—for example, an elicitation prompt or a tool-confirmation decision—this falls through to the empty default renderer. If that is the message's only content, renderMessage drops the entire message, so the exported transcript omits an interaction that the CLI and Markdown exporter preserve. Add rendering for the action-required variants instead of silently discarding them.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-09-10T03:24:48Z

+            const suppress = status === 'success' &&
+              (tool === 'write' || tool === 'edit' || tool === 'todo_write');


Restrict file-tool suppression to built-in tools

When an MCP extension exposes a tool such as storage__write, toolNameParts reduces it to the leaf name write, causing this branch to suppress its successful response as though it were Goose's built-in file writer. Such an extension's result may contain important output unrelated to the submitted content, so the export becomes incomplete; gate suppression on the full unqualified built-in tool name rather than the parsed leaf.

Useful? React with 👍 / 👎.

alexhancock · 2026-09-10T12:47:31Z

Cool @salman1993! Something simple built in makes sense.

To share something similar, I also built a session inspector as a side project a couple weeks back.

Deployed: https://www.sessioninspector.ai/
Code: https://github.com/alexhancock/session-inspector

Supports drag and drop of goose session export files. A bit more of a debugging tool in its approach. Supports Claude Code and goose, and can easily be expanded to other harnesses too with the implementation of a TS interface over the underlying data file.

DOsinga · 2026-09-14T17:54:59Z

Thanks — the viewer looks useful, but I don't think this should land as a CLI-only feature.

The desktop already exports sessions through _goose/unstable/session/export and offers JSON and Markdown from the session list. Please expose HTML through that same path and add it to the desktop export menu:

add Html to SessionExportFormat
put the HTML export operation on SessionManager, alongside export_session_markdown
handle Html in on_export_session
add HTML with the correct MIME type and .html extension in SessionListView

That keeps format support in one shared API instead of having the CLI load a session and call the renderer directly.

More broadly, the browser renderer is reimplementing Goose's message semantics from serialized JSON. At minimum, user-visible projection should happen in Rust before embedding the session, so the HTML viewer does not need to duplicate privacy/audience rules that already exist in Message::user_visible_content and related helpers.

DOsinga · 2026-09-15T15:07:54Z

Thanks for contributing. Goose uses an issue-first workflow. Please open or identify the issue for this work, wait until it reaches Ready, and link it from this pull request with Closes #ISSUE_NUMBER.

See From Issue to Pull Request. If no issue is linked and nobody replies here, this pull request will be closed after three days.

alexhancock

LGTM if you fix up the red check @salman1993!

salman1993 · 2026-10-01T19:06:55Z

@alexhancock CI check for MCP Conformance is failing but i don't think its related to this PR. Can you please re-run the failed job and see if that fixes it?

The failing assertion is SSE reconnection timing. The likely cause is the late-reconnection threshold under CI load. The same failure occurred on main yesterday. This PR changes none of the MCP transport, driver, dependencies, or workflow.

* main: fix: support hyphenated GPT 6.1 Sol effort aliases (#12689) Resolve extensions into a per-inference lease (#12161) fix: fixed unstable tests (#12679) fix(desktop): use a system Node.js in the Windows npx wrapper (#12176) fix(cli): show thinking when GOOSE_CLI_SHOW_THINKING is set to any value (#12454) fix(cost): price Databricks GLM aliases from the zhipuai catalog (#12673) fix(tom): read messages from config (#12634) fix(bedrock): preserve the service total when folding cache input tokens (#12586) fix(provider): refresh revoked Copilot tokens when listing models (#12627) feat(cli): prompt for goose mode during first-time configure (#12629) fix: refresh revoked GitHub Copilot API token once (#12616) docs: update Desktop permission mode instructions (#12626) fix(desktop): recognize ASAR when validating update target (#12599) docs: clarify self-serve LLM provider path (#12552) fix(acp): stamp the implemented protocol version in initialize (#12580) feat(cli): add HTML session export with an interactive viewer (#11977) fix: session naming/"none" reasoning effort fails for gpt-6.1-sol (#12605) fix: reflect loading state of chats (#12603) Remove Nostr session sharing from goose core (#12453)

salman1993 requested a review from a team as a code owner September 10, 2026 03:00

chatgpt-codex-connector Bot reviewed Sep 10, 2026

View reviewed changes

fix(cli): address HTML export review feedback

eda98fc

salman1993 mentioned this pull request Sep 10, 2026

view goose sessions in human friendly format #11978

Closed

1 task done

chatgpt-codex-connector Bot reviewed Sep 10, 2026

View reviewed changes

DOsinga assigned michaelneale and alexhancock and unassigned michaelneale Sep 24, 2026

alexhancock approved these changes Sep 29, 2026

View reviewed changes

fix(session): avoid string slicing in HTML export test

d70490a

alexhancock added this pull request to the merge queue Oct 1, 2026

Merged via the queue into aaif-goose:main with commit 9012eac Oct 1, 2026
44 of 45 checks passed

salman1993 mentioned this pull request Oct 6, 2026

docs: update Goose session viewer and add Pi session viewer block/buzz-app#651

Merged

github-actions Bot mentioned this pull request Oct 6, 2026

chore(release): release version 1.54.0 #12732

Closed

BrewTestBot mentioned this pull request Oct 8, 2026

block-goose-cli 1.54.0 Homebrew/homebrew-core#316593

Merged

		const blocks = Array.isArray(msg.content) ? msg.content : [];
		const bodyParts = blocks.map(renderContentBlock).filter((h) => h);

		const suppress = status === 'success' &&
		(tool === 'write' \|\| tool === 'edit' \|\| tool === 'todo_write');

Conversation

salman1993 commented Sep 10, 2026 • edited by DOsinga Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Credit / prior art

Verification

Uh oh!

chatgpt-codex-connector Bot commented Sep 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

salman1993 commented Sep 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Sep 10, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Sep 10, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Sep 10, 2026

Choose a reason for hiding this comment

Uh oh!

DOsinga commented Sep 10, 2026

Uh oh!

salman1993 commented Sep 10, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Sep 10, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Sep 10, 2026

Choose a reason for hiding this comment

Uh oh!

alexhancock commented Sep 10, 2026

Uh oh!

DOsinga commented Sep 14, 2026

Uh oh!

DOsinga commented Sep 15, 2026

Uh oh!

alexhancock left a comment

Choose a reason for hiding this comment

Uh oh!

salman1993 commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

salman1993 commented Sep 10, 2026 •

edited by DOsinga

Loading

chatgpt-codex-connector Bot commented Sep 10, 2026 •

edited

Loading

salman1993 commented Sep 10, 2026 •

edited

Loading

salman1993 commented Oct 1, 2026 •

edited

Loading