Files

30 lines
3.5 KiB
Markdown
Raw Permalink Normal View History

# agents
The generic AIMsight agents, one copy of each. An agent states only its trade here; everything specific to a caller (its output paths, its report format, its git rules) reaches it in the request, or through an instruction file the request names (`INSTRUCTIONS`). The rules of a target the upgrader and the validator change (what may change in it, what a regression is) are the target's own `CLAUDE.md`: written once, read by both and by whoever edits the target by hand.
| Agent | Its trade | Request parameters | Called by |
|---|---|---|---|
| `analyst` | read a range like the expert and label it, with an analysis that justifies each label | station, range, hints, output folder, `DETECTORS: yes \| no` (with `yes`, `Events: <command>`), `INSTRUCTIONS: <file>` | aimsight-app (`instructions/analyst.md`, `DETECTORS: no`) |
| `upgrader` | improve a target (a git repository) on the evidence given, without overfitting, one commit per fix | `Target`, `Evidence`, `Checks` (or `none`), `Base`, `Files already modified`, output folder, `INSTRUCTIONS: <file>` | Optimizer (`optimize` skill): the detectors (`instructions/upgrader-detectors.md`), then the tools (`instructions/upgrader-tools.md`) |
| `validator` | judge an upgrader's change on the checks and the code, without its diagnosis: keep, remove some fixes, cancel | `Target`, `Modification`, `Base`, `Checks` (before, after, after each fix), output, `INSTRUCTIONS: <file>` | Optimizer, the detectors (`instructions/validator-detectors.md`) |
| `support` | do what it is asked, as a generalist: answer a client or the expert, look into a station; it delegates a range's reading to the analyst (`claude -p` from a root of links in its folder) | `INSTRUCTIONS: <file>`, `Output folder` (both optional; else `~/aimsight-labeling/auto/support/<YYYY-MM-DD>_<subject>/`) | the user, from anywhere (`claude --plugin-dir ~/aimsight-agents --agent agents:support`) |
## Launching them
The repository is a Claude Code plugin (`.claude-plugin/plugin.json`), loaded read-only:
```bash
claude -p "<request>" --plugin-dir ~/aimsight-agents --agent agents:analyst
```
The support is launched by the user from anywhere, isolated like the other agents' runs and given the repositories it reads and writes; it builds its own root of links in its folder:
```bash
claude --plugin-dir ~/aimsight-agents --agent agents:support --setting-sources project,local --strict-mcp-config --add-dir ~/aimsight-labeling --add-dir ~/aimsight-data/data --add-dir ~/aimsight-tools --add-dir ~/aimsight-detectors --add-dir ~/aimsight-libredesk
```
In a workflow, through the Agent tool: `subagent_type: agents:upgrader`, with `--plugin-dir ~/aimsight-agents` when the session is launched.
The caller launches from its root, which carries the links `data/` (the stations, `~/aimsight-data/data`), `labeling/` (`~/aimsight-labeling`), `tools/` (`~/aimsight-tools`), and `detectors/` (`~/aimsight-detectors`) when the agent needs it; it gives `--add-dir` on their real targets so that the agent can read or write there. Claude does not write into a loaded plugin: what gets written (the tools, the detectors, the sessions) lives in the other repositories, never here.
Taken on 2026-11-16 from aimsight-app (`analyst`, `tool-builder`, commit dd6f1bf) and from detectors (`upgrader`, `validator`, commit 5438b0b); the same day, the upgrader and the validator were made generic on a target and the tool-builder folded into the upgrader (`docs/superpowers/specs/2026-11-16-generic-agents-design.md`). The architecture of the repositories: `~/aimsight-app/docs/architecture.drawio`.