Skip to main content

Goose isn’t responding

In the web app:
  • Refresh the page and try again.
  • Check your credit balance in Settings > Billing. If you’re out of credits, Goose can’t process messages.
  • Start a new chat session — the current session may have hit a state issue.
In Slack:
  • Make sure the Goose bot is invited to the channel.
  • Reply in a thread — Goose responds to threaded messages.
  • Check that the Slack integration is still connected in Settings > Integrations.
In Telegram / WhatsApp:
  • Verify the channel connection is active in Settings > Integrations.
  • Re-link the channel if the connection has expired.

Goose is slow

  • Long research tasks can take a minute or two. Goose shows a progress indicator when working on multi-step workflows.
  • Plan mode (Opus model) produces higher quality output but takes longer. Switch to Sonnet for faster responses.
  • If Goose seems stuck, start a new session and try again.

Goose gave incorrect or unexpected results

  • Be more specific — Add constraints to your prompt. Instead of “find leads,” try “find 10 Series A SaaS companies in the US with 50-200 employees.”
  • Check the skill — If using a skill, the instructions may need refinement. View the skill details and edit if needed.
  • Update memory — Goose may be working with outdated context. Check MEMORY.md and COMPANY.md in your workspace files.

Files aren’t showing up

  • Files created during a chat session should appear in the Files section immediately.
  • If a file was created in an automation, check the automation’s run history for errors.
  • Try refreshing the page.

Integrations not working

MCP servers:
  • Go to Settings > MCP Servers and check the connection status.
  • Make sure the server URL is accessible from the internet (localhost won’t work).
  • Check that any required API keys are set in Settings > Environment Variables.
Composio integrations (Notion, GitHub, Linear, etc.):
  • Re-authorize the integration if the OAuth token has expired.
  • Go to Settings > Integrations to see connection status.

Automation failed

  1. Go to Automations and find the failed run in the history.
  2. Check the error message — common causes:
    • Timeout — Agent-mode automations have a 15-minute limit. Simplify the prompt or break it into smaller steps.
    • Credit exhaustion — The automation ran out of credits mid-execution.
    • External API error — A third-party service (scraper, enrichment tool) was temporarily unavailable.
  3. Click Run Now to retry manually.

Account and login issues

  • Can’t log in — Gooseworks supports Google OAuth and magic links. Check your email (including spam) for the magic link.
  • Invited but can’t access — Make sure you’re logging in with the same email address that received the invitation.
  • Wrong organization — If you belong to multiple orgs, check the org switcher in settings.

Still stuck? Reach out at help@gooseworks.ai.