Filter Apps page to only show standalone Goose Apps

[aharvard]

Summary

Filter the Apps page to only display apps from the "apps" extension (vibe coded apps built by Goose).

Changes

• Client-side only change in AppsView.tsx
• Filters apps using mcpServers?.includes('apps') - the same pattern already used for the "Custom app" label
• No backend changes required

Why

Previously, the Apps page displayed all MCP UI resources from all extensions, including chat-dependent MCP apps that require a chat context to function. This caused confusion since those apps cannot be launched standalone.

Now only apps created by Goose (vibe coded apps) are shown on the Apps page.

[Copilot]

Pull request overview

Filters the Apps page to only show standalone goose apps by adding an explicit is_goose_app flag derived from Goose App JSON-LD metadata and applying that filter in the server’s list_apps endpoint.

Changes:

• Added is_goose_app to GooseApp and logic to detect Goose App JSON-LD metadata.
• Marked newly created apps as standalone (is_goose_app: true) and filtered /agent/list_apps results accordingly.
• Regenerated OpenAPI + TypeScript client types to expose isGooseApp.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
ui/desktop/src/api/types.gen.ts	Adds isGooseApp to generated TS types for app filtering.
ui/desktop/openapi.json	Adds isGooseApp to the OpenAPI schema for GooseApp.
crates/goose/src/goose_apps/app.rs	Adds is_goose_app to GooseApp and implements metadata detection.
crates/goose/src/agents/apps_extension.rs	Marks newly created apps as standalone (is_goose_app: true).
crates/goose-server/src/routes/agent.rs	Filters list_apps results to only return is_goose_app apps and updates caching behavior.

Comments suppressed due to low confidence (1)

crates/goose-server/src/routes/agent.rs:1023

• Cache cleanup now derives active_extensions from the filtered apps list, so extensions that only provide non-Goose apps will never have their cached entries deleted, causing stale/unused cache files to accumulate; compute the set from all_apps (or from ui_resources) and then store only the filtered subset.

    if let Some(cache) = cache.as_ref() {
        let active_extensions: HashSet<String> = apps
            .iter()
            .flat_map(|app| app.mcp_servers.iter().cloned())
            .collect();

        for extension_name in active_extensions {
            if let Err(e) = cache.delete_extension_apps(&extension_name) {
                warn!(

[Copilot]

This recompiles the same regex every time has_goose_app_metadata is called (likely once per UI resource on each /list_apps), which is unnecessarily expensive; consider a precompiled static (e.g., once_cell::sync::Lazy<Regex>) or reusing the existing regex from from_html.

[Copilot]

has_goose_app_metadata only inspects the first application/ld+json <script> match, so it can return false even if a later JSON-LD block contains @type: "GooseApp"; iterate over all matches and return true if any block qualifies.

Suggested change

	let Some(json_str) = metadata_re.captures(html).and_then(|cap| cap.get(1)) else {
	return false;
	};
	let Ok(metadata) = serde_json::from_str::<serde_json::Value>(json_str.as_str()) else {
	return false;
	};
	metadata
	.get("@type")
	.and_then(|v| v.as_str())
	.is_some_and(|t| t == Self::GOOSE_APP_TYPE)
	for caps in metadata_re.captures_iter(html) {
	let Some(json_match) = caps.get(1) else {
	continue;
	};
	let Ok(metadata) =
	serde_json::from_str::<serde_json::Value>(json_match.as_str())
	else {
	continue;
	};
	if metadata
	.get("@type")
	.and_then(|v| v.as_str())
	.is_some_and(|t| t == Self::GOOSE_APP_TYPE)
	{
	return true;
	}
	}
	false

[DOsinga]

as discussed, I think we should do the filtering on the client

[aharvard]

@DOsinga, we're client-side only now. LMK if this is cool.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

This filtering uses a.mcpServers?.includes('apps'), but the PR description says the Apps page should filter on app.isGooseApp; either update the implementation to use the isGooseApp field (and ensure it exists in the generated GooseApp type) or update the PR description/title to match the actual filter criterion.

[Copilot]

The same apps.filter((a) => a.mcpServers?.includes('apps')) logic is duplicated in several places; factor this into a small helper (and/or a shared constant for the extension name) to avoid missing an update if the filter rule changes again.

[aharvard]

@DOsinga, friendly ping for when you have a moment