Troubleshooting

Start with what Row-Bot already tells you. The sidebar's attention indicator appears when something needs you, Overview's Needs you lists it, and Monitor shows every health check with a one-click fix. Most issues fall into one of four categories: setup is incomplete, a provider or tool is off, the wrong model is selected, or Row-Bot is waiting for your approval.

Setup Problems

• If Row-Bot keeps opening setup, finish How should Row-Bot think? or choose Set up later. Open Setup Center from Overview or the command palette to continue optional setup.
• Check Settings › Providers and Settings › Models before troubleshooting a conversation.
• Check Settings › System if local files, browser automation, or command execution are involved, and Settings › Devices & remote access for other devices or the public link.
• For native application control, open the Computer Use setup in Settings › System and resolve its driver or operating-system permission status before retrying.

Model Problems

• Refresh the provider in Settings › Providers, then refresh the catalog in Settings › Models.
• A model marked Unavailable in a picker says why; reconnecting its provider usually fixes it.
• Choose a tool-capable model for workflows, designs, code folders, and multi-step tool use.
• For local and custom endpoints, use enough context for Row-Bot's instructions and tool schemas; lower the Reading limit in Settings › Models on smaller computers.
• If reasoning choices are missing, rejected, or reset, use the active model's conditional control or /reasoning, then follow Reasoning Controls.

Chat, Tool, And Approval Problems

• Check the model picker, the composer's Mode (Agent or Chat only), the conversation's agent profile, its Approvals setting, and the enabled tools.
• If an action is waiting, approve or deny it in the conversation, from the sidebar's attention indicator, or from Overview. Approvals wait until you answer.
• If a step shows as skipped, it was denied and did not run.
• Ask Row-Bot to explain the last tool result if the transcript is unclear.
• If Computer Use is paused, choose Resume only after reviewing the target; if its lease is busy, stop or finish the active native task first.

Workflow Problems

• Confirm the workflow is enabled, and that an earlier run isn't still waiting for approval: while one waits, the next scheduled run is skipped.
• Run it once with Run before trusting a schedule.
• Check delivery defaults and the channel's status in Monitor.

Design And Code Folder Problems

• Designs: give a clearer goal, audience and length, and attach references. Exports use the last saved version.
• Code folders: check that the folder is listed under Working on in the conversation's details card. On a phone or in a browser, folders are chosen inside Row-Bot's workspace folder; anything outside it is only available from the desktop app's picker.
• Review commands and changes before approving or importing them.

Knowledge And Monitor Problems

• If Knowledge is empty, turn on memory in Settings › Memory or add documents in Settings › Documents.
• If a memory is wrong, edit, merge or archive it in Home › Knowledge.
• Use Monitor's Needs attention, History and Logs for background issues, and Copy diagnosis report when asking for help.

Apps And Skills

An app that isn't ready shows one status and one fix: the main action on its page in Settings › Apps, also offered in Overview's Needs you.

Status	What it means	Do this
Sign in needed	The app needs a sign-in, or its saved sign-in stopped working.	Sign in, or Sign in again.
Key needed	It needs a key or token.	Add key.
Finish setup	Setup stopped before the end, waiting for a setting, the actions to allow, or something it needs to run.	Continue setup.
Working…	Row-Bot is finishing your last change.	Wait a moment.
Needs attention	The connection failed, or Row-Bot couldn't confirm your last change.	Fix, or Retry.
Off	You turned it off.	Turn on.
Removed	A package was removed and its saved data kept.	Delete saved data when you no longer need it.

• Finishing your last change… Retry: Row-Bot couldn't confirm that a change finished, for example because it closed part-way. Retry checks what happened and never repeats the change.
• Open program, then check again: the app works with a program on this computer, such as Blender. Open the program and its add-on, then choose Check again.
• Install Docker Desktop, then try again, or Docker Desktop isn't running on this computer: the app runs as a container image. Install or open Docker Desktop, or choose another way to connect on the app's page.
• Signing in to an app from your phone: without a public address, the browser ends on a page that doesn't load at http://127.0.0.1. Copy that page's whole address and paste it into the sign-in step; see Sign in from a phone or another computer. If it says the address is from a different sign-in, open the sign-in page from the step again and paste the new address.
• App needs your own OAuth app to sign in: the service accepts only an OAuth app you create. Create one at the service, register the callback address the step shows, and paste its Client ID (and Client secret (optional), if it has one).
• If Google asks you to sign in every 7 days, your Google app is still in Testing; see Google sign-ins in Testing last 7 days.
• If an app's tools never appear in chat, check that it is Ready, that it is checked in the chat's + › Apps, that the chat's agent profile allows it, and that Use apps is on in Apps › Advanced.
• Channels and accounts are apps too (for example Apps › Telegram or Apps › Google); Open on the app's page opens their own settings. A stopped channel shows Restart in Monitor, and an account whose sign-in expired shows Reconnect there.
• Skills need to be in Your skills in Settings › Skills, turned on, and relevant to the prompt; you can also call one with its slash command.

Catalogs And Proxies

• Couldn't update. The last copy is still used.: the catalog couldn't be reached. Search keeps working with the last copy; choose Update again later.
• Behind a proxy, Row-Bot sends catalog updates and Search online catalogs through the proxy set in Windows or macOS settings or in the HTTPS_PROXY environment variable. It doesn't run automatic proxy configuration (PAC) scripts, so set the proxy's address itself.
• Logos, bundles downloaded from the Registry and app sign-ins connect directly, not through the proxy, so they fail on a network that allows only proxied traffic.

Windows Connectors, Composio And App Views

• Windows connectors appear in Apps › Advanced › Catalogs only on Windows builds that have Windows' On-device Agent Registry (Insider build 26220.7344 or later, with Experimental agentic features on). Choose Update to list them.
• Composio isn't searched until you turn on Use Composio in Apps › Advanced › Catalogs and agree to its disclosure: it is a separate service, with its own account, that keeps requests and results for up to a year by default. Turning it off doesn't remove a Composio connection you made; remove that on its page.
• App views show only under a step that succeeded, for an app that has views, while Show app views in chat (in Apps › Advanced) and Show views in chat on the app's page are on and the app is on in that chat. "This view didn't start" or "Views are busy" usually clears with Open again.

Remote Access And Server Mode

• If the browser shows untrusted_forwarding_headers, a proxy supplied forwarding metadata from an address Row-Bot does not trust. Restart after enabling a Row-Bot-owned Tailscale route. For another proxy, configure only its exact connecting address or CIDR; do not trust a broad network.
• If the browser shows unexpected_host, add the exact canonical browser-facing host and verify the proxy preserves it.
• If a code cannot be used, create it for the exact scheme, host, and port currently used by that browser. Expired, used and stale-route codes must be recreated.
• If Tailscale reports a conflict, Funnel, or an unowned route, inspect that configuration manually. Row-Bot deliberately refuses to reset or overwrite it.
• If a remote microphone is unavailable, use localhost or HTTPS, grant browser permission, and install the local voice model explicitly.
• "Disconnected. What you last saw is kept." means the browser lost its connection to Row-Bot: check that Row-Bot is running and the network is up, then Reconnect. "Something went wrong. Try again. Details: client_error" is a fault in the app, not the connection; reload the page, and report the details if it happens again.
• Run row-bot access doctor for a secret-free server and route safety report.

The full route, authentication, Docker, proxy, and recovery guidance is in Remote Access And Server Mode.

Voice And Buddy

• Check microphone and output device selection and permissions.
• Use Dictate before Talk if you need review.
• Check provider readiness for realtime voice.
• If docked Buddy is missing, enable Show Buddy in Settings › Buddy. If a torn-off overlay was hidden, use the tray's Show Buddy action.
• Drag Buddy itself out of the sidebar in the native Windows or macOS app. Browser/server and phone layouts cannot create the native overlay.
• Use Open full thread for microphone controls, complex approvals, attachments, tool traces, and complete conversation history.
• Restart Row-Bot to return Buddy placement to the sidebar dock; a saved hidden preference must still be turned back on.