Skip to content

Let safe prime-agent read vault-linked skills on the work role - #86

Merged
technicalpickles merged 1 commit into
mainfrom
prime-agent-vault-skills-grant
Oct 22, 2026
Merged

technicalpickles merged 1 commit into
mainfrom
prime-agent-vault-skills-grant

Conversation

@technicalpickles

Copy link
Copy Markdown
Owner

Summary

  • safe prime-agent couldn't read a skill symlinked into ~/.prime/agent/skills when the link ends up in the vault. Seatbelt checks the resolved path, so the symlink alone isn't enough and the read dies with EPERM. This adds a read-only grant for the one skill that needs it (writing-voice) instead of the whole vault.
  • It lives in role-work.sb because the vault path is per machine. A machine that reads the same skill under the home role needs its own grant in role-home.sb, with its own path.

Test plan

  • Under safe, with a symlink to ~/.claude/skills/writing-voice in ~/.prime/agent/skills/, prime-agent got Operation not permitted reading its SKILL.md. With this branch's profiles (ran a copy of bin/safe pointed at them) the read goes through.

🤖 Generated with Claude Code

~/.claude/skills/writing-voice is a symlink into the vault. Seatbelt checks the
resolved path, so prime-agent got EPERM reading it through a symlink in
~/.prime/agent/skills. Grant read-only on that one skill's subpath so skills
can be symlinked instead of rsync-copied on every launch.

Verified under safe: the read fails without the grant and succeeds with it.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@technicalpickles
technicalpickles merged commit fe30ef8 into main Oct 22, 2026
1 check passed
@technicalpickles
technicalpickles deleted the prime-agent-vault-skills-grant branch October 22, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant