David Flanagan

@Blizzke Comtrya can ONLY work with files within the manifests `./files` directory. We would like to change this, but that's not super high priority at the moment. Meaning, you can...

@akhilmhdh No, though that will definitely help minimise the toil. I could have a special "integrations" folder with subfolders for syncs; then pull them into sub-folders, but it will still...

🙁 This is disappointing. I'd have been happy to contribute this myself

I seen in the common patterns doc that you suggest doing the following for this use-case: ```nix enterShell = '' export PATH="$HOME/.mix/escripts:$PATH" ''; ```

Subdirectories are fine, but when I launch Claude in a subdirectory the MCP config and commands at the root of the repository are not loaded.

This can be fixed by going to the Zitadel project and adding your Zitadel URL to the allowed URLs list.

I'm on mobile, but find the Zitadel project and select the Console application; then update your origin with your Zitadel URL This should really be done by default for us....

This is actually the approach I've taken with a new reimagined dotfiles tool, that uses TypeScript interface instead of YAML https://github.com/korora-tech/dhd You run `dhd generate types` It's mostly built by...

There are two ways we can tackle this: # Sudo Exec Currently, we use Rust APIs for file management. These can't elevate privileges at runtime. We'd need to start using...

and of course, the simple option is to encourage `sudo comtrya apply`, but this then makes unprivileged actions/atoms run as root and provides different contexts. I'd rather not go down...