RFE: special rule for the Zed code editor?

[plaimbock]

I've been trying to add a special rule for Zed https://github.com/zed-industries/zed but can't make it work properly. It does not automatically sign into github via the browser (Firefox) when started and does not activate Claude. When starting Zed in a normal env this all works. Any suggestions how to make this work would be most appreciated. Thanks!

 zed:
    - A special rule for running the Zed code editor
    - dbus: { allow: own, path: dev.zed.zed.* }
    - dbus: { allow: talk, path: org.freedesktop.portal.Secrets }
    - dbus: { allow: talk, path: org.mozilla.firefox.* }
    - bind: { path: $HOME/.config/zed, try: true, read-write: true }
    - bind: { path: $HOME/.local/share/zed, try: true, read-write: true }
    - bind: { path: $HOME/.fonts, try: true }
    - bind: { path: $HOME/.config/github-copilot, try: true, read-write: true }
    - bind: { path: $HOME/.cache/claude-cli-nodejs, try: true, read-write: true }
    - bind: { path: $HOME/.claude/.credentials.json, try: true, read-write: true }
    - bind: { path: $HOME/.claude.json, try: true, read-write: true }
    - env: { PS1: '\h \w \$ ' }
    - bind: { path: $HOME/Dev, read-write: true }
    - chdir: $HOME/Dev

[jcoffland]

I've not used Zed. It looks interesting. I'm using vscode and Claude. I setup a sbx template for development and I create new sandboxes from that. I've intentionally not given it access to my github or ssh keys. I manually activate Claude in each instance. I check in/out code manually outside the sandbox. This is to ensure nothing in the sandbox can control my repos. I'm careful to run npm and vscode plugins only inside the sandboxes. I've considered actually blocking programs like npm and pip from running when outside the sandbox.

[plaimbock]

I was thinking pretty the same except the manual activation. A special rule for vscode would be welcome. I hardly ever use it but you can never be safe enough.