main
John Lauer Publish 0.1.0 d8a45ab

name: hydrogen-staying-current description: >- How a Hydrogen workspace on Linux stays current: adom-wiki pkg update through the adom/hook prompt hook, the Linux skill set Hydrogen itself writes, the code-server reload banner, and how to ship a skill, CLI or app to every workspace. Use when asked how updates work, how to get the latest skills, or how to distribute a tool to all users.

How this workspace stays up to date (Linux)

TL;DR (anyone)

You don't do anything. Your workspace's Adom tooling is registry-native: everything is an adom-wiki package (CLIs, skills, apps), and the auto-update hook (adom/hook, installed by adom/core) runs adom-wiki pkg update in the background (throttled ~30 min, on your prompts, for both Claude Code and Codex) and re-resolves adom/core so newly added tools arrive automatically.

  • Force a check now: adom-wiki pkg update
  • See what's installed / behind: adom-wiki pkg list / adom-wiki pkg outdated

Where the Hydrogen skills come from

  • adom/hydrogen-bootstrap (wiki package) ships the platform-generic Hydrogen skills, deployed flat into ~/.claude/skills/.
  • Hydrogen itself ships the Linux layer. The Hydrogen build carries the Linux skill set and writes it into ~/.claude/skills/ at every launch and after every package convergence, over any package copy of the same name. So a package update cannot leave a Linux workspace with another platform's text for long: the next launch or convergence puts the Linux version back. New Linux skill text arrives with a Hydrogen update (see hydrogen-self-update), not a package update.
  • Org member apps arrive through your org's org-bootstrap meta-package.

The reload banner

code-server self-updates on disk but only takes effect after a restart. Hydrogen detects that natively and shows "code-server has an update — click to reload" at the top of the editor (only after setup is complete, never mid-cascade). Clicking restarts code-server + reloads the editor. Extensions never banner — VS Code's own auto-update activates them.

"How do I ship a tool/skill/app to every Adom workspace?" (Adom employees)

Publish it as an adom-wiki package, then add it as a dependency of the right bootstrap: every container: adom/core; every Hydrogen workspace: adom/hydrogen-bootstrap; org members only: your org's org-bootstrap. Hydrogen skills: a platform-generic one goes in adom/hydrogen-bootstrap; a Linux one is a Linux platform block in the Hydrogen repo's skills/public-facing/shared/<name>/SKILL.md and ships with the next Hydrogen build (see ~/.claude/skills/hydrogen-skill-loop/SKILL.md). The hook's re-resolve delivers package changes fleet-wide within about 30 minutes of users prompting.