Repository navigation
Releases
Releases · eltomato89/asm
v0.7.0
ASM v0.7.0
Image: ghcr.io/eltomato89/asm:0.7.0 (also 0.7, latest; linux/amd64)
New
- Linked devices. Attach the
asmCLI to its Claude Code device, duringasm login(opt-in on the browser page) or later on the devices page.- The attached CLI uses the main device's standing approval and default vault; its own settings are dropped when linking.
- Grants of a linked group can only be redeemed by that group's CLI (
wrong_device_groupotherwise), and they stay bound to the group they were issued for. Unlinked devices work as before. - Revoking the main device revokes attached CLIs by default (or detaches them). Unlinking cancels the CLI's open grants and requests.
- If the main device has an active standing approval, linking shows a warning that the CLI will be approved automatically.
- Agents can propose a standing approval. New MCP tool
request_standing_approval:- Named vaults or secrets only, reads only, at most
ASM_STANDING_REQUEST_MAX_DAYS(default 14) days. - Only while no standing approval is active; one open proposal per device, valid 30 minutes; 24 h cooldown after a denial, at most 3 proposals per device per day.
- You can only narrow it (fewer vaults/secrets, shorter, no renewal). Approving always needs a recent sign-in in the app or a passkey on the push page (
/approve/standing/…); it is never approved automatically. await_requestacceptssrq_…ids;whoami.standing_requesttells the agent whether it may propose. The audit log shows "proposed by the agent, adjusted by you".
- Named vaults or secrets only, reads only, at most
Security
- Approve links for proposals are redacted from request logs.
- Linking, unlinking and approving a proposal require a recent sign-in.
Upgrade notes
- New optional environment variable
ASM_STANDING_REQUEST_MAX_DAYS(defaultmin(14, ASM_STANDING_APPROVAL_MAX_DAYS),0disables proposals; a value aboveASM_STANDING_APPROVAL_MAX_DAYSfails at startup). - Database migrations run automatically on start (device links, grant group binding, standing approval proposals).
- Existing devices stay unlinked. To use linking, attach your CLI on the devices page ("Link…").
v0.6.0
ASM v0.6.0
Image: ghcr.io/eltomato89/asm:0.6.0 (also 0.6, latest; linux/amd64)
New
- Standing approval per device. Let a device use secrets without asking every time, within limits you set on the devices page:
- Until a date, at most
ASM_STANDING_APPROVAL_MAX_DAYS(default 90) days ahead. - Scope: all secrets, selected vaults (including secrets added later), or a list of secrets. Optionally, secrets the device creates in its default vault are added to the list.
- Reads only by default; a per-device switch also allows changes (
update_secret) without asking. - After expiry: ask every time again, or ask once and extend by a preset number of days when you approve. Denying only rejects that request.
- Standing approvals take precedence over auto mode. They show up in the request list ("via standing approval"), on the push approve page (renewal note) and in the audit log. MCP
whoamitells the agent whether it is covered (no secret list).
- Until a date, at most
- Default vault per device. Secrets a device creates without naming a vault go to its default vault: your personal vault unless you change it on the devices page.
Security
- Setting a standing approval or a device's default vault requires a recent sign-in, as does approving a renewal in the browser (the push page already requires Face ID / a passkey).
- Revoking a device, losing access to a vault, or deleting a secret removes the corresponding coverage.
ASM_STANDING_APPROVAL_MAX_DAYS=0turns the feature off and removes existing standing approvals.
Upgrade notes
- New optional environment variable:
ASM_STANDING_APPROVAL_MAX_DAYS(default90,0disables, max3650). - A database migration runs automatically on start (new tables for standing approvals, a default vault column on devices).
- New personal vaults are unaffected; existing devices default to their owner's personal vault.
v0.5.1
ASM v0.5.1
Image: ghcr.io/eltomato89/asm:0.5.1 (also 0.5, latest; linux/amd64)
Fixes
- Approve page: after approving or denying a request (or when it is no longer valid), the page now shows an Open ASM button that leads to the overview. Opened from a push notification in the installed web app on iPhone, there was no way back into the app before.
Upgrade notes
- No new environment variables and no database migrations.
v0.5.0
ASM v0.5.0
First public release. Website: https://eltomato89.github.io/asm/
Image: ghcr.io/eltomato89/asm:0.5.0 (also 0.5, latest; linux/amd64)
New
- English web UI with German as a second language. The UI follows the browser language; switch it per browser under Settings → Language.
- Open source under the Apache License 2.0 (
LICENSE,NOTICE). Third-party licenses ship asTHIRD_PARTY_NOTICESin the Docker image, next to the CLI bundle (also served at/cli/THIRD_PARTY_NOTICES) and in the web build. - Landing page with an animated demo, plus an English README (German version:
README.de.md).
Changes
- Push notifications are now in English ("New request waiting for approval").
- New installations name the personal vault "Personal". Existing vaults keep their stored name; the UI shows a localized label for personal vaults either way.
asmCLI installs now also downloadTHIRD_PARTY_NOTICES(the install continues if that download fails).
Upgrade notes
- No new environment variables and no database migrations.
- The UI language changes to English for browsers that aren't set to German. To keep German, choose Settings → Language → Deutsch.
v0.4.0
ASM v0.4.0
Image: ghcr.io/eltomato89/asm:0.4.0 (auch 0.4, latest; linux/amd64)
Neu
- Push-Freigabe vom iPhone: Web Push mit neutraler Benachrichtigung, Einmal-Link, Freigabe nur mit Face ID/Passkey; öffentlich muss nur
/approveerreichbar sein (Anleitung für Nginx Proxy Manager im README). Zweite Sicherung überASM_TRUSTED_NETWORKS. - CLI-Verteilung über den Server:
curl -fsSL https://<asm>/cli/install.sh | sh,asm update; Tokens im macOS-Schlüsselbund bzw. Linux-secret-tool. - CI & Releases über GitHub Actions (Tests, E2E, CLI auf Node 22.12, Image nach GHCR).
Sicherheit
ASM_TRUST_PROXYakzeptiert jetzt Hop-Anzahl oder Proxy-CIDRs (bitte1hinter einem Proxy setzen);truezusammen mitASM_TRUSTED_NETWORKSwird abgelehnt.- Push-Endpunkte nur bei bekannten Push-Diensten, Freigabe-Links werden aus Logs entfernt.
- Alle Abhängigkeiten auf aktuelle Versionen, Server auf Node 24;
pnpm audit --prodohne Befunde.
Upgrade-Hinweise
- Server läuft jetzt auf Node 24 (im Image enthalten), die CLI braucht Node ≥ 22.12.
- Neue Umgebungsvariablen:
ASM_TRUSTED_NETWORKS,ASM_VAPID_SUBJECT,ASM_CLI_DIR(optional).ASM_TRUST_PROXY=1empfohlen. - Datenbank-Migrationen laufen beim Start automatisch.