feat: Easy session failure reporting #4183

ki3ani · 2025-08-19T14:44:55Z

Summary

Implements #3244 - adds "Report a Failure" button with automated system info collection and GitHub Issues integration.

Users can now report failures directly within the app instead of manually navigating to GitHub. The modal automatically collects system information and opens pre-filled GitHub
Issues in the browser.

Screenshots

Before: Settings Help & Feedback Section

After: New "Report a Failure" Button Added

Report Failure Modal - System Info Auto-Collection

Success State After Submission

GitHub Issue Pre-filled in Browser

Implementation Details

ReportFailureModal component with form validation and automatic system info collection
GitHub integration opens pre-filled GitHub Issues in browser with proper formatting
Automatic data collection: Goose version, platform, architecture, extension count, provider type
SDK integration uses providers() API for reliable provider detection
Proper error handling with user feedback for all scenarios

Technical Changes

Frontend (`ui/desktop/`)

Added ReportFailureModal.tsx with system info collection using SDK providers API
Enhanced AppSettingsSection.tsx to include the new "Report a Failure" button
Extended preload.ts and main.ts to support opening GitHub URLs

Test Plan

Modal opens and automatically collects system information
Form validation prevents empty submissions
GitHub Issues opens in browser with pre-filled template
System info collection works across different platforms
Provider detection correctly identifies AWS Bedrock, Ollama, etc.
Success/error states provide appropriate user feedback

Notes

Opens GitHub Issues in browser with pre-filled bug report template
Provider detection uses SDK providers() API for reliable detection
Architecture detection exposed through Electron API

jamadeo · 2025-08-20T13:35:31Z

Thanks @ki3ani this is a good feature. However I don't think we should dependon a github token set in goosed -- rather, you can do this more simply by opening the system web browser at something like

https://github.com/block/goose/issues/new?title=YOUR_TITLE&body=YOUR_BODY&labels=LABEL1,LABEL2&milestone=MILESTONE_NAME&assignees=ASSIGNEE1,ASSIGNEE2&template=TEMPLATE_NAME

ki3ani · 2025-08-21T08:14:26Z

Thanks @ki3ani this is a good feature. However I don't think we should dependon a github token set in goosed -- rather, you can do this more simply by opening the system web browser at something like

https://github.com/block/goose/issues/new?title=YOUR_TITLE&body=YOUR_BODY&labels=LABEL1,LABEL2&milestone=MILESTONE_NAME&assignees=ASSIGNEE1,ASSIGNEE2&template=TEMPLATE_NAME

That was well noted @jamadeo, ive refactored to open pre-filled GitHub URL in browser instead.

jamadeo · 2025-08-27T12:15:23Z

crates/goose-server/src/routes/feedback.rs

+        payload.system_info.goose_version,
+        payload.timestamp
+    );
+}


Now that it's a pre-filled github URL, I think you can just remove the "backend" component. No need to have it just to log.

Good point, i have removed the backend feedback endpoint since it was just logging.

jamadeo · 2025-08-27T12:19:24Z

ui/desktop/src/components/ReportFailureModal.tsx

+    try {
+      // Get extension count from the API
+      const apiUrl = getApiUrl('/extension/list');
+      const secretKey = getSecretKey();


I know we do this in other places (we shouldn't) but we should avoid constructing the request like this an instead use the generated SDK:

goose/ui/desktop/src/api/sdk.gen.ts

Lines 111 to 116 in 99fa628

export const getExtensions = <ThrowOnError extends boolean = false>(options?: Options<GetExtensionsData, ThrowOnError>) => {

return (options?.client ?? _heyApiClient).get<GetExtensionsResponses, GetExtensionsErrors, ThrowOnError>({

url: '/config/extensions',

...options

});

};

jamadeo · 2025-08-27T12:21:04Z

ui/desktop/src/components/ReportFailureModal.tsx

+      // For now, collect from browser console errors and any stored logs
+      const recentErrors: string[] = [];
+
+      const storedErrors = localStorage.getItem('goose_recent_errors');


is this a thing? do we write to goose_recent_errors anywhere?

You're right, that wasn't actually used anywhere. Removed it.

jamadeo · 2025-09-26T03:30:12Z

ui/desktop/src/components/ReportFailureModal.tsx

+
+  const collectRecentErrors = useCallback(async () => {
+    try {
+      // Recent errors are logged to the main process via ErrorBoundary


I'm still confused about the recentErrors bit - it looks like it's only ever set to an array of one constant string? what is this about main process error boundary?

I reviewed the mechanism for collecting recent errors. To keep this PR strictly in scope and prevent introducing complex dependencies, I removed the entire collectRecentErrors function and state

jamadeo · 2025-09-26T03:33:49Z

ui/desktop/src/components/ReportFailureModal.tsx

+    try {
+      const secretKey = getSecretKey();
+      const response = await getExtensions({
+        headers: secretKey ? { 'X-Secret-Key': secretKey } : {},


you should not to include the secret key here, as it's globally configured for the generated client sdk

jamadeo · 2025-09-26T03:37:48Z

ui/desktop/src/components/ReportFailureModal.tsx

+          Array.isArray(providerResponse.data) &&
+          providerResponse.data.length > 0
+        ) {
+          info.providerType = providerResponse.data[0].name || 'Unknown Provider';


I don't think you want just the first provider.

The right thing to use here is probably the session metadata for the active session. #4648 adds that to the client API, so this might fit in better once that's merged

I removed the old provider listing logic and refactored the code to use getSessionHistory from the merged #4648 to correctly retrieve the provider_name

DOsinga · 2025-10-02T20:49:29Z

@ki3ani thanks for kicking this off, if you address @jamadeo 's comments, let's get this in!

DOsinga · 2025-10-08T18:47:06Z

can you also do the DCO? and @jamadeo can you have another look?

jamadeo · 2025-10-09T13:37:25Z

ui/desktop/src/components/ReportFailureModal.tsx

@@ -0,0 +1,269 @@
+import { useState, useEffect, useCallback } from 'react';
+import { Button } from './ui/button';
+import { Textarea } from './ui/textarea';


some of these don't exist:

./ui/textarea
./Modal
getSessionHistory

does this run for you?

@jamadeo Yes it was running but some imports were broken which I hadn't noticed. Fixed now - replaced ./ui/textarea with native textarea, ./Modal with Dialog components, and
getSessionHistory with providers() SDK call. All working properly now.

DOsinga · 2025-10-11T20:34:48Z

also can you look into the DCO thing?

Signed-off-by: ki3ani <[email protected]>

- Remove session metadata fallback approach - Use providers() SDK call directly for reliable detection - Clean up unused imports Signed-off-by: Kenneth Mungai <[email protected]> Signed-off-by: ki3ani <[email protected]>

ki3ani · 2025-10-16T21:15:58Z

also can you look into the DCO thing?

Done

jamadeo

Much better! Only real issue is that it picks the wrong provider. Also consider the text truncation, if we must truncate because it's too much for the URL, we should limit the text area so the user doesn't unexpectedly lose what they wrote

jamadeo · 2025-10-17T21:00:05Z

ui/desktop/src/components/ReportFailureModal.tsx

+        if (providersResponse.data && Array.isArray(providersResponse.data)) {
+          const providersList = providersResponse.data;
+          if (providersList.length > 0) {
+            info.providerType = providersList[0].name || 'Unknown';


this isn't the right one to use. You can use useModelAndProvider to get the current model and provider

er, looks like the extension count is also wrong. When I tried it, it shows 0 extensions installed, but I have several

jamadeo · 2025-10-17T21:03:02Z

ui/desktop/src/components/ReportFailureModal.tsx

+
+    try {
+      const issueTitle = encodeURIComponent(
+        `[FAILURE REPORT] ${description.substring(0, 60)}${description.length > 60 ? '...' : ''}`


60 characters seems quite small for what someone might type into this box. If we're limited by url length, you could leave out the txt entry and have the user type in the opened github window. You'd still have the collected system info

jamadeo · 2025-10-17T21:04:12Z

ui/desktop/src/components/settings/app/AppSettingsSection.tsx

+            >
+              <AlertCircle size={16} />
+              Report a Failure
+            </Button>


I see that this is now next to a "report a bug" button. I think your button is better because it collects system info, so I'd say go ahead and remove the other "report a bug" button so we don't have two very similar actions

DOsinga · 2025-10-28T18:25:18Z

closing this since there has been no activity on it. can always reopen

ki3ani changed the title ~~Easy session failure reporting~~ feat: Easy session failure reporting Aug 19, 2025

ki3ani force-pushed the easy-session-failure-reporting branch from caa86fd to 2fd5de7 Compare August 21, 2025 08:07

jamadeo reviewed Aug 27, 2025

View reviewed changes

ki3ani force-pushed the easy-session-failure-reporting branch from 2fd5de7 to 68f4069 Compare August 30, 2025 08:44

DOsinga assigned jamadeo Sep 24, 2025

jamadeo requested changes Sep 26, 2025

View reviewed changes

DOsinga added the waiting label Oct 6, 2025

ki3ani force-pushed the easy-session-failure-reporting branch from 68f4069 to 0a6927f Compare October 7, 2025 13:22

jamadeo requested changes Oct 9, 2025

View reviewed changes

ki3ani force-pushed the easy-session-failure-reporting branch from bbe7a25 to 5bf7acc Compare October 16, 2025 04:35

ki3ani added 8 commits October 16, 2025 07:37

feat: add failure reporting system

46f6062

Signed-off-by: ki3ani <[email protected]>

fix: improve system info collection and GitHub issue format

346fbb0

Signed-off-by: ki3ani <[email protected]>

chore: do linting

4c73568

Signed-off-by: ki3ani <[email protected]>

refactor: simplify failure reporting to use browser-based GitHub issues

c6b38b7

Signed-off-by: ki3ani <[email protected]>

refactor: simplify failure reporting to use browser-based GitHub issues

26d8c89

Signed-off-by: ki3ani <[email protected]>

fix linting

064cf2d

Signed-off-by: ki3ani <[email protected]>

fix(ui): Address review comments on failure report data collection

902cc86

Signed-off-by: ki3ani <[email protected]>

fix imports

3fa79c1

Signed-off-by: ki3ani <[email protected]>

ki3ani force-pushed the easy-session-failure-reporting branch from 5bf7acc to 3fa79c1 Compare October 16, 2025 04:37

Merge branch 'main' into easy-session-failure-reporting

7b83e17

Signed-off-by: ki3ani <[email protected]>

ki3ani force-pushed the easy-session-failure-reporting branch from 360b6cb to 7b83e17 Compare October 16, 2025 13:43

fix: simplify provider detection to use SDK providers API

f81a3b0

- Remove session metadata fallback approach - Use providers() SDK call directly for reliable detection - Clean up unused imports Signed-off-by: Kenneth Mungai <[email protected]> Signed-off-by: ki3ani <[email protected]>

ki3ani force-pushed the easy-session-failure-reporting branch from 5fa67e5 to f81a3b0 Compare October 16, 2025 17:55

jamadeo reviewed Oct 17, 2025

View reviewed changes

DOsinga closed this Oct 28, 2025

	export const getExtensions = <ThrowOnError extends boolean = false>(options?: Options<GetExtensionsData, ThrowOnError>) => {
	return (options?.client ?? _heyApiClient).get<GetExtensionsResponses, GetExtensionsErrors, ThrowOnError>({
	url: '/config/extensions',
	...options
	});
	};

feat: Easy session failure reporting #4183

feat: Easy session failure reporting #4183

Uh oh!

Conversation

ki3ani commented Aug 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots

Before: Settings Help & Feedback Section

After: New "Report a Failure" Button Added

Report Failure Modal - System Info Auto-Collection

Success State After Submission

GitHub Issue Pre-filled in Browser

Implementation Details

Technical Changes

Frontend (ui/desktop/)

Test Plan

Notes

Uh oh!

jamadeo commented Aug 20, 2025

Uh oh!

ki3ani commented Aug 21, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DOsinga commented Oct 2, 2025

Uh oh!

DOsinga commented Oct 8, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DOsinga commented Oct 11, 2025

Uh oh!

ki3ani commented Oct 16, 2025

Uh oh!

jamadeo left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DOsinga commented Oct 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ki3ani commented Aug 19, 2025 •

edited

Loading

Frontend (`ui/desktop/`)