Turtle
7520fe94e1
* refactor(preset): trim the creation-mode system prompt The `cordis` preset persona repeated what the plugin_manager and cordis_inspect_* tool descriptions and the two shipped skills already carry. Keep only identity, the shipped-preset constraint, the visual request routing rule, and which skill to load for what. Drop the tool-cordis prompt section, which restated its own tool descriptions, and the cordis_inspect_query navigation hints that the provider manifests returned by cordis_inspect_list already state. Shorten both skill descriptions so the first-turn catalog stays small. First-turn request for the cordis preset, measured through the DeepSeek API with deepseek-v4-flash: 9572 -> 8975 prompt tokens. * docs: regenerate config catalog after section order removal * docs: regenerate module graph after tool-cordis dependency removal * refactor(preset): give the cordis preset the standard persona Creation mode's system prompt now equals standard mode's; the skill catalog and the shipped skills carry every routing and off-limits rule. The plugin skill description states the visual-request destination. First-turn request for the cordis preset: 9572 -> 8815 prompt tokens. * fix(review): document current tool-cordis state and pin the shared persona The tool-cordis README pair now states that only the two tool schemas enter requests, that disposal removes tools and providers, and that the first-turn skill catalog carries the routing. The Web skill row test resolves the owner's selected fixture generation instead of a fixed v3 path. The preset e2e asserts the cordis persona sections equal standard's.
description, kind
| description | kind |
|---|---|
| The core group map: the session log, system-prompt assembly, tool registry, agent vocabulary, and default loop that form the product API spine. | package-group |
packages/core
English | 中文
Summary
Use the core packages to build or extend an agent that records durable session history, assembles system prompts, exposes tools, selects a default model, and runs model turns. These packages define the shared APIs used by every composition, while executable product assemblies live under packages/bundle. Choose this group when developing agent behavior or replacing one of those capabilities; start with dsh-base when you need the default runnable composition.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
scope/ |
Scoped registration and event routing that isolate one agent's contributions | library — no ctx key |
session/ |
The append-only session event log every agent's history derives from | ctx.sessions |
system-prompt/ |
System-prompt assembly from ordered sections, tool schemas, and variables | ctx.systemPrompt |
tools/ |
The tool registry and guarded execution pipeline the loop dispatches through | ctx.tools |
agent-tool-presentation/ |
Per-agent tool-presentation selector for presets | no ctx key |
agent/ |
The Agent handle plugins program against, plus its live registry and events |
ctx.agents |
agent-default-model/ |
The deployment default model selection entry points apply to fresh agents | ctx.agentDefaultModel |
agent-loop/ |
The default agent driver: creates agents and runs the turn and step lifecycle | ctx.agentLoop |
scope supplies the shared scoping primitive; agent owns the public Agent contract, while agent-loop is its default implementation, so extension plugins depend on agent and the driver stays swappable. agent-default-model owns the deployment selection an entry point applies when a session has none of its own. Runnable compositions live under packages/bundle; this group owns only the swappable spine pieces.
Related documentation
- Core subsystem — the package-by-package loop map and the
Agenthandle contracts. - Session subsystem — the session event vocabulary and derived history.
- System-prompt subsystem — prompt section, dynamic context, and tool-schema types.
- Tools subsystem — the tool execution pipeline and presentation vocabulary.
- Scoped registration subsystem — the scoped-layer primitive these registries build on.
- Architecture — the turn flow and where new behavior goes.
- Base bundle — the default product composition.
- SDK minimal bundle — a complete standalone composition with a deliberately smaller feature set.
Dev Note
Working context for maintainers — click to expand
None.