Skip to content

Sync v1 REST client with API spec: add first_run_yaml to ListAgentTemplatesResponse#20

Open
ellipsis-dev[bot] wants to merge 1 commit into
mainfrom
sync/v1-list-templates-first-run-yaml
Open

Sync v1 REST client with API spec: add first_run_yaml to ListAgentTemplatesResponse#20
ellipsis-dev[bot] wants to merge 1 commit into
mainfrom
sync/v1-list-templates-first-run-yaml

Conversation

@ellipsis-dev

@ellipsis-dev ellipsis-dev Bot commented Jul 2, 2026

Copy link
Copy Markdown

Summary

Syncs the hand-maintained v1 REST client types with a spec change from ellipsis-dev/ellipsis#5484.

The GET /v1/agents/templates response model (ListAgentTemplatesResponse in ellipsis/src/public_api/services/agent_templates_service.py) gained a new required field, and the v1 route now populates it (v1_router.py).

Changes

src/lib/types.ts

  • Changed ListAgentTemplatesResponse: added required field first_run_yaml: string (Pydantic first_run_yaml: str) — the verbatim YAML of the dashboard's first-run template (recent-work-summary), served alongside the gallery.

No new/removed/renamed endpoints, and no verb/path/query changes, so src/lib/api.ts is unchanged. AgentTemplate and all other v1 models are unchanged.

Verification

  • bun run typecheck — passes
  • bun run test — 107 passed

Out of scope

No run-stream / WebSocket frame schema changes in the triggering PR, so src/lib/ws.ts is untouched.

Triggered by merged spec change: ellipsis-dev/ellipsis#5484

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.

0 participants