Request new personal-files interface for Atuin

store-requests privileged-interfaces
1

Hello,

I’d like to request a couple new personal-files interfaces with read/write access for the atuin snap. They access the files:

  • $HOME/.claude/settings.json
  • $HOME/.codex/hooks.json
  • $HOME/.config/opencode/plugins/atuin.ts
  • $HOME/.pi/agent/extensions/atuin.ts

Atuin accesses those to configure it own integration to the respective AI harness frameworks.

I only require manual-connection and added some scripting to help the end user with those (see here).

For reference, the initial request for personal-files interfaces.

2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

Hello @artivis!

Two of the paths ($HOME/.config/opencode/plugins/atuin.ts and $HOME/.pi/agent/extensions/atuin.ts) are executable files loaded by AI agents. Giving write access here lets Atuin inject code into other AI tools, which poses a significant security risk. Could Atuin just print these file contents to stdout during the hook install command, allowing users to copy/paste them manually instead?

Regarding .claude/settings.json and .codex/hooks.json, can you confirm that Atuin merges changes rather than overwriting them? We want to make sure it won’t break any existing, non-snap installations that the user might be running.

4

Hi @yomonokio ,

Thanks for the reply.

First of all, mind that I’m not developing/maintaining Atuin, I’m only a user that packaged it as a snap. So my knowledge of its internals is rather limited and my influence null.

Regarding the .ts files, they are indeed scripts (harnesses plugins) which Atuin ships and automatically install at the appropriate paths. Printing them to stdout and asking the user to copy/paste kinda defeat the point of this automatic integration.

As for the .json , I’d expect that Atuin does merge changes but I’ll double check and confirm here.

5

Hey @artivis

Thanks for the reply! Since the Atuin snap own the .ts files, we 're good to go (I wasn’t sure because of the different paths)!

When you have more information about the .json ones, we can proceed with the voting process :slight_smile:

6

Hi @yomonokio :waving_hand: ,

I can confirm that Atuin merges its config with an existing json (if any). Find the evidence at atuin/crates/atuin/src/command/client/hook.rs at d337eaa50c1ee01571489fda6cf977ac580e5d7a · atuinsh/atuin · GitHub.

Cheers.

7

Hello @artivis :slight_smile:

GIven the justification provided this is a +1 from my side for granting auto-connection of thepersonal-files interface with read/write access to the files below:

  • $HOME/.claude/settings.json
  • $HOME/.codex/hooks.json
  • $HOME/.config/opencode/plugins/atuin.ts
  • $HOME/.pi/agent/extensions/atuin.ts
1 Like
8

Hello @artivis,

Thank you for the further investigation and context. Given the provided reasoning and the previous granted request, this is a +1 from me for granting manual connection as requested for the personal-files interface with read/write access to the following list of files:

  • $HOME/.claude/settings.json
  • $HOME/.codex/hooks.json
  • $HOME/.config/opencode/plugins/atuin.ts
  • $HOME/.pi/agent/extensions/atuin.ts
1 Like
9

+2 votes for, 0 against the request is approved! @artivis could you please update the snapcraft.yamlso we can proceed with granting the requested interfaces?

10

Done in the source repo and the CI tried to push to the store :+1:

11

Granting manual connection for the personal-files interface. This is now live :slight_smile:

1 Like