[{"data":1,"prerenderedAt":687},["ShallowReactive",2],{"help-category-\u002Ftroubleshooting\u002Fslow-agent-responses":3,"help-article-\u002Ftroubleshooting\u002Fslow-agent-responses":4,"related-articles-\u002Ftroubleshooting\u002Fslow-agent-responses":119},[],{"id":5,"title":6,"body":7,"category":104,"description":105,"draft":106,"extension":107,"meta":108,"navigation":109,"order":110,"path":111,"relatedArticles":112,"seo":113,"slug":114,"stem":115,"updatedAt":116,"__hash__":117,"excerpt":105,"searchText":118},"help\u002Fhelp\u002Ftroubleshooting\u002F08.slow-agent-responses.md","Slow agent responses",{"type":8,"value":9,"toc":95},"minimark",[10,14,19,22,45,49,52,57,61,64,67,71,74,79,83,86],[11,12,13],"p",{},"If your agent is taking longer than usual to reply, the most likely cause is slowness on the LLM provider's side — not MultiClaw itself. Check your provider's status page (OpenAI, Anthropic, etc.) first. If they're reporting an incident, you'll need to wait it out or switch models.",[15,16,18],"h2",{"id":17},"llm-provider-latency","LLM provider latency",[11,20,21],{},"The underlying language model is hosted by a third-party provider. Their server load directly affects how fast your agent responds. MultiClaw has no control over this.",[11,23,24,28,29,35,36,40,41,44],{},[25,26,27],"strong",{},"What to do:"," Visit your provider's status page — ",[30,31,32],"a",{"href":32,"rel":33},"https:\u002F\u002Fstatus.openai.com",[34],"nofollow"," or ",[30,37,38],{"href":38,"rel":39},"https:\u002F\u002Fstatus.anthropic.com",[34],". If the provider is healthy, try switching to a faster or lighter model in the agent's ",[25,42,43],{},"Model"," settings.",[15,46,48],{"id":47},"large-context-window","Large context window",[11,50,51],{},"Every message you send includes the full conversation history. As a conversation grows, the payload sent to the model grows too — and processing time increases with it.",[11,53,54,56],{},[25,55,27],{}," Start a new conversation to reset the context. This is the most reliable way to reduce latency caused by accumulated history.",[15,58,60],{"id":59},"complex-multi-step-task","Complex multi-step task",[11,62,63],{},"Agents working through a multi-step plan take longer by design. Each step requires the model to reason, act, and check results before moving on. This is expected behaviour, not a bug.",[11,65,66],{},"You'll see the agent's progress in the chat. If it appears completely stuck — no activity for several minutes — that's a different issue from general slowness.",[15,68,70],{"id":69},"slow-internet-connection","Slow internet connection",[11,72,73],{},"A weak connection between your machine and the LLM provider's API adds latency to every request. Even a small amount of packet loss compounds across a long conversation.",[11,75,76,78],{},[25,77,27],{}," Switch to a faster network if possible. You can use a speed test to confirm local bandwidth isn't the bottleneck.",[15,80,82],{"id":81},"too-many-mcp-tools-enabled","Too many MCP tools enabled",[11,84,85],{},"At the start of every turn, the agent sends the schemas for all enabled MCP tools to the model. More tools means a larger payload, which slows down the first token of each response.",[11,87,88,90,91,94],{},[25,89,27],{}," Disable any MCP servers you're not actively using. Open ",[25,92,93],{},"MCP Servers"," from the sidebar and toggle off unused servers.",{"title":96,"searchDepth":97,"depth":97,"links":98},"",2,[99,100,101,102,103],{"id":17,"depth":97,"text":18},{"id":47,"depth":97,"text":48},{"id":59,"depth":97,"text":60},{"id":69,"depth":97,"text":70},{"id":81,"depth":97,"text":82},"troubleshooting","Understand and reduce latency caused by LLM load, large context, high token limits, or MCP tools.",false,"md",{},true,8,"\u002Ftroubleshooting\u002Fslow-agent-responses",[],{"title":6,"description":105},"slow-agent-responses","help\u002Ftroubleshooting\u002F08.slow-agent-responses","2026-03-30","M7cSrdB_9HUH8aVk-QAclXO-lCwznINr1-NhLEMWav8","Slow agent responses Understand and reduce latency caused by LLM load, large context, high token limits, or MCP tools.",[120,262,504],{"id":121,"title":122,"body":123,"category":104,"description":252,"draft":106,"extension":107,"meta":253,"navigation":109,"order":254,"path":255,"relatedArticles":256,"seo":257,"slug":258,"stem":259,"updatedAt":116,"__hash__":260,"excerpt":252,"searchText":261},"help\u002Fhelp\u002Ftroubleshooting\u002F01.agent-shows-disconnected.md","Agent shows 'Disconnected'",{"type":8,"value":124,"toc":243},[125,140,144,153,157,160,164,172,176,187,191,207,211,219,223,232],[11,126,127,128,131,132,135,136,139],{},"The ",[25,129,130],{},"Disconnected"," badge appears when the local OpenClaw gateway cannot reach MultiClaw Cloud. In most cases, the gateway has stopped — open ",[25,133,134],{},"Settings > Gateway"," and click ",[25,137,138],{},"Start gateway"," to fix it.",[15,141,143],{"id":142},"gateway-is-not-running","Gateway is not running",[11,145,146,147,149,150,152],{},"This is the most common cause. Go to ",[25,148,134],{}," and check the gateway status. If it shows as stopped, click ",[25,151,138],{}," and wait a few seconds for the agent status to update.",[15,154,156],{"id":155},"internet-connection-is-unavailable","Internet connection is unavailable",[11,158,159],{},"The gateway requires internet access to reach MultiClaw Cloud. Verify your machine can load a webpage. If your network is down, the agent will reconnect automatically once connectivity is restored.",[15,161,163],{"id":162},"multiclaw-cloud-is-experiencing-an-outage","MultiClaw Cloud is experiencing an outage",[11,165,166,167,171],{},"If your gateway is running and you have internet access, check ",[30,168,169],{"href":169,"rel":170},"https:\u002F\u002Fstatus.multiclaw.io",[34]," for any active incidents. No action is needed on your end — the gateway will reconnect once the service recovers.",[15,173,175],{"id":174},"workspace-session-has-expired","Workspace session has expired",[11,177,178,179,182,183,186],{},"Your session can expire after a period of inactivity. Go to ",[25,180,181],{},"Settings > General",", scroll to the ",[25,184,185],{},"Account"," card, and sign in again. The gateway will re-authenticate and the agent should show as connected within a few seconds.",[15,188,190],{"id":189},"firewall-or-proxy-blocking-the-connection","Firewall or proxy blocking the connection",[11,192,193,194,197,198,201,202,206],{},"Some corporate firewalls block outbound WebSocket connections. The gateway connects to MultiClaw Cloud over port ",[25,195,196],{},"443"," using the ",[25,199,200],{},"WSS"," protocol. Ask your IT administrator to allow outbound WSS traffic on port 443 to ",[203,204,205],"code",{},"*.multiclaw.io",".",[15,208,210],{"id":209},"auth-token-has-expired-or-been-revoked","Auth token has expired or been revoked",[11,212,213,214,182,216,218],{},"If signing in again does not help, your local auth token may be corrupted or revoked. Go to ",[25,215,181],{},[25,217,185],{}," card, sign out completely, then sign back in. This replaces the stored token and typically resolves the issue.",[15,220,222],{"id":221},"gateway-is-running-but-agent-stays-disconnected","Gateway is running but agent stays disconnected",[11,224,225,226,135,228,231],{},"Transient WebSocket errors can leave the gateway in a stuck state. Go to ",[25,227,134],{},[25,229,230],{},"Restart gateway",". The gateway reconnects with exponential back-off — waiting 30–60 seconds after a brief network interruption often resolves it without a manual restart.",[233,234,236],"callout",{"type":235},"tip",[11,237,238,239,242],{},"If none of the steps above work, check the gateway log at ",[203,240,241],{},"~\u002F.openclaw\u002Flogs\u002Fgateway.log"," for error messages that may point to the cause.",{"title":96,"searchDepth":97,"depth":97,"links":244},[245,246,247,248,249,250,251],{"id":142,"depth":97,"text":143},{"id":155,"depth":97,"text":156},{"id":162,"depth":97,"text":163},{"id":174,"depth":97,"text":175},{"id":189,"depth":97,"text":190},{"id":209,"depth":97,"text":210},{"id":221,"depth":97,"text":222},"Fix a disconnected agent status caused by gateway, network, session, or firewall issues.",{},1,"\u002Ftroubleshooting\u002Fagent-shows-disconnected",[],{"title":122,"description":252},"agent-shows-disconnected","help\u002Ftroubleshooting\u002F01.agent-shows-disconnected","9zuPiU2Ea9ivpf9-W_pFwN6PdgHplZxnykc7tldh_5k","Agent shows 'Disconnected' Fix a disconnected agent status caused by gateway, network, session, or firewall issues.",{"id":263,"title":264,"body":265,"category":104,"description":495,"draft":106,"extension":107,"meta":496,"navigation":109,"order":97,"path":497,"relatedArticles":498,"seo":499,"slug":500,"stem":501,"updatedAt":116,"__hash__":502,"excerpt":495,"searchText":503},"help\u002Fhelp\u002Ftroubleshooting\u002F02.gateway-fails-to-start.md","Gateway fails to start",{"type":8,"value":266,"toc":487},[267,295,299,305,310,346,350,353,357,375,379,382,386,411,415,418,422,447,451,454,458,477,481],[11,268,269,270,35,273,276,277,279,280,283,284,287,288,291,292,294],{},"If your gateway shows a red ",[25,271,272],{},"Error",[25,274,275],{},"Stopped"," status in ",[25,278,134],{}," and won't start, a port conflict is the most common cause. The gateway port is configured in your OpenClaw configuration file (",[203,281,282],{},"~\u002F.openclaw\u002Fopenclaw.json",") — if port ",[203,285,286],{},"18789"," is taken, update the ",[203,289,290],{},"port"," value there, then click ",[25,293,230],{},". If that doesn't help, work through the causes below.",[15,296,298],{"id":297},"port-conflict","Port conflict",[11,300,301,302,304],{},"Another process on your machine is already using port ",[203,303,286],{}," (the default gateway port). The gateway cannot bind to a port that's taken.",[11,306,307],{},[25,308,309],{},"To fix:",[311,312,313,320,331,339],"ol",{},[314,315,316,317,319],"li",{},"Open ",[203,318,282],{}," in a text editor.",[314,321,322,323,326,327,330],{},"Change the ",[203,324,325],{},"\"port\""," value to an unused port (e.g. ",[203,328,329],{},"18790",").",[314,332,333,334,336,337,206],{},"Save the file and click ",[25,335,230],{}," in ",[25,338,134],{},[314,340,341,342,345],{},"If you're on macOS or Linux and want to identify the conflicting process first, run ",[203,343,344],{},"lsof -i :18789"," in your terminal.",[15,347,349],{"id":348},"missing-or-corrupt-openclaw-binary","Missing or corrupt OpenClaw binary",[11,351,352],{},"The OpenClaw binary was deleted, moved, or never fully downloaded. Without it, the gateway cannot run.",[11,354,355],{},[25,356,309],{},[311,358,359,368],{},[314,360,361,362,367],{},"Reinstall the MultiClaw desktop app from ",[30,363,366],{"href":364,"rel":365},"https:\u002F\u002Fmulticlaw.io\u002Fdownload",[34],"multiclaw.io\u002Fdownload"," — this restores the OpenClaw binary.",[314,369,370,371,336,373,206],{},"Once reinstalled, click ",[25,372,230],{},[25,374,134],{},[15,376,378],{"id":377},"empty-or-invalid-workspace-token","Empty or invalid workspace token",[11,380,381],{},"Your gateway token was cleared — this can happen after a failed sign-in or an app reset. The gateway won't start without a valid token.",[11,383,384],{},[25,385,309],{},[311,387,388,396,402,405],{},[314,389,316,390,392,393,395],{},[25,391,181],{}," and scroll to the ",[25,394,185],{}," card.",[314,397,398,399,206],{},"Click ",[25,400,401],{},"Log out",[314,403,404],{},"Sign back in with your account credentials.",[314,406,407,408,410],{},"Your token is regenerated automatically. Click ",[25,409,230],{}," once signed in.",[15,412,414],{"id":413},"binary-not-executable-macos-and-linux","Binary not executable (macOS and Linux)",[11,416,417],{},"The OpenClaw binary exists but does not have execute permissions. This often happens after a manual file move or a filesystem restore.",[11,419,420],{},[25,421,309],{},[311,423,424,435,441],{},[314,425,426,427,430,431,434],{},"The OpenClaw binary is located at ",[203,428,429],{},"~\u002F.openclaw\u002Fbin\u002Fopenclaw"," on macOS and Linux (or ",[203,432,433],{},"%APPDATA%\\OpenClaw\\bin\\openclaw.exe"," on Windows).",[314,436,437,438,206],{},"In your terminal, run ",[203,439,440],{},"chmod +x ~\u002F.openclaw\u002Fbin\u002Fopenclaw",[314,442,398,443,336,445,206],{},[25,444,230],{},[25,446,134],{},[15,448,450],{"id":449},"data-directory-inaccessible","Data directory inaccessible",[11,452,453],{},"The OpenClaw data directory no longer exists or your user account cannot write to it. The gateway needs a writable directory to store its data.",[11,455,456],{},[25,457,309],{},[311,459,460,464,471],{},[314,461,316,462,319],{},[203,463,282],{},[314,465,466,467,470],{},"Update the ",[203,468,469],{},"\"data_dir\""," value to a folder that exists and that you have write access to.",[314,472,398,473,336,475,206],{},[25,474,230],{},[25,476,134],{},[15,478,480],{"id":479},"still-not-working","Still not working?",[11,482,483,484,486],{},"Check the gateway log at ",[203,485,241],{}," — it will usually identify the exact failure line.",{"title":96,"searchDepth":97,"depth":97,"links":488},[489,490,491,492,493,494],{"id":297,"depth":97,"text":298},{"id":348,"depth":97,"text":349},{"id":377,"depth":97,"text":378},{"id":413,"depth":97,"text":414},{"id":449,"depth":97,"text":450},{"id":479,"depth":97,"text":480},"Diagnose and fix port conflicts, missing binaries, token errors, and permission problems.",{},"\u002Ftroubleshooting\u002Fgateway-fails-to-start",[],{"title":264,"description":495},"gateway-fails-to-start","help\u002Ftroubleshooting\u002F02.gateway-fails-to-start","_0wciXQlb9TxhMmXBMEySTf8zKPz2-_ue4yZEGoHNvI","Gateway fails to start Diagnose and fix port conflicts, missing binaries, token errors, and permission problems.",{"id":505,"title":506,"body":507,"category":104,"description":677,"draft":106,"extension":107,"meta":678,"navigation":109,"order":679,"path":680,"relatedArticles":681,"seo":682,"slug":683,"stem":684,"updatedAt":116,"__hash__":685,"excerpt":677,"searchText":686},"help\u002Fhelp\u002Ftroubleshooting\u002F03.cannot-sign-in.md","Cannot sign in",{"type":8,"value":508,"toc":669},[509,512,516,527,542,546,549,554,565,570,586,590,597,611,615,618,632,636,639,650,654,657],[11,510,511],{},"If you cannot sign in, start by checking your workspace URL — most sign-in failures are caused by using the wrong subdomain. Open your invite email and copy the URL directly from it.",[15,513,515],{"id":514},"wrong-workspace-url","Wrong workspace URL",[11,517,518,519,522,523,526],{},"Your workspace has a unique subdomain. ",[203,520,521],{},"acme.multiclaw.io"," and ",[203,524,525],{},"acme.app.multiclaw.io"," are different addresses — only one is yours.",[311,528,529,532,535],{},[314,530,531],{},"Open your original invite email.",[314,533,534],{},"Copy the workspace URL exactly as written.",[314,536,537,538,541],{},"Paste it into your browser or the Desktop app's ",[25,539,540],{},"Workspace URL"," field.",[15,543,545],{"id":544},"expired-or-invalid-session","Expired or invalid session",[11,547,548],{},"Your session token may have expired, especially after a long period of inactivity.",[11,550,551],{},[25,552,553],{},"On the web dashboard:",[311,555,556,562],{},[314,557,558,559,206],{},"Open your browser's cookie settings and clear all cookies for ",[203,560,561],{},"multiclaw.io",[314,563,564],{},"Return to your workspace URL and sign in again.",[11,566,567],{},[25,568,569],{},"On the Desktop app:",[311,571,572,579,583],{},[314,573,574,575,392,577,395],{},"Go to ",[25,576,181],{},[25,578,185],{},[314,580,398,581,206],{},[25,582,401],{},[314,584,585],{},"Sign back in with your credentials.",[15,587,589],{"id":588},"sign-in-with-multiplai-error","Sign in with Multiplai error",[11,591,592,593,596],{},"If you use ",[25,594,595],{},"Sign in with Multiplai"," and see an error, the issue is usually a session mismatch between Multiplai and MultiClaw.",[311,598,599,602,608],{},[314,600,601],{},"Sign out of both Multiplai and MultiClaw completely.",[314,603,604,605,607],{},"Return to the MultiClaw sign-in screen and click ",[25,606,595],{}," again.",[314,609,610],{},"If the error persists, try signing in with email and password instead, or contact support.",[15,612,614],{"id":613},"email-not-confirmed","Email not confirmed",[11,616,617],{},"If you signed up recently and have never signed in before, your email address may not be confirmed yet.",[311,619,620,623,626],{},[314,621,622],{},"Check your inbox and spam\u002Fjunk folder for a confirmation email from MultiClaw.",[314,624,625],{},"Click the link inside that email.",[314,627,628,629,206],{},"If the email has expired or you cannot find it, return to the sign-in screen and click ",[25,630,631],{},"Resend confirmation",[15,633,635],{"id":634},"account-locked","Account locked",[11,637,638],{},"After repeated failed sign-in attempts, access may be temporarily restricted.",[311,640,641,644],{},[314,642,643],{},"Wait a few minutes, then try again.",[314,645,646,647,206],{},"If you still cannot sign in, ask your workspace admin to check your account status in MultiClaw Cloud under ",[25,648,649],{},"Settings → Members",[15,651,653],{"id":652},"multiclaw-cloud-is-down","MultiClaw Cloud is down",[11,655,656],{},"Occasionally, sign-in fails because the service itself is unavailable.",[311,658,659,666],{},[314,660,661,662,665],{},"Visit ",[30,663,169],{"href":169,"rel":664},[34]," to check for active incidents.",[314,667,668],{},"If an incident is reported, wait for it to be resolved — no action is needed on your end.",{"title":96,"searchDepth":97,"depth":97,"links":670},[671,672,673,674,675,676],{"id":514,"depth":97,"text":515},{"id":544,"depth":97,"text":545},{"id":588,"depth":97,"text":589},{"id":613,"depth":97,"text":614},{"id":634,"depth":97,"text":635},{"id":652,"depth":97,"text":653},"Resolve sign-in failures caused by wrong workspace URL, expired sessions, SSO errors, or unconfirmed email.",{},3,"\u002Ftroubleshooting\u002Fcannot-sign-in",[],{"title":506,"description":677},"cannot-sign-in","help\u002Ftroubleshooting\u002F03.cannot-sign-in","59H6ZnK81o4O-gYFOFiVOMekfEPx496CxJfHU7S5Myw","Cannot sign in Resolve sign-in failures caused by wrong workspace URL, expired sessions, SSO errors, or unconfirmed email.",1778463887060]