Yichen Jiang
1d917e7c31
Sections differ by hundreds of pixels — a short preferences list against the composition editor — and the 600px panel served both badly: the list left a wide empty band, the editor cramped a YAML file into a 16-row box with dead space under it. The panel is now `min(800px, 100vh - 48px)`: one height for every section, whatever does not fit scrolls where it already did. The composition editor takes the column's full height rather than a fixed row count, so the extra space reaches the text instead of the gap. Refresh the settings goldens the preset section's nav entry had made stale.
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 deployment ships standard (the full coding agent), minimal (a two-tool benchmark surface), and cordis (the standard agent plus the self-referential toolset and a composition-authoring skill, so a person can ask an agent to author another agent).
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.