fix: run Remote Control in ~/work, which Claude can trust
os / os (push) Waiting to run

Claude never saves trust for a home directory, so claude-remote.service
now runs in ~/work, which tmpfiles makes and pre-trusts in .claude.json.
Its status screen on stdout no longer floods the journal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Job79andClaude Opus 5.5 committed 2026-11-22 16:47:45 +01:00
1 parent 1707500c05
commit 3a4a9f715a
4 files changed
+22 -7

No files matched your search

+2 -1
View File
@@ -25,7 +25,8 @@ resize it to the disk size you want and boot it with UEFI and a TPM. At first
boot, the screen offers a recovery key for the encrypted disk and asks for a
root password. Then log in as root and put your ssh key in
`/home/agent/.ssh/authorized_keys` (for root: `~/.ssh/authorized_keys`), which
starts sshd. Run `claude` once as `agent` to sign in. The VM then shows up in
starts sshd. As `agent`, run `claude` once in `~/work` to sign in and trust
that folder, where Remote Control runs. The VM then shows up in
claude.ai/code and the Claude app under its hostname: `agentos-` and four hex
digits.