fix(tools): check usage limits before running hosted-key tools via the API - #8602
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
All reported issues were addressed across 7 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
|
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
All reported issues were addressed across 7 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
Summary
POST /api/v2/tools/{toolId}/execute, using the same cached execution gate as workflow runs402 USAGE_LIMIT_EXCEEDEDwhen the limit is exceeded, and document it in the OpenAPI specType of Change
Testing
execute-tool.test.tsand the route test (new cases fail with the fix reverted)bun run lint,bun run type-check,bun run check:audits,docs-manifest:check, block-registry checktest:scripts:generate-docs.test.tstimes out locally, same on clean stagingChecklist
test-auditauthoring gate)🤖 Generated with Claude Code