Repository navigation
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…").