docs: expose agent followups endpoint#151
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR updates the OpenAPI sync exclusion policy and regenerated Agent API OpenAPI document to expose POST /agent/runs/{runId}/followups and the RunFollowupRequest schema. I did not find correctness, documentation-structure, security, or spec-alignment issues in the attached diff.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
2 participants
Summary
Expose
POST /agent/runs/{runId}/followupsin the public Agent API reference as a focused one-off update.This PR:
/agent/runs/{runId}/followupsfrom the OpenAPI sync exclusion policy.agentpaths.developers/agent-api-openapi.yamlso Scalar renders the follow-up endpoint andRunFollowupRequestschema.To keep this PR focused, the generated YAML was regenerated from the same
warp-serversource commit used by the last docs sync (810f9bce554ff3c276b308e4cf741f0f39bc954b) after removing only this exclusion, rather than pulling in unrelated currentwarp-serverOpenAPI drift.Related issues
Slack request to make
POST /api/v1/agent/runs/{runId}/followupsvisible indocs.warp.dev/api#tag/agent.Validation
python3 .agents/skills/sync-openapi-spec/scripts/sync_openapi.py --mode self-test→self-test: OKdevelopers/agent-api-openapi.yamlwith--mode apply→All $refs resolve in the regenerated spec.submitRunFollowup,/agent/runs/{runId}/followups, andRunFollowupRequestare present indevelopers/agent-api-openapi.yaml.npm cinpm run build→ 333 pages built successfully; only existing non-blocking prerender/header warnings were emitted.Screenshots
Not included; this is an OpenAPI spec update rendered by Scalar.
Follow-ups
Current
warp-serverhas additional OpenAPI drift beyond this endpoint (client-events,timeline, and schema changes). Those are intentionally out of scope for this one-off and can be handled by a separate full sync PR.Conversation: https://staging.warp.dev/conversation/f637f93c-9eed-4ce7-8580-296680a9b963
Run: https://oz.staging.warp.dev/runs/019e6f6c-a0c5-7d55-bb00-70ecc0beea75
This PR was generated with Oz.