Goatfied — The AI code editor

Sign-in

Stuck on the sign-in tab? Make sure your browser allows the redirect back to Goatfied, then start the sign-in again.
On a corporate network, allowlist api.goatfied.com and goatfied.com.

Completions or chat not responding

Check connectivity to api.goatfied.com; a proxy or VPN can block the streaming connection.
If a model is rate-limited, Goatfied falls back automatically — a brief slowdown is expected during failover.
Confirm you’re signed in and your plan is active in Settings → Billing.

@codebase returns nothing

The index may still be building on a large repo. Give it a moment and try again.
Check the files you expect are the kind that get indexed.

Behind a proxy or VPN

Streaming responses use a long-lived text/event-stream connection. Proxies that buffer responses can make replies appear to hang — allow streaming to api.goatfied.com or add an exception.
Corporate TLS inspection can break the connection. Allowlist api.goatfied.com and goatfied.com rather than re-signing their certificates.

Identifying a request

Every model response carries x-goat-* headers that tell you exactly how it was served — useful when reporting an issue:

x-goat-provider — which upstream served the request.
x-goat-model — the exact model id used.
x-goat-route — the surface (chat, edit, tab).
x-goat-tier — the billing tier applied.

The desktop app surfaces these on each reply’s metrics chip when metrics are enabled in Settings. Include them in any bug report so we can trace the request.

Still stuck?