claude-code: read and remove the person's own home items through the mesh
Hand-written items in an account's ~/.claude could only be removed over a shell on the machine. claude_code_home_show reads one in full (memory, ~/.claude/CLAUDE.md, included); claude_code_home_remove removes one on the person's word, with a required reason, refusing what the mesh placed and symbolic links, keeping a dated copy in the module's state and logging it.
This commit is contained in:
@@ -70,7 +70,15 @@ operator account's own `~/.claude` on those nodes):
|
||||
- `claude_code_config_list`, `_show` (one registration in full), `_status` (what applies here, the plugin
|
||||
as written, and the home's own items — which the mesh placed, which share a name with a mesh item, which
|
||||
call a tool server not loaded here) and `_import` (an item of this node's home, registered at a scope;
|
||||
the original stays).
|
||||
the original stays);
|
||||
- `claude_code_home_show` (`kind`, `name`): one item of this node's home in full — a skill, subagent,
|
||||
command, output style, rule file (`instructions`), or the account's own memory `~/.claude/CLAUDE.md`
|
||||
(`memory`) — and whether the mesh placed it;
|
||||
- `claude_code_home_remove` (`kind`, `name`, `why`): removes one item the person made, on their word —
|
||||
removing it is the person's act, and this tool is that act made explicit. `why` is required; what the
|
||||
mesh placed is refused (its `_unregister` owns it), and so is a symbolic link. A copy is kept first in
|
||||
the module's state, `removed-from-home/<date>/<time>-<kind>-<name>/`, with a `removal.json` note, and
|
||||
the removal and its reason are appended to `removed-from-home/removed.log`; the answer names the copy.
|
||||
|
||||
A new session takes a change; a running one at `/reload-plugins`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user