Why does Claude receive a queue ticket instead of a result when launching an osFoundry Graph?
This is the tool that a Claude chat calls to start a Graph in osFoundry, as listed by the public MCP endpoint. Retrieved with an unauthenticated tools/list on 2026-11-08 and shortened: { name : run_graph_session , description : Queue a Graph run on the owner's online desktop in a connected project. Retrieve progress and result with get_graph_run. The desktop can go offline,…
A tool used by Claude's chat to initiate a Graph in osFoundry was retrieved on November 8, 2026. The tool, called "run_graph_session", queues a Graph run on the owner's online desktop in a connected project. A Graph is a saved JavaScript program executed by the desktop's fleet engine, which can include conditional paths, parallel agents, and limited retries.
The desktop requests work from the server, rather than the server pushing it, and the process involves a relay that syncs with the server every 20 seconds. Tests of the system showed that runs can be queued for up to 20 seconds and that running multiple Graph sessions in parallel can actually slow down the process.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
