Skip to content

fix(runbooks): align roster references with rendered agent ids - #1059

Closed
atillayedek wants to merge 1 commit into
msitarzewski:mainfrom
atillayedek:fix/runbook-agent-ids-1027
Closed

atillayedek wants to merge 1 commit into
msitarzewski:mainfrom
atillayedek:fix/runbook-agent-ids-1027

Conversation

@atillayedek

@atillayedek atillayedek commented Oct 6, 2026 •

Copy link
Copy Markdown

What does this PR do?

Agent Information (if adding/modifying an agent)

  • Agent Name:
  • Category:
  • Specialty:

Checklist

  • Follows the agent template structure from CONTRIBUTING.md
  • Includes YAML frontmatter with name, description, color
  • Has concrete code/template examples (for new agents)
  • Tested in real scenarios
  • Proofread and formatted correctly

@msitarzewski

Copy link
Copy Markdown
Owner

Thank you, @atillayedek, and for adding a regression test. We're keeping file stems in runbooks.json, though: the Agency Agents desktop app identifies agents by filename stem, so name-derived ids would stop its runbook deploys from resolving. The full reasoning is on #1027: #1027 (comment). Closing for that reason, with thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants