feat(packaging): Linux AppImage installer - #39
Merged
Conversation
Completes the cross-platform installer matrix (macOS .pkg, Windows .msi,
Linux .AppImage — all three from one tag push).
Linux ships *without* a desktop a11y bridge for now: AT-SPI Linux
bridge isn't in this codebase yet. Every other plugin (memory,
recipes, network, foundations, vision, system, microsoft, web, pdf)
runs fine — the .AppImage is genuinely useful for Linux developers
using Claude Code / Cursor / Codex right now.
When the AT-SPI bridge ships, it slots into the same AppDir layout
(`usr/lib/agentmark/bridges/agentmark-bridge-linux`); the launcher
already detects + wires it.
Files:
packaging/scripts/build-linux.sh pnpm build → Node → AppDir → appimagetool
packaging/templates/AppRun AppImage entrypoint (delegates to launcher)
packaging/templates/agentmark.desktop XDG desktop entry (AppImage spec requirement)
.github/workflows/release.yml + build-linux job; appended to publish
Also: launcher.sh updated to detect BOTH the macOS pkg layout
(<root>/{bin,node,agentmark,bridges}) AND the Linux AppImage layout
(<root>/usr/{bin/node, bin/agentmark-mcp, lib/agentmark, lib/agentmark/bridges})
by probing for the entry file. One launcher, both layouts.
Plus: launcher now only sets AGENTMARK_BRIDGE_PATH when a bridge
binary actually exists. Previously hardcoded the macOS bridge name —
on Linux that env var would point at a missing file.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What ships
Each `.AppImage` is one self-contained file. User makes it executable, double-clicks (or runs from a terminal), they're on a working `agentmark-mcp`.
```
AgentMark.AppDir/
├── AppRun entrypoint (delegates to launcher)
├── agentmark.desktop XDG desktop entry (AppImage spec)
├── agentmark.png placeholder icon (AppImage spec)
└── usr/
├── bin/
│ ├── node pinned Node 22.11.0 LTS
│ └── agentmark-mcp launcher script
├── lib/agentmark/ dist/ + schema/ + package.json + prod deps
└── share/
├── applications/agentmark.desktop
└── icons/hicolor/256x256/apps/agentmark.png
```
What's NOT in the Linux build
Launcher dual-layout support
The shared `launcher.sh` now handles both:
Also: launcher now only sets `AGENTMARK_BRIDGE_PATH` when the bridge binary actually exists. Previously hardcoded the macOS bridge name — on Linux that env var would point at a missing file.
Test plan
Pinned versions (unchanged)
🤖 Generated with Claude Code