Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Avoid attempting to serialize the "tool" during tool call execution by TooTallNate · Pull Request #790 · vercel/workflow · GitHub
Skip to content

Avoid attempting to serialize the "tool" during tool call execution - #790

Merged
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution
Jan 15, 2026
Merged

Avoid attempting to serialize the "tool" during tool call execution#790
TooTallNate merged 1 commit into
mainfrom
01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution

Conversation

@TooTallNate

@TooTallNateTooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
Member

Fixed serialization issue when executing tool calls in DurableAgent.

What changed?

Modified the executeTool function in durable-agent.ts to extract the execute method from the tool object before calling it, rather than invoking it directly on the tool object. This prevents JavaScript from binding this to the tool object, which contains non-serializable properties like inputSchema.

How to test?

Test tool execution in workflows where tools have complex properties that can't be serialized. Verify that tool calls complete successfully without serialization errors.

Why make this change?

When a tool's execute function is used as a workflow step (marked with 'use step'), the step system attempts to capture and serialize this. Since the tool object contains non-serializable properties, this was causing failures. By extracting the execute function before calling it, we avoid the serialization of the entire tool object.

@changeset-bot

changeset-botBot commented Jan 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2e34af0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
NameType
@workflow/aiPatch
@workflow/docs-typecheckPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercelBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actionsBot commented Jan 15, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production418011429
✅ 💻 Local Development38208390
✅ 📦 Local Production38208390
✅ 🐘 Local Postgres38208390
✅ 🪟 Windows390039
❌ 🌍 Community Worlds147210168
Total175021351806

❌ Failed Tests

🌍 Community Worlds (21 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (18 failed):

  • addTenWorkflow
  • addTenWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro3801
✅ example3801
✅ express3801
✅ fastify3801
✅ hono3801
✅ nextjs-turbopack3801
✅ nextjs-webpack3801
✅ nitro3801
✅ nuxt3801
✅ sveltekit3801
✅ vite3801
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable3801
✅ express-stable3801
✅ fastify-stable3801
✅ hono-stable3801
✅ nextjs-turbopack-stable3900
✅ nextjs-webpack-stable3900
✅ nitro-stable3801
✅ nuxt-stable3801
✅ sveltekit-stable3801
✅ vite-stable3801
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack3900
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb3810
✅ redis-dev300
❌ redis3810
✅ starter-dev300
❌ starter21180
✅ turso-dev300
❌ turso3810

📋 View full workflow run

@TooTallNateGraphite App

TooTallNate commented Jan 15, 2026

Copy link
Copy Markdown
MemberAuthor

This stack of pull requests is managed by Graphite. Learn more about stacking.

CopilotAI review requested due to automatic review settings January 15, 2026 18:56
@TooTallNate
TooTallNate changed the base branch from 01-09-add_support_for_custom_class_instance_serialization to graphite-base/790January 15, 2026 18:57
@TooTallNate
TooTallNateforce-pushed the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch from 119e416 to 2e34af0CompareJanuary 15, 2026 18:57
@TooTallNate
TooTallNate changed the base branch from graphite-base/790 to mainJanuary 15, 2026 18:57

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a serialization error that occurs when executing tool calls in DurableAgent where the tool's execute function is marked with 'use step'. The workflow step system attempts to capture and serialize the this context, which fails when this is bound to the tool object containing non-serializable properties like inputSchema.

Changes:

  • Modified executeTool function to extract the execute method before calling it, preventing this binding to the tool object
  • Added changeset documenting the fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
packages/ai/src/agent/durable-agent.tsExtracted execute function to avoid this binding during tool execution
.changeset/rude-suits-wonder.mdAdded changeset for patch version bump

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment threadpackages/ai/src/agent/durable-agent.ts
@TooTallNate
TooTallNate merged commit 49a1c5f into mainJan 15, 2026
130 of 134 checks passed
@TooTallNate
TooTallNate deleted the 01-15-avoid_attempting_to_serialize_the_tool_during_tool_call_execution branch January 15, 2026 21:43
Sign up for freeto 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.

3 participants

@TooTallNate@VaguelySerious