jochen
f291d113c8
Graduates research 029 and amends design 36 (section 8): skills, subagents, commands, hooks and output styles in one nox-mesh plugin; servers, settings and instructions in the managed files; mesh, node and home scopes.
4.2 KiB
status, initiated, touches, became
| status | initiated | touches | became | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| graduated | 2026-10-04 |
|
|
029 — The agent configured through its module
What
Everything about the operator's coding agent that can be configured is configured through the agent module's tools, and reaches the machines as one plugin the mesh serves:
- subagents, skills, slash commands, hooks, output styles and tool servers;
- the agent's settings and its instructions.
Each item is registered once, from any machine, and goes to one machine, several, or all of them, including a machine that joins later. The mechanism is the one the module already uses for tool servers: the registration is kept in the module's state on the bus, and each machine's instance writes what applies to it. The operator chose the plugin route on the day this effort opened.
Three scopes (the operator's direction, the same day):
- mesh: in the mesh's plugin and the managed files, on every machine;
- node: the same places, rendered for one machine or a list of them;
- home: placed in the operator account's own agent directory on a machine, beside what the person writes there by hand.
Instructions follow the same scopes: the mesh's piece, the node's piece, then further customisation per machine. See 03.
Why
The vendor gives the agent a machine-wide directory for its settings, its tool servers and one instruction file, and nothing machine-wide for skills, subagents, commands or hooks. Those exist only in a home or a project. So today they are copied into each home by hand, and they drift and go stale. 01 measures that on four machines.
A plugin is the vendor's own unit for carrying all of those at once. A machine-wide setting can name a marketplace and enable a plugin from it. If the module serves the plugin and its own managed settings enable it, the mesh gets a machine-wide place for everything the vendor left home-only, and the home stays the person's (ADR 0182).
What it touches
- The agent module's design (to-be 36): its managed directory, its state, and its tools.
- Module state (ADR 0201): where registrations are kept, and which file content fits in a bucket.
- Contributions (ADR 0210): a module other than the agent's, say the forge's, wanting the agent to have a skill for it. That is a contribution to the agent's seat, not a file it writes.
- The managed settings key the operator sets (ADR 0213), which a settings tool would write rather than a hand-composed settings layer.
Documents
- 01 — What is configured today: the evidence.
- 02 — What the vendor allows: plugins, marketplaces and managed settings, as documented, with sources.
- 03 — Options: where each kind of item goes, how it is registered and stored, and the questions a decision has to answer.
- 04 — What was confirmed: the checks, tried on one workstation.