* feat(windows): add desktop shortcut action to the app menu for each craft apps
* i18n: translate Add desktop shortcut for complete catalogs
* fix(windows): create desktop shortcuts on a background thread
* fix: use act_command and update Capabilities in UI tests
* fix(windows): merge main, refuse existing shortcuts, i18n toasts
* fix: use Event::Notice for desktop shortcut toasts (don't clear job phase)
* fix(windows): write desktop shortcuts with mslnk (no PowerShell)
* test(windows): cover desktop shortcut create and no-overwrite cases
* fix(windows): no-clobber desktop shortcut publish and stronger .lnk tests
* fix: fmt and Capabilities.desktop_shortcuts in remaining UI tests
* fix: Capabilities.desktop_shortcuts in app tests; ka and zh-TW i18n
* style: cargo fmt
* fix: Capabilities.desktop_shortcuts in launcher tests; allow unwrap in shortcut tests
* test(windows): accept relative path evidence in .lnk assertions on CI
* fix: Ukrainian Capabilities/i18n; canonicalize paths in .lnk test assert
* fix(windows): restore main process.rs and re-apply desktop shortcut only
## Summary
Fixes the MaterialCraft **Website** action opening the GitHub repository instead of the published ArtCraft page.
- Updates MaterialCraft’s catalog `site` URL to `https://getartcraft.com/apps/materialcraft`
- Updates the catalog regression test to cover the official Website URL
Fixes#1264
## Validation
- `cargo fmt --check`
- `git diff --check`
* feat(install): download one app at a time, in screen order
Downloads running side by side split the connection and each one crawls.
Apps now take turns: a download asked for while another is running waits
(shown as "Waiting for another download…", cancellable), and waiting
downloads start in the order the apps are listed on screen, following the
current sort. A download already finished on an earlier try skips the line,
and the next download starts as soon as the previous one is verified, while
that app installs.
- native: new `downloads::Downloads` queue (`install::DOWNLOADS`)
- protocol: `JobPhase::Queued`, `Command::DownloadOrder`
- ui: sends the sorted app order when it changes; new string in every catalog
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(install): queue apps hidden by a filter or search in suite order
Only the apps on screen are sent as the download order; the queue puts any
other waiting app after them, in suite order, instead of by its place in the
current sort. Tests cover a hidden app, a search, and the queue's fallback.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(install): let users choose how many downloads run at once
A "Simultaneous downloads" setting (1 to 4, default 1) in Settings > Updates,
sent in BackendOptions next to prereleases. The download queue counts running
downloads against it instead of allowing one: raising it starts waiting
downloads at once, lowering it lets running ones finish. Settings saved before
it existed allow one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(install): take a place in the download line when a job starts
Jobs joined the line only on reaching their download, so with nothing
downloading the first to get there started, even below others on screen: an
Update all batch started in suite order. start_job now takes the job's place
(Downloads::join) before its thread runs, and places not yet at their download
count when choosing who goes next. A place dropped before its turn (the job
failed, was stopped or found its file already downloaded) leaves the line.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(install): document the functions the download queue touches
CodeRabbit's docstring coverage check was at 38% of the functions in the diff.
Doc comments on the queue, its tests, and the backend and UI functions that
changed. No code changes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(install): give the platform-gated test jobs a place in line
Two Job literals in tests that only build on Linux and Windows
(a_downgrade_refuses_anything_but_an_msi_over_an_msi_install and
a_mac_downgrade_goes_ahead_without_a_package_to_put_back) were missing the new
place field, so the native tests didn't compile there.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(install): give the Windows MSI test a place in line, align the queued wording
The Windows-only integration test built a Job without the new place
field. The compact launcher-update row said "Waiting for other installs…"
for a queued download; it now matches the detail row.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(install): let users turn the download limit off
"No limit" in Settings → Updates lets every download run at once, as the
launcher did before. The default stays at one.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(install): keep the download queue building after the rebase onto main
Main grew new Job fields, two more UI catalogs (zh-TW, ka) and a settings
test that picked the nearest combo box. The test Job literal and both
catalogs get what the queue added, and the test now finds the install-format
chooser by its label, since the downloads dropdown sits closer to it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MS5Qb6riBMzoujge5GuGZF
* fix(install): join the whole batch to the download line before any worker starts
An "Update all" started each worker right after joining the line, so the
first worker could take a free slot before a row above it had joined.
install_all now prepares every job first and starts the workers after.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MS5Qb6riBMzoujge5GuGZF
* test(install): check the batch path itself takes every place before a worker starts
The test called prepare_job directly, so putting install_all back to
starting each job as it is prepared would still have passed. The backend
now runs workers through a spawn function a test can replace; the test
holds the workers and checks, at each start, that all apps are in line.
Reverting install_all makes it fail.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MS5Qb6riBMzoujge5GuGZF
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: launcher-403-review <review@local>
- The entry in a client's configuration (and in the copied JSON, VS Code and
Codex formats) is `ArtCraft`, which clients show as the integration's
name, instead of `craft-apps`.
- Right after Add, a client the launcher can restart (Claude Desktop on
Windows and macOS) gets a note on why it must restart (it loads MCP
servers only when it starts; restarting closes it, including a reply in
progress) and a Restart button (`Command::McpRestartClient`). On Windows
only Claude Desktop's processes are stopped, picked by install folder
(Store package or classic install), never `claude.exe` by name, which is
also Claude Code's CLI; it is started again through its Start menu entry.
On macOS it quits through AppleScript and `open -a Claude` starts it.
- Three strings in all twelve catalogs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The note says what the switch does: while it is on, MCP clients reach every
installed Craft app through one entry; while it is off, no agent reaches
them and the entries added here are removed.
- Quick install: Add / Remove per client found here, with a note to restart
the client.
- Other clients: copy the configuration as JSON (`mcpServers`: Claude
Desktop, Cursor, LM Studio, Windsurf and most others), for VS Code
(`servers`, `type: stdio`) or for Codex (TOML `[mcp_servers.craft-apps]`),
naming the gateway copy clients start (`McpAgents::gateway`). The formats
live in `artcraft_launcher_core::mcp_config`, with `SERVER_KEY`.
- Nine strings, translated in all twelve catalogs; the old note is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Windows redirects a packaged app's %APPDATA% into its package, so the
Microsoft Store install of Claude Desktop reads
%LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude and never
sees %APPDATA%\Claude: Settings showed it as not installed. The launcher
now uses the package's folder when only the Store install is there.
- Settings no longer has an Experimental features box: AI-MCP and
AI-MODELS are turned on in ArtCraft/flags.toml or with CRAFT_FLAGS, not by
a switch. SetFlag, Event::Flags and FlagState go, with the box's strings
in every catalog. The AI agents box still shows only while AI-MCP is on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Local services box from #1296 managed one LM Studio/Bionic entry per app
and an HTTP bridge on port 12345 that craft-ai-mcp no longer serves. Both are
replaced by the gateway: one craft-ai-mcp entry per MCP client.
Removed: local_mcp.rs, the McpSetService/McpSetBridge commands, the
McpService/McpBridge state, the Local services box and its strings. Kept, in
agents.rs: detecting the installed apps and their CLIs (InstalledApp) and
finding craft-ai-mcp beside the launcher (ARTCRAFT_LAUNCHER_GATEWAY_PATH for
development). Event::Mcp carries the AI agents state only.
Settings gets an Experimental features box with a switch per feature flag
from craft-flags (storytold/craft-libs#1118): AI-MCP and AI-MODELS, off by
default, shared with every Craft app through ArtCraft/flags.toml. A flag set
by CRAFT_FLAGS shows as such and can't be switched.
The AI agents box shows only while AI-MCP is on; the backend refuses to turn
agents on or add a client without it, and turning AI-MCP off turns agents off
and removes the client entries.
craft-flags is pinned to the head of storytold/craft-libs#1119 until it merges.
Settings gets an "AI agents" box. "Let AI agents use Craft apps" writes the
installed apps and their CLIs into ArtCraft/mcp/apps.json, the list the
craft-ai-mcp gateway reads (storytold/craft-ai-integrations#197). Each MCP
client found on this machine (Claude Desktop, Claude Code, Cursor, LM Studio)
gets an Add / Remove button for one entry, `craft-apps` -> `craft-ai-mcp
--stdio`, through which the agent reaches every app.
Turning the switch off removes the list and every entry the launcher added.
A client configuration that does not parse is never overwritten, and other
servers and keys in it are kept. While agents are on, the app list is
refreshed whenever Settings asks for the MCP state, so a newly installed app
is reachable too. Without craft-ai-mcp beside the launcher, the box says so
and offers no switch.
Refs storytold/craft-ai-integrations#195
* Load and verify the signed website catalog with bundled fallback
* Preserve signed fixture bytes across platforms and fix web lint
* Document the opt-in live catalog integration check
The launcher's self-update downloads the release file of the format the
running copy was installed from, and stops when the release has none. A
copy run outside the macOS app bundle updates from a .tar.gz, and the
launcher's macOS releases (v0.17.0 to v0.19.0) ship only the .dmg. Such a
copy was still offered "Update and restart", which then failed.
self_update::installs_from looks for that file with craft-update's own
pick_asset, as the update does. The backend reports self-update as
available, and starts one, only when the release has the file; otherwise
the update dialog and banner offer the download. The doc comment on
Capabilities::self_update states the new condition.
- save_servers now refuses to overwrite a present-but-malformed ng-mcp.json
instead of clobbering it (prevents lossy writes).
- enable/disable/remove_service only manage stdio entries; a same-named entry
of another connection type is left alone and we fall back to the deterministic id.
- Save failures are surfaced via a new Event::McpError shown as an error toast,
so a failed toggle is never silent.
- Settings now explain that the bridge port applies when the toggle flips.
Adds tests for the malformed-config refusal and the non-stdio name guard.
Detect installed Craft apps and the unified craft-ai-mcp bridge, and let the
user toggle each on/off as an MCP server in LM Studio / Bionic's ng-mcp.json.
Plumbing:
- core/protocol: Command::McpState | McpSetService { service_id, enabled } |
McpSetBridge { port, enabled }; Event::Mcp { services, bridge } plus the
McpService / McpBridge types (Default-derived).
- native/backend: mcp_state(&Shared) reads the manifest + a fresh detection
snapshot and ng-mcp.json to report which apps have usable CLIs (with their
current on/off state) and whether the bridge binary is present (found?
version?). Emits Event::Mcp after every detection pass and after each change.
- native/local_mcp: BRIDGE_ID now public; candidate_bridge_paths collapsed to a
let-chain (clippy).
UI (egui):
- app.rs: LauncherUi holds mcp_services / mcp_bridge / bridge_port (+ the once-
synced flag) and handles Event::Mcp.
- dialogs.rs: opening Settings requests Command::McpState once; the request is
reset when no dialog is on screen so reopening re-fetches fresh state.
- settings_dialog.rs: new "Local services" panel (only where manage_apps). A
collapsible "Craft apps" section lists each installed app as a toggle with
its CLI path shown in muted text; the unified bridge row has an editable,
accessible-labelled port field and a toggle that applies the current port.
i18n: translations for every new literal across all complete catalogs (ru, zh-CN,
zh-TW, de, fr, pt-BR, es, cs, pl, hu, ja, ka).
All tests pass; clippy clean of denied lints.
Add MailCraft (UCS-Care-Group/mailcraft) to the catalog as a community app by
UCS Care Group, with its icon, licences, details page and tagline in every
complete catalog. Downloads are checked against its SHA256SUMS.txt. Its macOS
builds are unsigned, so mac_team is None: the launcher opens an installed copy
there but installs nothing.
AGENTS.md lists its repo as an approved community app (approved 2026-11-08).
- Support ArtCraft Studio's published MSI and DMG asset formats in parse_asset_name while preserving existing asset naming
- Add real artcraft-release.json fixture and test asset selection across desktop platforms
- Add runs_on to CraftApp and filter out ArtCraft Studio on FreeBSD across backend and UI
- List ArtCraft Studio as app #01 in the README Craft App Suite table and xtask APPS array
- When a copy appears between a publisher looking and taking reporting,
the answer uses the view its detection asked for (last_system_kinds)
instead of probing there. A copy only enters installed through
publish_detected, which asks first.
- Event::Installable's doc covers both emissions: in the batch with the
Latest or Detected it depends on, and alone when only the plan changes.
- Tests: no probe under the lock (expired view kept), a plan report's
answer follows the current settings, a concurrent poll never splits a
pair.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The UI guessed from any download this platform takes, but an install keeps
the way a copy was installed (an AppImage with an AppImage, an MSI with an
MSI), so an AppImage copy with a .deb-only release still showed Update,
was announced and started automatically, and then failed. The backend now
sends Event::Installable, from the same plan an install makes, before each
Latest and Detected it depends on and whenever the plan changes. The UI
uses it for installed copies and keeps its own check where there is no
answer (the web build).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An installed app whose newer release has no installable download here
showed Update available, counted in Updates, notified and was picked by
auto-update, and installing failed with 'has no download'. It now reports
Installed, like a repository-managed copy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Choose version, and the launcher's own version list in Settings, showed
only the tag. Each row now adds, at its right, the day the release came
out and the size of the package this machine would download, in the
launcher's usual date and size formats. Either is left out when unknown;
the row keeps the tag as its name and carries them as its description.
On the selected row they take the row's text colour, not the muted grey.
The size follows the backend's choice of package. An app's installed
copy keeps its format (an MSI stays an MSI, the launcher's Windows copy
is its portable ZIP, an AppImage stays an AppImage), else the preferred
formats among those it installs here; FreeBSD always takes the tarball.
Where that depends on package managers the UI can't see (other Linux
installs), the row gives the date alone. The launcher's own rows size
what its self-update downloads, the format the running copy was
installed as, which the backend now reports once it knows; until then
the manual download, except on Linux.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each installed app's menu gains "Launch options…": flags typed there are
saved in Settings.launch_flags (app.ron, keyed by catalog id) and added to
the app's command line on Open. core::args::split turns the text into
arguments (whitespace, "…"/'…' quoting, backslashes kept for Windows
paths) and refuses an unclosed quote, both in the dialog and at launch.
Flatpak, launcher-unpacked, plain binary and macOS .app installs all pass
the flags through; strings are translated in every complete catalog.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): tighten tag, file name and notice link checks (#776, #782)
- Tags from GitHub, the feed and the latest-release redirect must be up to
64 of [A-Za-z0-9._+-], not starting with a dot (release::valid_tag).
A feed tag like `v0.6.0~beta-` plus a bidi override still read as
0.6.0-beta and was served; such a release now falls back to GitHub.
- Asset file names use the same allowlist, with no trailing dot and no
Windows device names (CON, nul.txt, COM1.msi).
- Notice links go through safe_web_link, so plain http and user-info
links are dropped, as in release notes.
- The 20-notice cap now counts the rename notices too.
* fix(core): treat only COM1-COM9 and LPT1-LPT9 as Windows device names
Microsoft's naming rules reserve COM1 to COM9 and LPT1 to LPT9 (plus the
superscript forms, which the ASCII allowlist already refuses), not COM0
or LPT0. Match them with a slice pattern instead of indexing.
* test(core): cover the hostile tags, names and links from review (#776, #782)
Adds a NUL in a tag, a file: notice link, 1,000 announcements, and direct
checks that a download link and a redirect use the same rules.
* fix(core): keep rename notices inside the notice cap (#782)
Twenty announcements left no room, so the cap cut the rename added after them.
* docs(core): notice links are https only now (#776)
Command::Replace carried only the app. Between the "already exists"
question and the answer, the release can change (a new version, another
asset name, another folder), and the install then recomputed its
destination and wrote over a different existing file with replace=true.
Replace now carries the path from Event::Occupied. The backend checks
what is in the way again: if it is exactly that path the install
overwrites it; if something else is in the way it asks again; if nothing
is, it installs without leave to overwrite.
Review of #1147:
- A failed OCI migration precheck (no version in the remote's AppStream data, polkit refusing
remote-add, offline) now falls back to the bundle update instead of failing it; only errors
once the reinstall starts are reported. The ref must list exactly the selected version.
- `flatpak list` names a named installation `system (<name>)`; the parser keeps `<name>`, and
one packages::flatpak_scope builds the --user/--system/--installation= argument everywhere.
- A repository-managed Flatpak on a pinned or nightly track gets the "update with flatpak"
hint instead of a plain `flatpak update`, and status no longer offers a GitHub version for it.
- The migration refuses while the app runs; the origin check after the reinstall can't be
cancelled; is_flatpark_origin matches only `flatpark`; settings_install keeps its doc; the
no-op oci_migration Cargo features are gone.
Signed bundles (storytold/craft-common-actions#129): a signed bundle's origin has the release
key but no signature lookaside, which `flatpak build-bundle` can't record, so its first update
from the ArtCraft OCI repository fails with "no valid signatures". The updater then sets
--signature-lookaside=https://getartcraft.com/signatures on that origin once and retries;
any other origin or error is left alone.
* Add MaterialCraft to the launcher suite
* Stage MaterialCraft integration for its first published release
* Fix MaterialCraft website link and installer icon layout
* Add TextureCraft to the launcher suite
* Fix formatting of TextureCraft release fixture test
* Distinguish TextureCraft details headline from its card