home.social

Search

36 results for “hmnews”

  1. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  2. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  3. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  4. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  5. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```

  6. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  7. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  8. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  9. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  10. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.

  11. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  12. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  13. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  14. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  15. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`

  16. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  17. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  18. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  19. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  20. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).

  21. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  22. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  23. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  24. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  25. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.

  26. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  27. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  28. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  29. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  30. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg