Yichen Jiang
45f1d439f6
The shipped host composition moved: `base.cordis.yml` and `web.cordis.yml` are the dsh-base and dsh-web-app patch layers now. The gate still opened the old paths and crashed on ENOENT — a gate that cannot read its inputs proves nothing, loudly or otherwise. Retargeting it also surfaced what the move implies for ownership: the web bundle carries the roster and its browser plugin rows now, so the bundle's own manifest is what must declare them. The gate's existing bare-plugin check said so as soon as it could parse the file again.
preset/ — per-session agent composition
English | 中文
An agent preset is a directory holding one agent.cordis.yml. Mounting it under an agent's scope context gives that session its own tools and prompt sections while every other live session keeps its own, so one process can run several differently composed agents at once.
| Package | Role | ctx key |
|---|---|---|
agent-presets/ |
Preset vocabulary, filesystem discovery over trusted and user-authored roots, and the guarded per-agent mount | ctx.agentPresets |
persona/ |
The agent persona as a composable row, so a preset can change identity and not only tools | — |
The presets the deployment ships live in apps/cli/config/agent-presets/ — one directory each, and that directory listing is the roster. Naming them here too would be a second list to keep in step, and the first one to fall behind.
The composition split this group assumes: registries and cross-session facilities are process singletons and stay in the host composition, while a preset carries what one agent contributes to them. A preset that names a row publishing a process-global service is rejected at mount rather than allowed to collide with the next session.
Design: the per-session agent-preset note.