Skip to content

Fix liberate_extract timeout #4095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nightnei merged 1 commit into from
Jul 7, 2026
+12 −4
Merged

Fix liberate_extract timeout #4095

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions apps/cli/ai/tools/data-liberation.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ import { textResult } from './utils';

const engineDir = path.join( import.meta.dirname, 'data-liberation-agent' );

// Engine ops (extract/screenshot/reconstruct) routinely run for minutes; the MCP SDK's
// 60 s default times them out (-32001) even though the engine keeps working.
const ENGINE_CALL_TIMEOUT_MS = 600_000;

let chromiumPromise: Promise< void > | null = null;

function ensureEngineChromium(): Promise< void > {
Expand Down Expand Up @@ -147,10 +151,14 @@ export const dataLiberationTool = defineTool(

await ensureEngineChromium();

const result = await client.callTool( {
name: args.tool,
arguments: normalizeArgs( args.args ),
} );
const result = await client.callTool(
{
name: args.tool,
arguments: normalizeArgs( args.args ),
},
undefined,
{ timeout: ENGINE_CALL_TIMEOUT_MS, resetTimeoutOnProgress: true }
);

const rawContent = Array.isArray( result.content )
? ( result.content as DataLiberationResultContent[] )
Expand Down
Loading