* Add optional macOS Dock hiding
* Restore Dock visibility when macOS unhides the app
* Use Keep launcher in the Dock when tray mode is disabled
* Document macOS close and Dock restoration behavior
* Document launcher window and Dock lifecycle helpers
* Decouple macOS tray and Dock visibility
* Restore reopening for hidden macOS startup
* Quit on macOS window close when tray mode is off
* Added uk translation
* Update macOS verification fixtures for new Installed fields
* Add pin toggle bookmark button on app cards.
Makes pinning discoverable without the menu: outline/filled bookmark with accent when pinned, keeps menu items, hides reorder grip and Move up/down in the details drawer.
* Fix paused-row double grip and widen table for pin toggle.
actions_in already draws the leading reorder grip, so paused_actions must not reserve or draw it again. Give every table actions column room for the pin square so Update labels are not fitted away.
* Clear egui texture deltas in headless UI drivers.
Pin icons leave TexturesDelta unapplied; dropping FullOutput panicked three discarded-pass tests on gate.
Installed gained externally_managed, origin and installation, and one of
the three Installed literals in macos_verify.rs was updated. The other two
were not, so the native crate's tests don't compile on macOS. No CI job
builds macOS, so nothing caught it.
Claude-Session: https://claude.ai/code/session_01MS5Qb6riBMzoujge5GuGZF
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Fixes#595.
On Windows, start at login is a HKCU\...\CurrentVersion\Run value that stores the launcher's full exe path. is_enabled only checks that the value exists, so after the launcher is reinstalled or moved to another folder the toggle still shows "on" while the value points at an exe that is no longer there. That matches the report: Task Manager lists the entry, "Open file location" is greyed out, nothing starts at login, and turning the option off and on again fixes it (the toggle rewrites the value with the current path).
Changes:
- login::refresh(), called once at startup in the primary instance: if the Run value exists and names a program that no longer exists, it rewrites the value through set_enabled(true) and logs the old and new value. If start at login is off, or the stored program still exists or cannot be checked, nothing changes. Environment variables in the stored path are expanded first.
- An unquoted Run value is resolved by trying each whitespace-separated prefix, so a positional argument such as minimized is not treated as part of the path, and a folder named "ArtCraft - Portable" is not cut short.
- Windows ignores $APPIMAGE so a leftover value cannot be written into the Run key.
- run_value(exe) builds the value in one place, shared by set_enabled and refresh.
- Windows only; macOS and Linux set_enabled paths are unchanged.
The repaired entry takes effect from the next login after the launcher has been opened once (for example from the Start menu), since a stale entry can't start the launcher itself.
Co-authored-by: MarekSpodBiedry <73122968+MarekSpodBiedry@users.noreply.github.com>
* Linux: always batch Update all behind one password prompt
On Linux the batch is one pkexec call through the installer queue's
same-command merge, so the opt-in kept for Windows' antivirus concern
(#1235) does not apply. Settings::updates_batched() is always true there
and the checkbox is hidden; Windows keeps the opt-in.
Fixes#1414
* Free the batch before a repository-managed Flatpak updates
A repository-managed Flatpak never joins the batch's installer call, but
run_install kept its gather place until update_flatpak_app returned. In a
mixed Update all, the deb/rpm/pacman members already waiting at the
installer were held back by the Flatpak's network work or prompt, up to
the 600-second gather timeout. Linux now always batches, so leave the
gather before the Flatpak update starts.
Also assert the exact update command shape in the UI tests: one
InstallAll on Linux, one Install per app elsewhere with batch_updates off.
build: pin the craft-libs crates to craft-libs main at 453b0da, pass the release's repo to craft-update, and offer Update and Restart only to a copy that can update itself
* WSL: claim a separate single-instance port so the Windows launcher still opens
The single-instance check binds 127.0.0.1:47413. WSL shares loopback ports
with Windows (WSL 2 forwards them, WSL 1 binds Windows' own), so a launcher
running inside WSL held the Windows launcher's port: starting the Windows
launcher then reached the WSL one, got "running <version>", raised the WSL
window and exited 0 without a window. A newer Windows launcher can't take
over either: the two sides have different instance tokens, so it defers too.
Inside WSL (WSL_DISTRO_NAME, or a Microsoft kernel release) the launcher now
uses port 47414. The handshake is unchanged, so every launcher version keeps
working with every other on the same OS, and the Windows side needs no
update.
Fixes#271
* WSL: describe both ways the shared port broke the Windows launcher
The module doc said a Windows launcher started after a WSL one exited
without a window. Launchers up to 0.14.0 do that. Since 0.14.1 (#1186)
the Windows launcher can't verify the WSL launcher's token, treats it as
unrelated and starts without the single-instance port, so each further
Windows start opens another launcher. Describe both.
* 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
craft-update, craft-ui, craft-flags and craft-quit now come from
storytold/craft-libs at 453b0da782. Cargo.lock changes only the source
of the craft-libs packages.
craft-ui at this rev includes storytold/craft-libs#1207: a combo box
that cuts its selected text short shows the full text in a tooltip on
hover.
craft-update, craft-ui, craft-flags and craft-quit now come from
storytold/craft-libs at 3af2280ee3. Cargo.lock changes only the source
of the craft-libs packages.
craft-update at this rev includes storytold/craft-libs#1503: a binary
listed in an extracted nextest archive counts as a development build
and does not update itself.
* i18n: add a professional Ukrainian (uk) UI translation
Add crates/ui-egui/src/i18n/uk.tsv, a complete catalog (240 plain strings,
5 plural rows, 13 app taglines, 12 month names and the backend @msg/@id rows),
translated clean-room from the English source. Register it in LANGUAGES as
code "uk" with the East Slavic plural rule, cover it with i18n unit tests,
a Ukrainian UI integration test and the README language list.
* i18n(uk): call the portable package «Портативна версія»
* i18n(uk): document the functions this change touches
Add doc comments to every function the diff touches in the Ukrainian UI test,
the i18n catalog tests and the language registry, so the docstring-coverage
check sees a documented diff.
* i18n(uk): add missing strings and clean up "ще раз" to "знову"
Sync the catalog with upstream/main (add the new update-dialog prompt and
the reworded AppImage note for custom install folders), replace the
Russianism "ще раз" with the idiomatic Ukrainian "знову", and rephrase
the AppImage sentence to avoid calques.
* Revert "i18n(uk): add missing strings and clean up "ще раз" to "знову""
This reverts commit ebd0ce55f3.
* Revert "Fix saved filters hiding all apps on startup (#678) (#684)"
* i18n(uk): translate the strings upstream added
Cover the pin and reorder menu items, the Retry update button, and
MaterialCraft's tagline and details.
* i18n(uk): translate the strings upstream added
Cover the split Open button and its installability notes, launch options
and the flag quoting errors, and the Save button.
* i18n(uk): translate the strings upstream added
Cover the AniCraft and MailCraft taglines and the AniCraft details the
catalogs carry, the batch-update permission setting, and the download-size
label on a card.
* i18n(uk): build Installed with the fields main added
`Installed` gained `externally_managed`, `origin` and `installation`, so the
Ukrainian UI test failed to compile with E0063. Mirror russian.rs.
* i18n(uk): drop the unrelated process-pipe fix
The pipe-deadline wording and the inherited-pipe retry change belong in their
own PR, not in a translation branch.
Split out of #640 at review request: a translation PR is the wrong place for a process-handling change.
## What
When the direct child exits while a captured reader is still unfinished — a descendant holding a pipe, or output still being drained — `run_command_with_output` waits for the readers under the same deadline. On timeout the error said `<program> didn't finish within N seconds`, although the child had finished. It now says `<program> exited, but its output was still being captured at the N second deadline`, which names the shared deadline and does not claim the pipe is still open (`20026ee`).
In `inherited_pipe_tests`, an attempt whose direct child hit its own deadline before the holder filled both pipes proves nothing about inherited pipes, so the test retries it with a longer deadline, as it already did for an attempt that never reached the marker. The retry ceiling is a named `MAX_DEADLINE`.
## Testing
Run locally on Linux x86_64: `cargo test -p artcraft-launcher-native inherited_pipe_tests` passes (1 passed, 2 ignored fixtures), `cargo clippy -p artcraft-launcher-native --all-targets --locked -- -D warnings` is clean, and `cargo fmt --all -- --check` is clean. The wasm check was not run because this crate is not part of the web build. Hosted CI is left to run.
Fixes#1358
## What went wrong
On Linux and the BSDs the window system never reports the button release that ends a window
move or resize (rust-windowing/winit#2999, emilk/egui#7959): egui keeps the button pressed and
its drag bookkeeping (`InteractionState.dragged`, unreachable from the app) never ends, so the
next press is no press — every second drag attempt does nothing, and hover on the title bar
dies while the stuck "press" lasts. The same applies to edge resizes. The pinned egui fork
carries the same behaviour as v0.17.0, so current releases are affected.
## The fix (`crates/ui-egui/src/widgets.rs`)
- **Title bar drag** — a button held from an earlier frame that now moves over the bar is taken
as the next attempt's start. It is sent at most once per press, and never on the press frame
itself: a press that arrives already moving is a click (the window buttons sit in this bar),
not a move.
- **Move and resize** — right after `StartDrag`/`BeginResize`, egui's pointer is let go
(`PointerState::default()`), as though the undelivered release had arrived. That makes the
next press a fresh one, which is the whole fix for the resize path (its trigger is a press
transition) and re-arms the title bar's once-per-press marker.
Windows, macOS and the web deliver the real release; there the pointer is left alone.
## Tests
- `every_title_bar_drag_attempt_starts_a_window_move` and `every_edge_resize_attempt_starts_a_resize`
drive two press-then-move attempts with **no release in between** — the compositor's exact
behaviour — and require each attempt to send its command. Both fail on the previous code.
- The existing edge-press integration tests (`a_press_on_the_window_edge_only_resizes` among
them) keep passing, pinning that a moving press is still a click.
- `cargo xtask ci` — all four steps green.
Honest limit: the compositor-level swallow itself is winit/upstream territory; this is the
launcher-side workaround until egui#7959 is fixed there.
## 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>
Moves both pins from 94a3fb5 (the PR head at the time) to 0d76ea0, the
merge. That brings in the last two review fixes: an app briefly in use is
stopped when agents go off, and an apps.json that can't be read counts as
agents off.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The launcher treated any `mcpServers.ArtCraft` key as its own: Add replaced
it, and Remove or turning agents off deleted it from every client. Now an
entry is ours only when it starts craft-ai-mcp with exactly `--stdio` and no
environment. Any other ArtCraft entry is never replaced (Add reports it) or
removed, and Settings no longer shows it as added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Takes #1385's release-file check (`launcher_update_job` with
`self_update::installs_from`) as the one check for Update and Restart,
and drops this branch's copy of it (`release_installs`, the flag stored
next to `launcher_release`, `to_update_kind`). `launcher_update_job`
also requires `is_self_updating` and returns the release's repo for
`self_update::update`.
The backend test checks the signed-copy and release-file cases through
`capabilities` and `update_launcher`.
The gateway now holds only an app's connection during a call (listing,
searching and describing answer at once) and asks the switch again once a
queued call has its app, so it never starts after agents are turned off.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moves craft-update from 6e03f65bf to 47b6bbadf, the merge of
storytold/craft-libs#923. craft-update's Updater now reads whether the
copy can install itself on the update check's thread instead of in
tick, so a frame reads no installed file. The launcher's own
self-update already reads it on its check thread (launcher_update in
backend.rs), and the craft-update calls it makes are unchanged.
- The launcher writes, reads and removes ArtCraft/mcp/apps.json through
`craft-ai-agents` (storytold/craft-ai-integrations#197), the same crate the
gateway reads it with and every Craft app checks the switch with, instead
of its own copy of the format.
- Every app is started as plain `<app>-cli mcp`: by the suite's rule that
command works in the open window when the app runs and accepts agents, and
headless otherwise. The per-app argument table (`--live` for PhotoCraft,
`--headless` for VectorCraft) and reading each CLI's `--help` to see
whether it takes them are gone.
- Gateway and craft-ai-agents pinned to the head of #197 (35e0352).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- install_gateway returned an identical copy before setting its mode, so a
copy that had lost its execute bit was reused and clients couldn't start
it. The mode is now checked on both paths (Unix). Test extended: a 0644
copy with the right bytes comes back executable (fails without the fix;
run in Linux).
- packaging/linux/test-package-metadata.sh builds packages from a fake
release folder; it now has a craft-ai-mcp fixture too, since the packages
install the gateway beside the launcher.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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>
The gateway now asks the launcher's app list before every call: with the
switch off it refuses every tool and stops the app servers it started, and
it no longer falls back to CLIs on PATH.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Current Windows versions of Claude Desktop keep their data in
%LOCALAPPDATA%\Claude-Data\<install> and leave a .user-data-left.* marker in
the Store package folder they moved out of. The launcher wrote its entry into
that abandoned config, so Claude never saw it. Claude-Data now comes first,
then %APPDATA%\Claude, then a package folder without the marker.
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 app list gave every app plain `mcp`, so the gateway reached PhotoCraft
only headless. PhotoCraft now gets `mcp --live` (the open window, through
the connection it publishes, storytold/photocraft#13396) and VectorCraft
`mcp --headless` (its plain `mcp` attaches to a control port with no token
yet). Each is used only when that install's `mcp --help` names the
argument, so an older release still gets plain `mcp` instead of a usage
error.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>