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

+9 -2
View File
@@ -1,6 +1,13 @@
# agent.conf makes the home of the user agent.
# agent.conf makes the home of the user agent, and in it work, where
# claude-remote.service runs (mkosi.extra/usr/lib/systemd/user).
d /home/agent 0700 agent agent
d /home/agent/work 0700 agent agent
# .claude.json trusts ~/work, so claude-remote.service can run there without
# the trust dialog first. It is only made if missing, because Claude keeps its
# login there too.
f /home/agent/.claude.json 0600 agent agent - {"projects":{"/home/agent/work":{"hasTrustDialogAccepted":true}}}
# linger starts the user manager of agent at boot, for rootless podman and
# claude-remote.path (mkosi.extra/usr/lib/systemd/user).
# claude-remote.path.
f /var/lib/systemd/linger/agent