openclaw/nix-openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/nix-openclaw.git synced 2026-07-25 05:35:30 -04:00
Code Issues 31 Packages Projects Releases Wiki Activity

[PR #12] Allow local file management #40

New Issue
Open
opened 2026-02-15 17:04:41 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:04:41 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/nix-openclaw/pull/12
Author: @uos-status
Created: 1/25/2026
Status: 🔄 Open

Base: main ← Head: fix/manage-files-option

📝 Commits (5)

  • 34261f1 fix: Linux compatibility updates
  • f1ad09e fix: include extensions directory in gateway install
  • da842bb fix: include docs directory in gateway install for templates
  • c8f79d6 fix: add auth.profiles config for anthropic provider
  • f356de3 feat: add manageConfig and manageDocuments options

📊 Changes

2 files changed (+62 additions, -29 deletions)

View changed files

📝 nix/modules/home-manager/clawdbot.nix (+61 -28)
📝 nix/scripts/gateway-install.sh (+1 -1)

📄 Description

Problem

By default, the nix-clawdbot Home Manager module manages all configuration and document files by symlinking them from the Nix store. This prevents the application from modifying its own configuration (e.g., during onboard or via UI) and makes it difficult for users to manually edit files in the workspace without changing their Nix configuration.

Users may want to manage configuration via Nix but let the bot manage its own documents, or vice versa.

Solution

Added two new options to the Home Manager module:

  1. programs.clawdbot.manageConfig (default: true)
    • When false, the clawdbot.json configuration file is not managed or symlinked by Nix.
  2. programs.clawdbot.manageDocuments (default: true)
    • When false, document files, skill files, and plugin files in the workspace are not managed or symlinked by Nix.
    • Activation guards for documents and plugins are disabled.

This provides granular control over which parts of the Clawdbot workspace are managed declaratively via Nix and which are left to the application or manual management.

Files Modified

  • nix/modules/home-manager/clawdbot.nix

Additional Info. This is based off this PR:

https://github.com/clawdbot/nix-clawdbot/pull/9

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/openclaw/nix-openclaw/pull/12 **Author:** [@uos-status](https://github.com/uos-status) **Created:** 1/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/manage-files-option` --- ### 📝 Commits (5) - [`34261f1`](https://github.com/openclaw/nix-openclaw/commit/34261f18f11f118ee6e002d1067bcc86a51bffaf) fix: Linux compatibility updates - [`f1ad09e`](https://github.com/openclaw/nix-openclaw/commit/f1ad09ec30fff4d3b15fa5bc2573d3864f9f9a53) fix: include extensions directory in gateway install - [`da842bb`](https://github.com/openclaw/nix-openclaw/commit/da842bbec01030958d9995c9058e19e0e6c9131b) fix: include docs directory in gateway install for templates - [`c8f79d6`](https://github.com/openclaw/nix-openclaw/commit/c8f79d6c756dcc0923b03b9385609cad09e0b793) fix: add auth.profiles config for anthropic provider - [`f356de3`](https://github.com/openclaw/nix-openclaw/commit/f356de3bf05a5d28fc08f35ce62b706fa9450091) feat: add manageConfig and manageDocuments options ### 📊 Changes **2 files changed** (+62 additions, -29 deletions) <details> <summary>View changed files</summary> 📝 `nix/modules/home-manager/clawdbot.nix` (+61 -28) 📝 `nix/scripts/gateway-install.sh` (+1 -1) </details> ### 📄 Description ## Problem By default, the `nix-clawdbot` Home Manager module manages all configuration and document files by symlinking them from the Nix store. This prevents the application from modifying its own configuration (e.g., during `onboard` or via UI) and makes it difficult for users to manually edit files in the workspace without changing their Nix configuration. Users may want to manage configuration via Nix but let the bot manage its own documents, or vice versa. ## Solution Added two new options to the Home Manager module: 1. **`programs.clawdbot.manageConfig`** (default: `true`) - When `false`, the `clawdbot.json` configuration file is not managed or symlinked by Nix. 2. **`programs.clawdbot.manageDocuments`** (default: `true`) - When `false`, document files, skill files, and plugin files in the workspace are not managed or symlinked by Nix. - Activation guards for documents and plugins are disabled. This provides granular control over which parts of the Clawdbot workspace are managed declaratively via Nix and which are left to the application or manual management. ## Files Modified - `nix/modules/home-manager/clawdbot.nix` ## Additional Info. This is based off this PR: https://github.com/clawdbot/nix-clawdbot/pull/9 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:04:41 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
maintainer-roadmap
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/nix-openclaw#40
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?