Skip to main content

Common troubleshooting

Start with the symptom below. Before retrying a task that changes files or external data, check whether any part already completed. An error or stopped response is not proof that nothing happened.

Startup​

  1. Confirm that the installer matches your operating system and processor using System requirements and installation.
  2. Record the exact operating-system warning or startup error. Do not bypass a security warning without establishing that the installer is from the intended source.
  3. If Ghast opens, record its version in Settings → About. If it cannot open, provide the installer filename instead.

Do not delete Ghast's configuration as a first troubleshooting step: it can contain conversations, provider settings and extensions. Preserve your data before attempting a reset or reinstall.

Chat​

  1. Read the error beside the composer and note whether failure occurred before sending or during the response.
  2. If no model is selected, follow Enable, test, and select models.
  3. If the error concerns credentials or a disabled provider, check 0G Compute setup. If it concerns insufficient funds, follow funding instructions; do not repeatedly retry the same request.
  4. For a network or timeout error, check Network settings.
  5. After addressing the error, use the Quickstart text-only example to separate a model problem from an attachment or tool problem. This still sends a real model request and can consume usage.

If the short example works, add back only what the failing task needs and check the error again. For an action that may have sent, created or changed something, verify the destination before repeating it.

Tool not visible​

Check the selected model's tool support and the run's visible error or pending approval. For an external service, open Plugins → Manage connections and check its status and any tool-change review alert. For a Skill, check its enabled state in Plugins → Skills. The current Add menu has no Tools selector; follow the extension troubleshooting steps before reinstalling or changing permissions.

Tool failure​

Expand the failed tool card and read its error, requested target and any command exit code. If it is waiting for permission, follow Tool approvals; a waiting request is not the same as a failed execution.

For a send, delete, publish, create or payment action, inspect the destination first. If a result already exists, tell Ghast to continue from it rather than repeat the action. Do not switch to Full access merely to dismiss an unexplained error.

Files​

  1. Confirm the selected workspace and the file's full path.
  2. Open the file in the Files panel, refresh the tree if needed, and inspect the actual content.
  3. Read the failed tool result for a missing path, read-only location or permission request.
  4. Check Review and inline diffs before asking for another edit.

A natural-language “done” message does not prove a write occurred. A preview failure also does not prove the file is empty; check the original in an external editor when needed.

Context too long​

Open Context usage beside the composer. Remove unnecessary attachments from the pending draft and select only the tools and skills the task needs. In an existing long conversation, send /compact alone; see compaction and recovery for no-change and error cases. If starting a new conversation, carry over the current goal, constraints and verified progress—not just the last reply.

A Team task is blocked or incomplete​

Open the affected work item and read its status and latest explanation. Check the workspace, requested permission, provider error and any files already produced. Give the teammate the missing input or a concrete correction in the existing task; do not create a duplicate before checking whether the original is still active.

A channel does not reply​

Open the relevant channel settings and check whether its bot or app is connected. Then use that platform's setup guide to check permitted users/conversations, group mention requirements and platform permissions. These controls differ between channels.

If Ghast received the message but no reply arrived, check the model error and delivery status, plus the platform's message or attachment limits. Avoid repeatedly sending a task that may already be running.

Voice, Web, and Computer Use​

For voice input, check microphone permission and whether recognition preparation has finished. For spoken output, check the selected voice, playback controls and provider connection. These are separate features; use the Voice guide for the relevant flow.

For web search, check the selected engine, sign-in where required, and network connection. A result from a different engine or account may not reproduce the same page; see Web search.

For Computer Use, follow the platform setup and permission checks. Record which app and action failed without sharing private screen content.

Browser success does not prove Computer Use success.

Share a useful error report​

Include the Ghast version (if available), operating system, affected page, model or service, approximate time, the smallest steps that reproduce the issue, the redacted error, and whether anything changed before failure.

Do not include API keys, wallet recovery material, full conversation exports or customer data. Review screenshots for account details and private paths. If Ghast opens, see About and feedback for the feedback entry.