10 replies

embedded run timeout: timeoutMs=600000

✅Solved

Hi Krill,

my agent just ran into this timeout, but it wasn't real...it was doing tool calls the whole time and working on stuff. What's the config setting to increase this? I can't remember having seen it anywhere and the docs...not the greatest reference when searching something...

Thanks in advance!

Solution

That log line (

embedded run timeout: timeoutMs=600000

embedded run timeout: timeoutMs=600000

) is the hard wall-clock runtime cap for a single embedded agent run. Default is 600s = 10 minutes (tool calls don’t “reset” it — it’s just time since the run started).

Config knob:

{
  agents: {
    defaults: {
      timeoutSeconds: 1800, // e.g. 30 minutes
    },
  },
}

{
  agents: {
    defaults: {
      timeoutSeconds: 1800, // e.g. 30 minutes
    },
  },
}

Quick CLI way:

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•5h ago•

10 replies

Henry Loenwind

embedded run timeout: timeoutMs=600000

✅Solved

Solution

That log line (

embedded run timeout: timeoutMs=600000

embedded run timeout: timeoutMs=600000

) is the hard wall-clock runtime cap for a single embedded agent run. Default is 600s = 10 minutes (tool calls don’t “reset” it — it’s just time since the run started).

Config knob:

{
  agents: {
    defaults: {
      timeoutSeconds: 1800, // e.g. 30 minutes
    },
  },
}

{
  agents: {
    defaults: {
      timeoutSeconds: 1800, // e.g. 30 minutes
    },
  },
}

Quick CLI way:

Jump to solution

embedded run timeout: timeoutMs=600000

Similar Threads

embedded run timeout: timeoutMs=600000

Similar Threads

Similar Threads

Similar Threads