35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
---
|
|
status: open
|
|
parent: "[[027-pi-subagents-implementation-spec-task]]"
|
|
blocked-by:
|
|
- "[[046-pi-subagents-minimal-tracer-bullet-task]]"
|
|
tags:
|
|
- ticket/task/afk
|
|
---
|
|
|
|
# Support config files, named agents, and tool profiles
|
|
|
|
## Question
|
|
|
|
Implement config loading, Markdown named agents, defaults, diagnostics, and tool profile resolution so named subagent spawns work end to end.
|
|
|
|
## What to build
|
|
|
|
Add the configuration boundary around the minimal spawn path.
|
|
The extension should accept absent global and project config as normal, load trusted project configuration after global configuration, load Markdown named agents from user and trusted project locations, and resolve spawn settings from overrides, frontmatter, config, and in-code defaults.
|
|
Tool profiles should include the reserved built-ins and user-defined custom profiles, while preserving diagnostics for invalid input.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] Missing config files and missing agent directories are accepted as normal.
|
|
- [ ] Global config and trusted project config merge in the specified order.
|
|
- [ ] Markdown agent definitions load from user and trusted project paths with correct precedence.
|
|
- [ ] Duplicate definitions in one tier and invalid frontmatter produce diagnostics without crashing startup.
|
|
- [ ] A named spawn resolves prompt, context, model, thinking, and tools from spawn overrides, frontmatter, config, and in-code defaults.
|
|
- [ ] Built-in tool profile names cannot be overridden.
|
|
|
|
## Implementation Notes
|
|
|
|
Do not write starter config files.
|
|
Do not define named agents inline in `subagents.json`.
|