Skip to content

Conversation

@VaguelySerious
Copy link
Member

@VaguelySerious VaguelySerious commented Jan 9, 2026

Superseeded by #23

adriandlam and others added 24 commits November 26, 2025 09:35
* feat: add nuxt example

* lockfile
Update nextJS to patched versions and update workflows to beta-27
* basic express + workflow

* proper express w/nitro

* add workflow to transcode audio

* remove fluent-static in place of system ffmpeg

* use sandbox to run ffmpeg

* use streams over buffers

* Update readme + wav handling

* rename output

* update readme

* update typo + upgrade workflow

* convert to multi-steps

* separate sandbox impl into streams

* update tsconfig + imports

* remove middleware

* update readme and fix

* update readme

* update readme

* update readme

* tweaks

---------

Co-authored-by: Adrian Lam <[email protected]>
Signed-off-by: Peter Wielander <[email protected]>
Signed-off-by: Peter Wielander <[email protected]>
Signed-off-by: Peter Wielander <[email protected]>
Signed-off-by: Peter Wielander <[email protected]>
@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​workflow/​ai@​4.0.1-beta.447810084100100

View full report


// If we have output, the approval has been processed
if (output) {
try {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

executeBookingApproval returns plain string but BookingApproval component expects JSON with nested structure, causing JSON.parse to fail

Fix on Vercel

}

const handleSubmit = async (approved: boolean) => {
setIsSubmitting(true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The booking approval submission lacks error handling and user feedback - failed API requests are silently ignored

Fix on Vercel

Comment on lines 298 to 307
async function executeBookingApproval(
{
flightNumber,
passengerName,
}: { flightNumber: string; passengerName: string; price: number },
{ toolCallId }: { toolCallId: string }
) {
// Note: No "use step" here - hooks are workflow-level primitives
// Use the toolCallId as the hook token so the UI can reference it
const hook = bookingApprovalHook.create({ token: toolCallId });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
async function executeBookingApproval(
{
flightNumber,
passengerName,
}: { flightNumber: string; passengerName: string; price: number },
{ toolCallId }: { toolCallId: string }
) {
// Note: No "use step" here - hooks are workflow-level primitives
// Use the toolCallId as the hook token so the UI can reference it
const hook = bookingApprovalHook.create({ token: toolCallId });
async function executeBookingApproval({
flightNumber,
passengerName,
}: {
flightNumber: string;
passengerName: string;
price: number;
}) {
// Note: No "use step" here - hooks are workflow-level primitives
// The Workflow framework automatically manages the hook token and associates it with the tool call
const hook = bookingApprovalHook.create();

The executeBookingApproval function signature expects a second parameter { toolCallId }, but the Vercel AI SDK framework only passes a single parameter (the input object) to tool execute functions.

Fix on Vercel

@VaguelySerious
Copy link
Member Author

Superseeded by #23

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.