feat: add apt-manager extension by ali00209 · Pull Request #403 · vicinaehq/extensions

ali00209 · 2026-09-22T08:12:29Z

Summary

Manage apt packages and repositories from Vicinae, launched via the apt command.

Features

Installed packages — list, remove/reinstall, show info.
All packages — browse the full apt cache (lazy-loaded), install on the fly.
Upgradable packages — see updates, upgrade individually.
Update all — apt update then apt-get upgrade --with-new-pkgs, with confirmation.
Clean up system — apt-get autoremove --purge then apt-get autoclean.
Repositories — list sources from sources.list/sources.list.d (legacy one-line and deb822 .sources), add new repos as deb822 .sources files, enable/disable/remove.
Flatpak support — manage Flatpak applications and remotes when the CLI is available (sections hidden otherwise).

How it works

Read-only operations (apt list, apt-cache show) run without privileges.
Every privileged operation (install, remove, upgrade, cleanup, repo writes) runs via pkexec, showing the desktop's polkit authentication dialog. If pkexec is missing, a readable error is shown plus a "Retry in Terminal (sudo)" action.
Long-running command output is displayed in a result view after completion.

Requirements

Debian / Ubuntu (or compatible) system with apt.
pkexec (package policykit-1) for privileged operations — either the polkit agent of your desktop session or the fallback terminal action.
Optional: flatpak to manage Flatpak applications and repositories.

clankus-aurelius · 2026-09-22T08:12:32Z

Thanks for contributing an extension to Vicinae! 👋

Before publication, this pull request receives two reviews:

An automated review for extension guidelines, safety, error handling, and likely correctness issues.
A final review from a Vicinae maintainer.

✅ Ready for human review. The automated reviewer approved the latest commit and a maintainer has been notified.

No blocking findings remain on the latest commit.

The automated reviewer examines only the current commit. New commits invalidate its previous decision and start another review.

clankus-aurelius

The extension can silently overwrite an existing APT source file, and several package/repository workflows behave incorrectly or conceal failures. The issues should be resolved before publication.

Automated review found 1 publication-blocking issue.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-22T08:15:50Z

+			: content.replace("Enabled: yes", "Enabled: no");
+
+		const path = join(SOURCES_LIST_D, `${slugify(name)}.sources`);
+		setIsSubmitting(true);
+		const toast = await showToast({
+			style: Toast.Style.Animated,
+			title: `Adding repository ${uri}`,


🔴 Blocking — Adding a repository silently overwrites an existing source file

Rule: CORRECTNESS-001

The user-controlled filename is converted directly into a .sources path and passed to pkexec tee, which truncates any existing file at that path without warning. Reusing a common name can therefore destroy an existing repository configuration.

Suggested resolution: Check whether the destination exists and refuse the operation or require explicit overwrite confirmation before writing it. Preserve existing content unless the user knowingly chooses replacement.

clankus-aurelius · 2026-09-22T08:15:50Z

+			index < Math.min(repo.endLine, lines.length);
+			index += 1
+		) {
+			const stripped = lines[index].trim();
+			if (stripped.startsWith("Enabled:")) {
+				lines[index] = `Enabled: ${enabled ? "yes" : "no"}`;
+				return lines.join("\n");
+			}
+		}
+		return lines.join("\n");
+	}
+	if (repo.startLine >= 0 && repo.startLine < lines.length) {


🟠 Warning — Disabling ordinary deb822 repositories does nothing

Rule: CORRECTNESS-001

For an enabled deb822 stanza without an existing Enabled: field, the loop finds nothing and returns the original content. The UI then reports success even though the repository remains enabled.

Suggested resolution: When disabling and no Enabled: field exists, insert Enabled: no into the selected stanza before writing the file.

clankus-aurelius · 2026-09-22T08:15:50Z

+				{toggleDetail}
+				{pkg.flags.installed ? (
+					<Action
+						title={`Remove ${pkg.name}`}
+						icon={Icon.Trash}
+						style={Action.Style.Destructive}
+						shortcut={Keyboard.Shortcut.Common.Remove}
+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["uninstall", "-y", pkg.name],
+								`Remove ${pkg.name}`,
+								`Remove the Flatpak application ${pkg.name}?`,
+							)


🟠 Warning — User-installed Flatpaks are operated on as system installations

Rule: CORRECTNESS-001

The installed list includes system and user applications, but the package model does not retain their installation and this action always invokes Flatpak through pkexec without --user or --system. Removing a user-installed application can therefore target the wrong installation or fail.

Suggested resolution: Record each application's installation when listing it, pass that through AptPackage, and execute the action with runFlatpakCommand and the corresponding installation flag.

clankus-aurelius · 2026-09-22T08:15:50Z

+			<List.Section title="System">
+				<RootItem
+					title="Update all packages"
+					subtitle="apt update then upgrade with new packages"
+					icon={Icon.Bolt}
+					shortcut={{ key: "u", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					onAction={() =>
+						runAndShow(
+							runAptUpgradeAll,
+							"Update all packages",
+							["upgrade", "-y", "--with-new-pkgs"],
+							"Run apt update then upgrade all packages?",
+						)
+					}
+					extraActions={
+						<Action.RunInTerminal
+							title="Retry in Terminal (sudo)"
+							icon={Icon.Terminal}
+							args={["sudo", "apt-get", "upgrade", "-y", "--with-new-pkgs"]}
+							options={{ hold: true }}
+						/>
+					}
+				/>
+				<RootItem
+					title="Clean up system"
+					subtitle="autoremove --purge then autoclean"
+					icon={Icon.Eraser}
+					shortcut={{ key: "k", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					destructive
+					onAction={() =>
+						runAndShow(
+							runAptCleanup,
+							"Clean up system",
+							["autoremove", "-y", "--purge"],
+							"Run autoremove --purge and autoclean?",
+						)
+					}
+				/>


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

“Update all” normally runs apt-get update followed by upgrade, but its terminal retry runs only upgrade. The cleanup result similarly retries only autoremove, omitting autoclean, so the advertised fallback does not repeat the selected operation.

Suggested resolution: Provide retry actions that execute the complete confirmed sequence, or label the partial commands accurately and expose separate actions for every omitted stage.

clankus-aurelius · 2026-09-22T08:15:50Z

+
+		const shouldUpdate = Boolean(values.updateNow);
+		if (shouldUpdate) {
+			await runAptUpdate();
+			pop();
+			return;


🟠 Warning — Package-list update failures are silently ignored

Rule: UX-001

After adding a repository, the result of runAptUpdate() is discarded and the form closes even when updating package lists fails. The user receives no indication that packages from the new source are unavailable.

Suggested resolution: Inspect the operation result, show its error on failure, and keep the form or result view open so the user can retry.

clankus-aurelius · 2026-09-22T08:15:50Z

+- Every privileged operation (`install`, `remove`, `upgrade`, `cleanup`, repo writes)
+  is run via `pkexec`, which shows the desktop's polkit authentication dialog.
+  If `pkexec` is missing you'll get a readable error plus a "Retry in Terminal (sudo)"
+  action instead.
+- Command output for long-running operations is shown in a result view after completion.


🟠 Warning — The documented sudo fallback is not available for every privileged operation

Rule: MANIFEST-001

The README promises a terminal retry for every privileged operation, but repository writes, deletions, and enable/disable actions only show an error toast when pkexec fails.

Suggested resolution: Either add equivalent terminal retry actions to repository operations or narrow the documentation to the operations that actually provide the fallback.

clankus-aurelius · 2026-09-22T08:15:50Z

+	"display": "Node 16",
+	"include": ["src/**/*"],
+	"compilerOptions": {
+		//"lib": ["es2020"],


🔵 Suggestion — Commented-out configuration remains in the submission

Rule: QUALITY-001

The disabled lib setting is an unexplained development remnant.

Suggested resolution: Remove the commented-out setting.

Co-authored-by: Clankus Aurelius <clankus@aurelle.dev>

clankus-aurelius

The locale parsing issue is fixed. The other previously reported repository, Flatpak, retry, feedback, documentation, and dead-code issues remain unresolved.

Automated review found 1 publication-blocking issue.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-22T08:36:41Z

+		setIsSubmitting(true);
+		const toast = await showToast({
+			style: Toast.Style.Animated,
+			title: `Adding repository ${uri}`,


🔴 Blocking — Adding a repository can overwrite an existing source file

Rule: CORRECTNESS-001

The derived .sources path is passed to pkexec tee, which truncates any existing file with the same name without warning, potentially destroying repository configuration.

Suggested resolution: Check whether the destination exists and refuse the operation, or require explicit overwrite confirmation before writing it.

clankus-aurelius · 2026-09-22T08:36:41Z

+		}
+		return lines.join("\n");
+	}
+	if (repo.startLine >= 0 && repo.startLine < lines.length) {


🟠 Warning — Disabling an ordinary deb822 repository does nothing

Rule: CORRECTNESS-001

When an enabled deb822 stanza has no Enabled: field, the loop returns the original content, yet the UI reports that the repository was disabled.

Suggested resolution: When disabling and no Enabled: field exists, insert Enabled: no into the selected stanza before writing the file.

clankus-aurelius · 2026-09-22T08:36:41Z

+							)
+						}
+					/>
+				) : (
+					<Action
+						title={`Install ${pkg.name}`}


🟠 Warning — Flatpak application actions ignore the installation scope

Rule: CORRECTNESS-001

Installed applications are collected from both user and system installations, but the model does not retain that scope and these actions always run through pkexec without the corresponding --user or --system selection.

Suggested resolution: Retain each application's installation in AptPackage and execute install or uninstall through runFlatpakCommand with the matching installation flag.

clankus-aurelius · 2026-09-22T08:36:41Z

+							"Run autoremove --purge and autoclean?",
+						)
+					}
+				/>


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade, omitting apt-get update; the cleanup retry similarly runs only autoremove, omitting autoclean. The fallback therefore does not repeat the advertised operation.

Suggested resolution: Make each retry execute the complete confirmed sequence, or label and expose the partial stages separately.

clankus-aurelius · 2026-09-22T08:36:41Z

+			return;
+		}
+		pop();


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails, leaving the user unaware that packages from the new source may be unavailable.

Suggested resolution: Inspect the operation result, show actionable failure feedback, and keep an appropriate view open for retry.

clankus-aurelius · 2026-09-22T08:36:41Z

+- Every privileged operation (`install`, `remove`, `upgrade`, `cleanup`, repo writes)
+  is run via `pkexec`, which shows the desktop's polkit authentication dialog.
+  If `pkexec` is missing you'll get a readable error plus a "Retry in Terminal (sudo)"
+  action instead.
+- Command output for long-running operations is shown in a result view after completion.


🟠 Warning — The documented sudo fallback is not universally available

Rule: MANIFEST-001

The README promises a terminal retry for every privileged operation, but APT repository writes, deletions, and enable/disable actions only display errors when pkexec fails.

Suggested resolution: Add equivalent terminal retry actions to repository operations or narrow the documentation to the operations that provide the fallback.

clankus-aurelius · 2026-09-22T08:36:41Z

+	"display": "Node 16",
+	"include": ["src/**/*"],
+	"compilerOptions": {
+		//"lib": ["es2020"],


🔵 Suggestion — Commented-out configuration remains in the submission

Rule: QUALITY-001

The disabled lib setting is an unexplained development remnant.

Suggested resolution: Remove the commented-out setting.

…write - Insert Enabled: no when disabling deb822 stanza without the field (CORRECTNESS-001) - Add pkexec availability checks to writeFilePrivileged/deleteFilePrivileged - Add existsSync check before writing new repo files in AddRepo - Narrow README terminal retry documentation to match actual behavior

clankus-aurelius

Three prior issues are resolved. Four earlier findings remain, and the new repository error message introduces one misleading recovery instruction.

Automated extension review passed. A maintainer review is still required.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-22T08:51:26Z

+					/>
+				) : (
+					<Action
+						title={`Install ${pkg.name}`}


🟠 Warning — Flatpak application actions ignore installation scope

Rule: CORRECTNESS-001

Installed applications are collected from both user and system installations, but AptPackage does not retain that scope and these actions always use privileged Flatpak commands without --user or --system.

Suggested resolution: Retain each application's installation scope and use runFlatpakCommand with the matching installation flag.

clankus-aurelius · 2026-09-22T08:51:26Z

+							"Run autoremove --purge and autoclean?",
+						)
+					}
+				/>


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade, omitting apt-get update; the cleanup retry similarly runs only autoremove, omitting autoclean.

Suggested resolution: Make each retry execute the complete confirmed sequence, or present the stages as separate operations with accurate labels.

clankus-aurelius · 2026-09-22T08:51:26Z

+			pop();
+			return;
+		}
+		pop();


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails.

Suggested resolution: Inspect the operation result, show actionable failure feedback, and keep an appropriate view open for retry.

clankus-aurelius · 2026-09-22T08:51:26Z

+	}
+	const result = await run("pkexec", ["tee", path], {
+		input: content,
+		timeout: 120_000,
+	});
+	return result.ok
+		? null
+		: result.stderr.trim() || result.stdout.trim() || "Failed to write file";
+}
+
+export async function deleteFilePrivileged(
+	path: string,
+): Promise<string | null> {
+	if (!pkexecAvailable()) {
+		return "`pkexec` was not found in PATH. Install polkit (e.g. `apt install policykit-1`) or use the 'Retry in Terminal' action with sudo.";


🟠 Warning — Repository errors advertise a nonexistent retry action

Rule: UX-001

Both new pkexec checks instruct users to use a “Retry in Terminal” action, but repository write and delete flows provide no such action.

Suggested resolution: Either add a terminal retry to repository operations or change these errors to describe an available recovery path.

clankus-aurelius · 2026-09-22T08:51:26Z

+	"display": "Node 16",
+	"include": ["src/**/*"],
+	"compilerOptions": {
+		//"lib": ["es2020"],


🔵 Suggestion — Commented-out configuration remains in the submission

Rule: QUALITY-001

The disabled lib setting is an unexplained development remnant.

Suggested resolution: Remove the commented-out setting.

clankus-aurelius · 2026-09-22T08:51:31Z

@aurelleb automated review passed for 4a69318; this extension is ready for your review.

- Add installation field to FlathubListedApp and AptPackage - Split fetchFlathubInstalled into --system and --user queries - Use runFlatpakCommand with installation flag instead of runPrivileged - User Flatpak operations run directly (no pkexec); system still uses pkexec - Terminal retry via sudo only for system Flatpak operations

clankus-aurelius

Four prior issues remain unresolved. The Flatpak scope changes retain installation metadata but still do not pass the matching CLI scope flag.

Automated extension review passed. A maintainer review is still required.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-22T09:01:50Z

+				<RootItem
+					title="Update all packages"
+					subtitle="apt update then upgrade with new packages"
+					icon={Icon.Bolt}
+					shortcut={{ key: "u", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					onAction={() =>
+						runAndShow(
+							runAptUpgradeAll,
+							"Update all packages",
+							["upgrade", "-y", "--with-new-pkgs"],
+							"Run apt update then upgrade all packages?",
+						)
+					}
+					extraActions={
+						<Action.RunInTerminal
+							title="Retry in Terminal (sudo)"
+							icon={Icon.Terminal}
+							args={["sudo", "apt-get", "upgrade", "-y", "--with-new-pkgs"]}
+							options={{ hold: true }}
+						/>
+					}
+				/>
+				<RootItem
+					title="Clean up system"
+					subtitle="autoremove --purge then autoclean"
+					icon={Icon.Eraser}
+					shortcut={{ key: "k", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					destructive
+					onAction={() =>
+						runAndShow(
+							runAptCleanup,
+							"Clean up system",
+							["autoremove", "-y", "--purge"],
+							"Run autoremove --purge and autoclean?",
+						)
+					}
+				/>


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade, omitting apt-get update; the cleanup retry receives only autoremove, omitting autoclean. The retries therefore do not perform the operations presented to the user.

Suggested resolution: Make each terminal retry execute the complete confirmed sequence, or expose the stages separately with accurate labels.

clankus-aurelius · 2026-09-22T09:01:50Z

+		}
+		pop();
+	};
+
+	return (


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails.

Suggested resolution: Inspect the result, show actionable failure feedback, and keep an appropriate view open so the update can be retried.

clankus-aurelius · 2026-09-22T09:01:50Z

+		return "`pkexec` was not found in PATH. Install polkit (e.g. `apt install policykit-1`) or use the 'Retry in Terminal' action with sudo.";
+	}
+	const result = await run("pkexec", ["rm", "-f", path], { timeout: 120_000 });
+	return result.ok ? null : result.stderr.trim() || "Failed to delete file";
+}
+
+/**
+ * Apply a set of pending file changes. Empty replacements delete the file,
+ * everything else overwrites it via `pkexec tee`.
+ */
+export async function applyRepoChanges(
+	changes: Array<{ path: string; content: string | null }>,
+): Promise<Array<{ path: string; ok: boolean; error: string | null }>> {


🟠 Warning — Repository errors advertise a nonexistent retry action

Rule: UX-001

Both missing-pkexec errors direct users to a “Retry in Terminal” action, but repository write and delete flows provide no such action.

Suggested resolution: Add a terminal retry to repository operations or change these errors to describe an available recovery path.

- AppImages integrated into existing apt command, mixed in package list - Discovery from ~/Applications with .desktop/.appdata.xml metadata parsing - Install from URL or local file (user choice via form) - Three-depth removal: file only, with desktop entries, with config - Manual check for updates per AppImage - AppImage detail view with name, version, description

clankus-aurelius

The four prior findings remain unresolved. The new AppImage support also introduces unsafe executable downloads and several material action/removal/update errors.

Automated review found 2 publication-blocking issues.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-23T09:37:28Z

+						shortcut={Keyboard.Shortcut.Common.Remove}
+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["uninstall", "-y", pkg.name],
+								`Remove ${pkg.name}`,
+								`Remove the Flatpak application ${pkg.name}?`,
+								pkg.installation,
+							)
+						}
+					/>
+				) : (
+					<Action
+						title={`Install ${pkg.name}`}
+						icon={Icon.Plus}
+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["install", "-y", "flathub", pkg.name],
+								`Install ${pkg.name}`,
+								null,


🟠 Warning — Flatpak application actions still omit installation scope

Rule: CORRECTNESS-001

The selected installation only controls privilege handling; the install and uninstall arguments still omit the matching --user or --system flag, so they may target the wrong installation or fail.

Suggested resolution: Add the scope flag derived from pkg.installation to both Flatpak command argument arrays.

clankus-aurelius · 2026-09-23T09:37:28Z

+					title="Update all packages"
+					subtitle="apt update then upgrade with new packages"
+					icon={Icon.Bolt}
+					shortcut={{ key: "u", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					onAction={() =>
+						runAndShow(
+							runAptUpgradeAll,
+							"Update all packages",
+							["upgrade", "-y", "--with-new-pkgs"],
+							"Run apt update then upgrade all packages?",
+						)
+					}
+					extraActions={
+						<Action.RunInTerminal
+							title="Retry in Terminal (sudo)"
+							icon={Icon.Terminal}
+							args={["sudo", "apt-get", "upgrade", "-y", "--with-new-pkgs"]}
+							options={{ hold: true }}
+						/>
+					}
+				/>
+				<RootItem
+					title="Clean up system"
+					subtitle="autoremove --purge then autoclean"
+					icon={Icon.Eraser}
+					shortcut={{ key: "k", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					destructive
+					onAction={() =>
+						runAndShow(
+							runAptCleanup,
+							"Clean up system",
+							["autoremove", "-y", "--purge"],


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade, omitting apt-get update, while the cleanup retry receives only autoremove, omitting autoclean. The retries therefore do not perform the operations presented to the user.

Suggested resolution: Make each retry execute the complete confirmed sequence, or expose the stages separately with accurate labels.

clankus-aurelius · 2026-09-23T09:37:28Z

+	};
+
+	return (
+		<Form
+			navigationTitle="Add Repository"
+			isLoading={isSubmitting}


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails.

Suggested resolution: Inspect the result, show actionable failure feedback, and keep an appropriate view open so the update can be retried.

clankus-aurelius · 2026-09-23T09:37:28Z

+): Promise<Array<{ path: string; ok: boolean; error: string | null }>> {
+	const results: Array<{ path: string; ok: boolean; error: string | null }> =
+		[];
+	for (const change of changes) {
+		if (change.content === null || change.content.trim() === "") {
+			const error = await deleteFilePrivileged(change.path);
+			results.push({ path: change.path, ok: error === null, error });
+		} else {
+			const error = await writeFilePrivileged(change.path, change.content);
+			results.push({ path: change.path, ok: error === null, error });
+		}
+	}
+	return results;
+}
+


🟠 Warning — Repository errors advertise a nonexistent retry action

Rule: UX-001

Both missing-pkexec errors direct users to a “Retry in Terminal” action, but repository write and delete flows provide no such action.

Suggested resolution: Add a terminal retry to repository operations or change these errors to describe the recovery path that is actually available.

clankus-aurelius · 2026-09-23T09:37:28Z

+		targetPath = join(appsDir, urlName);
+		try {
+			const response = await fetch(url);
+			if (!response.ok) {
+				return { ok: false, error: `Download failed: ${response.status}` };
+			}
+			const buffer = await response.arrayBuffer();
+			const bytes = Buffer.from(buffer);
+			try {
+				const { writeFileSync } = await import("node:fs");
+				writeFileSync(targetPath, bytes);
+			} catch {
+				const fs = await import("node:fs");
+				await new Promise<void>((resolve, reject) => {
+					const stream = fs.createWriteStream(targetPath);
+					stream.on("finish", () => resolve());
+					stream.on("error", (e) => reject(e));
+					stream.write(bytes);
+					stream.end();
+				});
+			}
+			try {
+				chmodSync(targetPath, 0o755);
+			} catch {
+				// chmod may fail silently
+			}
+		} catch (err) {
+			return {
+				ok: false,
+				error: `Download failed: ${err instanceof Error ? err.message : String(err)}`,


🔴 Blocking — Arbitrary URLs are installed as executable files

Rule: SECURITY-001

Any user-supplied URL is downloaded without source or content validation, written into ~/Applications, and marked executable. This is an arbitrary downloaded executable rather than a justified resource from an established source.

Suggested resolution: Remove arbitrary-URL executable installation, or restrict downloads to verified releases from established sources with integrity/authenticity verification; otherwise direct users to install AppImages themselves.

clankus-aurelius · 2026-09-23T09:37:28Z

+		);
+	}
+


🔴 Blocking — Installed AppImages receive APT actions

Rule: CORRECTNESS-001

The earlier kind === "installed" branch returns before this AppImage branch. Consequently, every AppImage shown under Installed Packages gets APT remove/reinstall actions, potentially operating on an unrelated Debian package with the same displayed name.

Suggested resolution: Handle pkg.manager === "appimage" before branches based only on list kind.

clankus-aurelius · 2026-09-23T09:37:28Z

+			if (existsSync(configDir)) {
+				rmSync(configDir, { recursive: true, force: true });
+			}
+		}
+	} catch (err) {
+		return {
+			ok: false,
+			error: `Remove failed: ${err instanceof Error ? err.message : String(err)}`,
+		};
+	}


🟠 Warning — AppImage removal scopes do not match their labels

Rule: CORRECTNESS-001

The config depth deletes the file and config directory but not the desktop entry, despite the UI reporting “File, desktop entry, and config removed.” The desktop-removal path also ignores the desktopPath already discovered for lowercase filenames.

Suggested resolution: Carry the discovered AppImage path and desktop path with each list item, and make the config depth delete both that exact desktop entry and the intended config directory before reporting success.

clankus-aurelius · 2026-09-23T09:37:28Z

+	} catch {
+		// ignore
+	}
+	if (!appUrl) {
+		return { ok: true, error: null, updateAvailable: false };
+	}
+	try {
+		const response = await fetch(appUrl, { method: "HEAD" });
+		if (!response.ok) {
+			return { ok: true, error: null, updateAvailable: false };
+		}
+		const lastModified = response.headers.get("last-modified");
+		if (lastModified) {
+			const remoteTime = new Date(lastModified).getTime();
+			return {
+				ok: true,
+				error: null,
+				updateAvailable: remoteTime > localMtime,
+			};
+		}
+	} catch {
+		// ignore network errors
+	}
+	return { ok: true, error: null, updateAvailable: false };


🟠 Warning — Failed or unsupported update checks report up to date

Rule: CORRECTNESS-001

Missing update URLs, failed HEAD requests, non-success responses, and absent Last-Modified headers all return a successful updateAvailable: false. The action therefore tells users the AppImage is up to date when no comparison was performed.

Suggested resolution: Return a failure or explicit unsupported result whenever update metadata cannot be obtained, and only report up to date after a valid remote comparison.

clankus-aurelius

All eight previously reported issues remain unresolved; the new desktop-entry generation does not address the AppImage update or removal defects. Two publication-blocking issues remain.

Findings without an inline diff location

Failed or unsupported update checks report up to date (extensions/apt-manager/src/lib/appimage.ts:365, CORRECTNESS-001): Missing update URLs, failed HEAD requests, unsuccessful responses, and absent Last-Modified headers all return a successful updateAvailable: false. Newly generated desktop entries also contain only a local executable path, so they provide no update URL. Return a failure or explicit unsupported result whenever update metadata cannot be obtained, and report “up to date” only after a valid remote comparison.

Automated review found 2 publication-blocking issues.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-23T09:47:09Z

+							runPrivileged(
+								"flatpak",
+								["uninstall", "-y", pkg.name],
+								`Remove ${pkg.name}`,
+								`Remove the Flatpak application ${pkg.name}?`,
+								pkg.installation,
+							)
+						}
+					/>
+				) : (
+					<Action
+						title={`Install ${pkg.name}`}
+						icon={Icon.Plus}
+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["install", "-y", "flathub", pkg.name],
+								`Install ${pkg.name}`,
+								null,


🟠 Warning — Flatpak actions omit the installation scope

Rule: CORRECTNESS-001

The selected installation only controls privilege handling; install and uninstall arguments omit the corresponding --user or --system flag, so they can target the wrong installation or fail.

Suggested resolution: Add the scope flag derived from pkg.installation to both Flatpak argument arrays.

clankus-aurelius · 2026-09-23T09:47:10Z

+							runAptUpgradeAll,
+							"Update all packages",
+							["upgrade", "-y", "--with-new-pkgs"],
+							"Run apt update then upgrade all packages?",
+						)
+					}
+					extraActions={
+						<Action.RunInTerminal
+							title="Retry in Terminal (sudo)"
+							icon={Icon.Terminal}
+							args={["sudo", "apt-get", "upgrade", "-y", "--with-new-pkgs"]}
+							options={{ hold: true }}
+						/>
+					}
+				/>
+				<RootItem
+					title="Clean up system"
+					subtitle="autoremove --purge then autoclean"
+					icon={Icon.Eraser}
+					shortcut={{ key: "k", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					destructive
+					onAction={() =>
+						runAndShow(
+							runAptCleanup,
+							"Clean up system",
+							["autoremove", "-y", "--purge"],


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade, omitting apt-get update, while the cleanup retry receives only autoremove, omitting autoclean. These retries do not perform the operations presented to users.

Suggested resolution: Make each retry execute the complete confirmed sequence, or expose the stages separately with accurate labels.

clankus-aurelius · 2026-09-23T09:47:10Z

+		<Form
+			navigationTitle="Add Repository"
+			isLoading={isSubmitting}
+			actions={
+				<ActionPanel>


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails.

Suggested resolution: Inspect the result, show actionable failure feedback, and keep an appropriate view open so the update can be retried.

clankus-aurelius · 2026-09-23T09:47:10Z

+		}
+	}
+	return results;
+}
+
+export function slugify(input: string): string {
+	const slug = input
+		.trim()
+		.toLowerCase()
+		.replace(/[^a-z0-9._-]+/g, "-")
+		.replace(/^-+|-+$/g, "")
+		.slice(0, 80);
+	return slug || "custom";


🟠 Warning — Repository errors advertise a nonexistent retry action

Rule: UX-001

Both missing-pkexec errors direct users to a “Retry in Terminal” action, but repository write and delete flows provide no such action.

Suggested resolution: Add a terminal retry to repository operations or change these errors to describe the available recovery path.

clankus-aurelius · 2026-09-23T09:47:10Z

+				const { writeFileSync } = await import("node:fs");
+				writeFileSync(targetPath, bytes);
+			} catch {
+				const fs = await import("node:fs");
+				await new Promise<void>((resolve, reject) => {
+					const stream = fs.createWriteStream(targetPath);
+					stream.on("finish", () => resolve());
+					stream.on("error", (e) => reject(e));
+					stream.write(bytes);
+					stream.end();
+				});
+			}
+			try {
+				chmodSync(targetPath, 0o755);
+			} catch {
+				// chmod may fail silently
+			}
+		} catch (err) {
+			return {
+				ok: false,
+				error: `Download failed: ${err instanceof Error ? err.message : String(err)}`,
+			};
+		}
+	} else {
+		const srcPath = source.path;
+		if (!existsSync(srcPath)) {
+			return { ok: false, error: `File not found: ${srcPath}` };
+		}
+		targetPath = join(appsDir, basename(srcPath));
+		try {
+			copyFileSync(srcPath, targetPath);
+			try {


🔴 Blocking — Arbitrary URLs are installed as executable files

Rule: SECURITY-001

Any user-supplied URL is downloaded without source, integrity, or content validation, written into ~/Applications, and marked executable.

Suggested resolution: Remove arbitrary-URL executable installation, or restrict downloads to verified releases from established sources with integrity or authenticity verification; otherwise direct users to install AppImages themselves.

clankus-aurelius · 2026-09-23T09:47:10Z

+						}
+					/>
+				)}
+				{copyName}


🔴 Blocking — Installed AppImages receive APT actions

Rule: CORRECTNESS-001

The kind === "installed" branch returns before the AppImage branch, so AppImages under Installed Packages receive APT remove and reinstall actions, potentially affecting an unrelated Debian package with the same name.

Suggested resolution: Handle pkg.manager === "appimage" before branches based only on list kind.

clankus-aurelius · 2026-09-23T09:47:10Z

+			if (existsSync(desktopFile)) {
+				rmSync(desktopFile, { force: true });
+			}
+		}
+		if (depth === "config") {
+			const configDir = join(homedir(), ".config", targetName);
+			if (existsSync(configDir)) {
+				rmSync(configDir, { recursive: true, force: true });
+			}
+		}
+	} catch (err) {
+		return {
+			ok: false,
+			error: `Remove failed: ${err instanceof Error ? err.message : String(err)}`,
+		};
+	}
+	return { ok: true, error: null };
+}


🟠 Warning — AppImage removal scopes do not match their labels

Rule: CORRECTNESS-001

The config depth removes neither the desktop entry nor the discovered desktopPath, despite reporting that the file, desktop entry, and config were removed. The desktop-removal path also reconstructs a path instead of using the discovered entry.

Suggested resolution: Carry the discovered AppImage and desktop paths with each item, and delete the exact desktop entry for both desktop and config removal depths before reporting success.

- User: ~/.local/share/applications/ (no privileges needed) - System: /usr/share/applications/ (via pkexec tee) - User prompted to choose location before installing - installAppImage returns targetPath for desktop file creation - installDesktopFile creates .desktop entry separately from binary

clankus-aurelius

Two publication-blocking defects remain, along with seven unresolved operational and feedback issues. The incremental desktop-entry changes also leave system entries behind during removal and introduce an unhandled write failure.

Automated review found 2 publication-blocking issues.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-23T09:59:26Z

+		try {
+			const response = await fetch(url);
+			if (!response.ok) {
+				return { ok: false, error: `Download failed: ${response.status}` };
+			}
+			const buffer = await response.arrayBuffer();
+			const bytes = Buffer.from(buffer);
+			writeFileSync(targetPath, bytes);
+			chmodSync(targetPath, 0o755);
+		} catch (err) {
+			return {
+				ok: false,
+				error: `Download failed: ${err instanceof Error ? err.message : String(err)}`,


🔴 Blocking — Arbitrary URLs are installed as executables

Rule: SECURITY-001

Any user-supplied URL is downloaded without source, integrity, or content validation, written into ~/Applications, and marked executable.

Suggested resolution: Remove arbitrary-URL installation, restrict downloads to authenticated releases from established sources with integrity verification, or direct users to install downloaded AppImages themselves.

clankus-aurelius · 2026-09-23T09:59:26Z

+	if (kind === "installed") {
+		return (


🔴 Blocking — Installed AppImages receive APT actions

Rule: CORRECTNESS-001

The installed-list branch returns before the AppImage branch, so installed AppImages receive apt-get remove and reinstall actions and may affect an unrelated Debian package with the same name.

Suggested resolution: Handle pkg.manager === "appimage" before branches based only on list kind.

clankus-aurelius · 2026-09-23T09:59:26Z

+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["uninstall", "-y", pkg.name],
+								`Remove ${pkg.name}`,
+								`Remove the Flatpak application ${pkg.name}?`,
+								pkg.installation,
+							)
+						}
+					/>
+				) : (
+					<Action
+						title={`Install ${pkg.name}`}
+						icon={Icon.Plus}
+						onAction={() =>
+							runPrivileged(
+								"flatpak",
+								["install", "-y", "flathub", pkg.name],
+								`Install ${pkg.name}`,
+								null,
+								pkg.installation,


🟠 Warning — Flatpak actions omit the installation scope

Rule: CORRECTNESS-001

Install and uninstall arguments omit --user or --system even though each package records its installation scope, so the command can target the wrong installation.

Suggested resolution: Include the flag derived from pkg.installation in both Flatpak argument arrays.

clankus-aurelius · 2026-09-23T09:59:26Z

+							["upgrade", "-y", "--with-new-pkgs"],
+							"Run apt update then upgrade all packages?",
+						)
+					}
+					extraActions={
+						<Action.RunInTerminal
+							title="Retry in Terminal (sudo)"
+							icon={Icon.Terminal}
+							args={["sudo", "apt-get", "upgrade", "-y", "--with-new-pkgs"]}
+							options={{ hold: true }}
+						/>
+					}
+				/>
+				<RootItem
+					title="Clean up system"
+					subtitle="autoremove --purge then autoclean"
+					icon={Icon.Eraser}
+					shortcut={{ key: "k", modifiers: ["cmd"] } as Keyboard.Shortcut}
+					destructive
+					onAction={() =>
+						runAndShow(
+							runAptCleanup,
+							"Clean up system",
+							["autoremove", "-y", "--purge"],
+							"Run autoremove --purge and autoclean?",
+						)
+					}
+				/>
+			</List.Section>
+			<List.Section title="Repositories">
+				<RootItem


🟠 Warning — Terminal retries omit stages of multi-step operations

Rule: CORRECTNESS-001

The update-all retry runs only upgrade and the cleanup retry receives only autoremove, so neither retry performs the complete operation presented to the user.

Suggested resolution: Make each terminal retry execute the complete confirmed sequence, or expose the stages separately with accurate labels.

clankus-aurelius · 2026-09-23T09:59:26Z

+		<Form
+			navigationTitle="Add Repository"
+			isLoading={isSubmitting}
+			actions={
+				<ActionPanel>
+					<Action.SubmitForm
+						title="Add Repository"


🟠 Warning — Package-list update failures are ignored

Rule: UX-001

The result of runAptUpdate() is discarded and the form closes even when updating package lists fails.

Suggested resolution: Inspect the operation result, show actionable failure feedback, and keep an appropriate view open for retry.

clankus-aurelius · 2026-09-23T09:59:26Z

+	}
+	const result = await run("pkexec", ["tee", path], {
+		input: content,
+		timeout: 120_000,
+	});
+	return result.ok
+		? null
+		: result.stderr.trim() || result.stdout.trim() || "Failed to write file";
+}
+
+export async function deleteFilePrivileged(
+	path: string,
+): Promise<string | null> {
+	if (!pkexecAvailable()) {
+		return "`pkexec` was not found in PATH. Install polkit (e.g. `apt install policykit-1`) or use the 'Retry in Terminal' action with sudo.";
+	}
+	const result = await run("pkexec", ["rm", "-f", path], { timeout: 120_000 });
+	return result.ok ? null : result.stderr.trim() || "Failed to delete file";
+}
+
+/**
+ * Apply a set of pending file changes. Empty replacements delete the file,
+ * everything else overwrites it via `pkexec tee`.


🟠 Warning — Repository errors advertise a nonexistent retry action

Rule: UX-001

Both missing-pkexec errors tell users to use a “Retry in Terminal” action, but repository write and delete flows provide no such action.

Suggested resolution: Add a terminal retry for repository operations or change the errors to describe an available recovery path.

clankus-aurelius · 2026-09-23T09:59:26Z

+	}
+	try {
+		if (depth === "file" || depth === "desktop" || depth === "config") {
+			rmSync(targetPath, { recursive: true, force: true });
+		}
+		if (depth === "desktop") {
+			const desktopFile = targetPath.replace(/\.AppImage$/i, ".desktop");
+			if (existsSync(desktopFile)) {
+				rmSync(desktopFile, { force: true });
+			}
+			const userDesktop = join(getUserDesktopDir(), `${targetName}.desktop`);
+			if (existsSync(userDesktop)) {
+				rmSync(userDesktop, { force: true });
+			}
+			const sysDesktop = join(
+				"/usr/share/applications",
+				`${targetName}.desktop`,
+			);
+			if (existsSync(sysDesktop)) {
+				rmSync(sysDesktop, { force: true });
+			}
+		}
+		if (depth === "config") {
+			const configDir = join(homedir(), ".config", targetName);
+			if (existsSync(configDir)) {
+				rmSync(configDir, { recursive: true, force: true });
+			}
+		}
+	} catch (err) {
+		return {
+			ok: false,
+			error: `Remove failed: ${err instanceof Error ? err.message : String(err)}`,
+		};
+	}


🟠 Warning — AppImage removal does not match its selected depth

Rule: CORRECTNESS-001

The config depth never removes desktop entries despite reporting that it did. System desktop entries are also removed with an unprivileged rmSync after the AppImage has already been deleted, which normally fails and leaves a partial removal.

Suggested resolution: Track the exact discovered desktop path, remove desktop entries for both desktop and config depths, and use a privileged operation for entries under /usr/share/applications.

clankus-aurelius · 2026-09-23T09:59:26Z

+		writeFileSync(desktopPath, desktopContent);
+	} else {


🟠 Warning — User desktop-entry write failures are unhandled

Rule: UX-001

writeFileSync is outside the surrounding error handling, so permission or I/O failures reject installDesktopFile instead of returning the error consumed by the installation view.

Suggested resolution: Wrap directory creation and the desktop-file write in one try/catch and return a failed result containing the write error.

clankus-aurelius · 2026-09-23T09:59:27Z

+		return { ok: true, error: null, updateAvailable: false };
+	}
+	try {
+		const response = await fetch(appUrl, { method: "HEAD" });
+		if (!response.ok) {
+			return { ok: true, error: null, updateAvailable: false };
+		}
+		const lastModified = response.headers.get("last-modified");
+		if (lastModified) {
+			const remoteTime = new Date(lastModified).getTime();
+			return {
+				ok: true,
+				error: null,
+				updateAvailable: remoteTime > localMtime,
+			};
+		}
+	} catch {
+		// ignore network errors
+	}
+	return { ok: true, error: null, updateAvailable: false };
+}


🟠 Warning — Unsupported or failed update checks report up to date

Rule: CORRECTNESS-001

Missing update URLs, unsuccessful HEAD requests, absent Last-Modified headers, and network failures all return ok with updateAvailable false. Generated desktop entries contain only a local executable path, so newly installed AppImages always take this path.

Suggested resolution: Return a failure or explicit unsupported result whenever valid remote update metadata cannot be obtained, and report “up to date” only after a successful comparison.

…ew findings - Install Package dialog detects extension and dispatches: .AppImage copy with metadata extraction, .deb via apt-get, .flatpak via flatpak (with explicit installation scope flag) - Only install AppImages from user-provided local files (no arbitrary URL downloads); drop URL-dependent update check - Harden removeAppImage: remove system desktop entries via pkexec before deleting the binary, cover both desktop/config depths - Surface failed metadata extraction as a warning instead of silent success - Handle user desktop-entry write failures; make repo pkexec errors describe an available recovery path instead of a nonexistent retry action - Complete terminal retries for multi-stage update/cleanup operations - Inspect runAptUpdate() result in AddRepo and show failure feedback - Order package actions so AppImages/Flatpaks never reach apt actions

clankus-aurelius

The incremental changes resolve most prior findings, but introduce one publication-blocking AppImage execution path. Two result-view flows also discard their terminal recovery action immediately.

Automated review found 1 publication-blocking issue.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-25T08:42:27Z

+		}
+		for (const entry of entries) {
+			if (/\.(metainfo|appdata)\.xml$/i.test(entry)) {
+				const full = join(dir, entry);


🔴 Blocking — AppImage metadata extraction executes an arbitrary downloaded file

Rule: SECURITY-001

After the user selects any .AppImage by filename, the extension makes it executable and launches it with --appimage-extract. An arbitrary executable can ignore that argument and run its payload immediately; the README explicitly directs users to select AppImages they downloaded themselves.

Suggested resolution: Do not execute the selected AppImage during installation. Extract metadata with a non-executing, established parser/tool, or omit automatic metadata extraction and only copy the file.

clankus-aurelius · 2026-09-25T08:42:27Z

+					updateResult.stderr.trim().slice(0, 140) ||
+					`exit code ${updateResult.code ?? "unknown"}`;
+				push(
+					<RunResult
+						heading="Update package lists"
+						title="Update package lists"
+						result={updateResult}
+						sudoArgs={["update"]}
+					/>,
+				);


🟠 Warning — Update failure retry view is immediately popped

Rule: UX-001

On update failure, push adds the RunResult view and the following pop() immediately removes the top view. This discards the detailed output and terminal retry, including when the error directs the user to that retry action.

Suggested resolution: Pop the repository form before pushing RunResult, and return without another pop.

clankus-aurelius · 2026-09-25T08:42:27Z

+			pop();
+			return;


🟠 Warning — Package-install result view is immediately popped

Rule: UX-001

The .deb flow pushes RunResult and then immediately pops the top navigation view, discarding the output and sudo retry. The Flatpak flow repeats the same sequence.

Suggested resolution: Pop the installation form before pushing the result view in both the .deb and Flatpak branches.

Suggested change

pop();

return;

pop();

showRunResult(label, result, ["install", "-y", path]);

…iew flow

clankus-aurelius

The prior findings are resolved, but the replacement AppImage metadata path does not handle the embedded filesystem offset used by standard Type 2 AppImages.

Automated extension review passed. A maintainer review is still required.

This is an AI-generated first pass and may be mistaken. If a finding is unclear or incorrect, reply in the relevant thread and mention @aurelleb.

clankus-aurelius · 2026-09-25T09:05:16Z

+	const tempDir = mkdtempSync(join(tmpdir(), "appimage-metadata-"));
+	try {
+		const result = await run(unsquashfs, ["-d", join(tempDir, "root"), appPath], {


🟠 Warning — Metadata extraction ignores the AppImage filesystem offset

Rule: CORRECTNESS-001

A Type 2 AppImage contains an ELF runtime before its SquashFS payload. Invoking unsquashfs directly on the whole AppImage without its -o offset fails to locate that payload, so common AppImages always fall back to filename-only metadata despite squashfs-tools being installed.

Suggested resolution: Read and validate the AppImage's SquashFS offset, then pass it to unsquashfs with -o; continue treating extraction failure as optional metadata failure.

feat: add apt-manager extension

a780449

clankus-aurelius added the ai-reviewing Automated extension review is running label Sep 22, 2026

clankus-aurelius requested changes Sep 22, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 22, 2026

Update extensions/apt-manager/src/lib/exec.ts

0ca7c23

Co-authored-by: Clankus Aurelius <clankus@aurelle.dev>

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 22, 2026

clankus-aurelius requested changes Sep 22, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 22, 2026

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 22, 2026

clankus-aurelius approved these changes Sep 22, 2026

View reviewed changes

clankus-aurelius removed the ai-reviewing Automated extension review is running label Sep 22, 2026

clankus-aurelius added the human-reviewable Automated review passed; ready for maintainer review label Sep 22, 2026

clankus-aurelius added ai-reviewing Automated extension review is running and removed human-reviewable Automated review passed; ready for maintainer review labels Sep 22, 2026

chore: add AGENT.md and .agent to gitignore, enable commonjs module

abb8422

clankus-aurelius approved these changes Sep 22, 2026

View reviewed changes

clankus-aurelius added human-reviewable Automated review passed; ready for maintainer review and removed ai-reviewing Automated extension review is running labels Sep 22, 2026

clankus-aurelius added ai-reviewing Automated extension review is running and removed human-reviewable Automated review passed; ready for maintainer review labels Sep 23, 2026

clankus-aurelius requested changes Sep 23, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 23, 2026

fix: auto-generate .desktop file after AppImage install

2b4b427

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 23, 2026

clankus-aurelius requested changes Sep 23, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 23, 2026

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 23, 2026

clankus-aurelius requested changes Sep 23, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 23, 2026

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 25, 2026

clankus-aurelius requested changes Sep 25, 2026

View reviewed changes

clankus-aurelius added ai-changes-requested Automated review found blocking issues and removed ai-reviewing Automated extension review is running labels Sep 25, 2026

fix(apt-manager): use unsquashfs for AppImage metadata, fix install v…

d22eef8

…iew flow

clankus-aurelius added ai-reviewing Automated extension review is running and removed ai-changes-requested Automated review found blocking issues labels Sep 25, 2026

clankus-aurelius approved these changes Sep 25, 2026

View reviewed changes

clankus-aurelius added human-reviewable Automated review passed; ready for maintainer review and removed ai-reviewing Automated extension review is running labels Sep 25, 2026

-			pop();
-			return;
+pop();
+			showRunResult(label, result, ["install", "-y", path]);

Conversation

ali00209 commented Sep 22, 2026

Summary

Features

How it works

Requirements

Uh oh!

clankus-aurelius commented Sep 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clankus-aurelius left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

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!

clankus-aurelius 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!

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!

clankus-aurelius 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!

Choose a reason for hiding this comment

Uh oh!

clankus-aurelius commented Sep 22, 2026

Uh oh!

clankus-aurelius left a comment

Choose a reason for hiding this comment

Uh oh!

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!

clankus-aurelius 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

clankus-aurelius commented Sep 22, 2026 •

edited

Loading