docs(ai): add tool calls, agents, and agent orchestration to Vercel AI SDK guide#3419
Draft
nicolas-angelo wants to merge 2 commits into
Draft
Conversation
…Vercel AI SDK guide
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Companion PR to draft #3415 (Clerk x Vercel AI SDK patterns)
Extends the foundational concepts with added patterns for advanced usage.
Authorizing tool calls: Covers gating individual tool invocations by Clerk permissions, plans, or features. It also introduces authorization patterns with the new tool-approval mechanism arriving in AI SDK v7.
Agents: Introduces a new conceptual framing: Clerk machines as agent identities. It opens the question of extending machine identity to carry first-class agent metadata of its own. For simplicity, the page shows agent configuration persisted on
organization_metadataand projected onto eachM2M tokenclaims at mint time.Agent orchestration: Using M2M auth to verify-and-delegate between a parent agent and a subagent inside a resumable workflow.
Status
Draft. Same caveats as #3415, waiting for initial feedback before polishing or further testing.
Preview
https://clerk.com/docs/pr/nicolas-guides-ai-vercel-ai-sdk-advanced/guides/ai/vercel-ai-sdk/getting-started
Test plan
pnpm run build:tsxclean