novox/mesh-catalog
8
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/main' into feat/the-agent-account-is-declared
mesh/merge-gate pass: builds claude-code, claude-licence-manager, restic, sudo → ace, g14, novox, shanks; no bus step; every machine composes with the chan…
Details
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
Details
mesh/delivery superseded: a newer head of the same pull request
Details

Browse Source
This commit is contained in:
jochen
2026-10-09 23:37:04 +02:00
parent eacda6e3ae ac7400d20c
commit b382045721
145 changed files with 14890 additions and 1433 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/claude-code/README.md
+5 -5
View File
@@ -107,8 +107,8 @@ another node. So these tools refuse, and say why and how it is done instead:
- `claude_code_hook_register`, `claude_code_settings_set`, `claude_code_permission_add`, `claude_code_permission_remove`:
the operator sets hooks, permission rules and every other managed setting in this module's `managed_settings`
setting, `mesh-controller settings set claude-code '{"managed_settings": {…}}' [--node <node>]`, typed at the
controller's terminal. The controller refuses `managed_settings`, `mcp_servers` and `role` through any verb: a
setting, `mesh-cli settings set claude-code '{"managed_settings": {…}}' [--node <node>]`, typed at the
controller's terminal (`mesh-cli`, or `nox`, on the control-node; hq ADR 0272). The controller refuses `managed_settings`, `mcp_servers` and `role` through any verb: a
mergeable file asks for every key its own content names;
- `claude_code_mcp_register`: the operator sets tool servers in the `mcp_servers` setting the same way;
- a skill, subagent or command that would run something by itself: a shell line the agent runs when it loads one
@@ -130,7 +130,7 @@ decision of 2026-10-09; a surface of the operator's own may update it later). In
skills, commands and subagents at the `mesh` or `node` scope are refused through the tools, and the import tool is
refused. They are keys of this module's settings, each text a list of its lines, because a setting holds no line
break: `instructions`, `output_styles`, `commands` and `agents` map a name to its text; `skills` maps a name to its
files, each a list of lines. For example `mesh-controller settings set claude-code '{"instructions": {"conventions":
files, each a list of lines. For example `mesh-cli settings set claude-code '{"instructions": {"conventions":
["Commit in the imperative.", "", "Test before pushing."]}}'`. They land where a registration did, laid over what was
registered before; what the operator writes there is not judged, but an item that is not well formed is left out and
said in the render's answer. What was registered before is still rendered and may be unregistered.
@@ -169,8 +169,8 @@ A new session takes a change; a running one at `/reload-plugins`.
## Settings
Per node or for the whole mesh, at the controller's terminal alone: `mesh-controller settings set claude-code '<json>'
[--node <node>]`. The controller refuses all three keys through any verb, `mesh-controller.settings` included, because
Per node or for the whole mesh, at the controller's terminal alone: `mesh-cli settings set claude-code '<json>'
[--node <node>]` on the control-node (in zsh, `nox`; hq ADR 0272). The controller refuses all three keys through any verb, `mesh-controller.settings` included, because
each reaches every session on the node and a verb's caller may be an agent (hq issue 340). Reading them through the
verb still answers.