Linkly AI is made up of several components that work together: the desktop client, the CLI, and Skills. To balance stability with delivering new features quickly, each component uses a different update mechanism. This page describes the release cadence you should expect and what you need to do in different scenarios.Documentation Index
Fetch the complete documentation index at: https://linkly.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
1. How each component updates
| Component | Update method | Requires user action |
|---|---|---|
| Desktop client | Auto-update | No (takes effect after restart) |
| Linkly AI CLI | Manual | Yes (run a command) |
| Linkly AI Skills | Manual | Yes (re-run the install command) |
When the desktop client publishes a new version, the CLI and Skills usually
need to be upgraded together to fully use the new features. Each changelog
starts with a 💡 Tips block reminding you whether a sync upgrade is needed.
2. Desktop client release channels
The desktop client provides two update channels. Pick the one that fits your preference.| Channel | Release cadence | Stability | Recommended for |
|---|---|---|---|
| Stable | Once a week | High, fully validated through Beta | Most users |
| Beta (Dev build) | One to several times a week | Includes experimental features, may be unstable | Early adopters who are comfortable troubleshooting and reporting issues |
Stable
- The default channel; new installs use it out of the box
- Released roughly once a week, rolling up features that have been validated in Beta
- A steady cadence well suited for everyday use where stability matters
Beta (Dev build)
- Released one or more times a week, containing the latest experimental features
- Because features are still being polished, expect some rough edges (occasional crashes, UI tweaks, minor data-format changes, etc.)
- Recommended only if you accept these tradeoffs and are willing to report problems
3. How auto-update works
The desktop client checks for and downloads updates in the background. You don’t have to do anything.- When it checks: about 3 seconds after launch, then every 4 hours
- Download behavior: when a new version is found, it downloads in the background
- When it takes effect: after download, the new version installs and activates the next time you restart the app
- Manual check: you can also go to Settings → About and click “Check for Updates” to trigger a check immediately
4. Joining the Beta channel
Open Settings
Click the tray icon or the menu in the top-right of the client, then go to
Settings → About.
Leaving the Beta channel
Just turn off “Join Beta Program” under Settings → About. From then on you’ll only receive Stable updates.Turning off the toggle does not roll back the Beta build you currently have
installed. The next Stable release will overwrite it as a regular update.
5. Manually updating the CLI and Skills
Linkly AI CLI
The CLI silently checks for new versions on each launch and prints a notice in your terminal when one is available. To upgrade:Linkly AI Skills
Skills doesn’t ship with a built-in upgrade command. Choose the method that matches how you installed it:- Installed via
skills add: re-run the install command to overwrite - Installed via
git clone(Claude Code, Codex CLI, etc.): inside the skill directory run - Uploaded on Claude.ai: re-download
linkly-ai.zipfrom GitHub Releases and upload it under Settings → Capabilities → Skills to overwrite - Installed via ClawHub: run
6. Versioning
All Linkly AI components follow Semantic Versioning:- Stable versions look like
v0.4.1 - Beta versions look like
v0.4.2-beta.1,v0.4.2-beta.2, … - The desktop client, CLI, and Skills each maintain their own version numbers; new CLI / Skills versions are typically released alongside a new desktop release