Error codes

Prerequisites

Before troubleshooting AI messages or errors:

• Sign in to your KrixIsHere account.
• Connect a Model provider in Integrations.
• Use a model that supports the feature you are trying to run.
• Connect GitHub if your request requires repository analysis.
• Keep secrets, API keys, and passwords out of chat messages.

AI Message Types

KrixIsHere can show several kinds of AI-related messages in the dashboard.

Standard AI Response

A standard response is the main answer from the selected model.

It may include:

• Markdown text
• Code blocks
• Lists
• Explanations
• Suggested next steps

Example:

Explain why this function returns undefined and suggest a fix.

Expected result:

• The AI replies with an explanation.
• If available, usage information appears below the message.
• If tools were used, agent activity appears below the message.

Thinking Status

When the AI is working, KrixIsHere may show a temporary thinking state.

This can include:

• How long the model has been thinking
• Whether it is searching, reading, or calling a tool
• A loading indicator while the response is being generated

This state disappears when the final response is ready.

Tool Activity

Some models can call tools when needed.

Tool activity may appear when the AI:

• Searches the web
• Reads a public web page
• Sends a safe public GET or HEAD API request
• Reads a connected GitHub repository in read-only mode
• Requests permission to open a browser preview
• Asks a clarifying question

Tool results may appear below the AI message as agent actions.

API Response Details

KrixIsHere may show API response details under an AI message.

These details can include:

• prompt_tokens
• completion_tokens
• total_tokens
• Remaining credits, if returned by the provider

Example response object:

{
  "usage": {
    "prompt_tokens": 22,
    "completion_tokens": 14,
    "total_tokens": 36
  }
}

What Tokens Mean

Tokens are small pieces of text used by AI models.

• prompt_tokens are used by your input.
• completion_tokens are used by the AI response.
• total_tokens is the combined usage.

Longer prompts, large pasted code blocks, and longer answers usually use more tokens.

Access Alerts

KrixIsHere uses full-screen alerts for important permission and access messages.

Provider Not Connected

This appears when you try to use AI before connecting a model provider.

Fix:

1. Open Integrations. 2. Connect the Model provider. 3. Retry the message.

GitHub Required

This appears when the AI needs repository access but GitHub is not connected.

Fix:

1. Open Integrations. 2. Select Connect GitHub. 3. Complete GitHub OAuth. 4. Retry the request.

GitHub access is read-only. The AI cannot modify repositories.

Browser Permission Required

This appears when the AI wants to open a public page in the browser preview.

You can choose:

• Allow once to open the page.
• Deny to block the action.

The AI cannot open or control a page without your approval.

AI Access Blocked

This appears when an administrator has blocked AI access for your account or IP address.

The alert may include:

• Block reason
• Expiration time, if temporary
• Whether the IP address was also blocked

If you believe this is a mistake, contact an administrator.

Error Codes

KrixIsHere and connected providers may return HTTP error codes.

200 OK

The request succeeded.

Expected result:

• The response is shown in the dashboard.
• Token usage may appear if returned by the provider.

400 Bad Request

The request was invalid.

Common causes:

• Missing required fields
• Invalid model ID
• Invalid JSON body
• Unsupported tool arguments
• Unsafe path or repository input

Fix:

• Check the request format.
• Retry with a shorter or clearer message.
• Make sure required fields are included.

401 Unauthorized

You are not signed in or the current session is not valid.

Common causes:

• Signed-out user
• Expired session
• Missing authenticated account for GitHub repository tools

Fix:

1. Sign in again. 2. Refresh the dashboard. 3. Retry the request.

402 Payment Required

The AI provider returned insufficient credits.

Fix:

• Add credits with the provider.
• Use a cheaper model.
• Reduce prompt length.
• Retry later if credits were just added.

403 Forbidden

The request was blocked by permissions.

Common causes:

• Non-admin user trying to access admin routes
• GitHub not connected
• AI access blocked by an administrator
• User is not allowed to access a requested resource

Fix:

• Confirm you are signed in with the correct account.
• For admin pages, make sure your Clerk user ID is listed in ADMIN_IDS or NEXT_PUBLIC_ADMIN_IDS.
• For GitHub analysis, connect GitHub first.
• If blocked, contact an administrator.

404 Not Found

The route or resource does not exist.

Common causes:

• Wrong API route
• Removed endpoint
• Repository file path does not exist
• Local workspace endpoint is unavailable

Fix:

• Check the route or file path.
• Use GitHub repository tools or paste code into the chat.
• Do not rely on local workspace access.

410 Gone

The requested feature is no longer available.

Example:

• Local workspace access was intentionally disabled for security.

Fix:

• Connect GitHub for read-only repository analysis.
• Paste code directly into the chat.
• Upload a safe text or source-code file.

429 Too Many Requests

Too many requests were sent too quickly.

Fix:

• Wait before retrying.
• Reduce repeated sends.
• Avoid rapidly submitting the same request.

500 Internal Server Error

The server failed unexpectedly.

Fix:

• Retry once.
• If it continues, report the issue with the page, request, and approximate time.

502 Bad Gateway

A connected provider or external service failed.

Common causes:

• AI provider unavailable
• Web research provider unavailable
• GitHub API request failed
• Public page could not be fetched safely

Fix:

• Retry later.
• Check the provider status.
• Use a smaller request.
• Paste the relevant content manually if needed.

Tool-Specific Errors

Web Research Failed

The AI could not search or read a public page.

Possible causes:

• The page is too large.
• The page is not HTML or plain text.
• The page blocks access.
• The URL redirects too many times.
• The URL points to a private or local network address.

Fix:

• Use a public https:// URL.
• Paste the relevant text into the chat.
• Try another source.

Browser Preview Blocked

Some websites block embedded previews.

Expected result:

• KrixIsHere shows a message explaining that the preview is blocked.
• You may still open the page externally.

Fix:

• Select Open externally.
• Use another source if the page cannot be accessed.

GitHub Not Connected

The AI tried to use repository tools without a GitHub connection.

Fix:

1. Open Integrations. 2. Select Connect GitHub. 3. Retry the repository request.

Repository Blocked

Some repositories are permanently blocked from agent access.

This protects the source code of the running KrixIsHere application and other protected repositories.

Fix:

• Choose another repository.
• Paste a safe excerpt into the chat.

Protected File Blocked

The AI cannot read files that look like secrets.

Blocked examples may include:

• .env
• credential files
• secret files
• private key files

Fix:

• Do not upload or request secrets.
• Paste a safe, redacted excerpt if needed.

Troubleshooting Checklist

If an AI request fails:

1. Confirm you are signed in. 2. Confirm the Model provider is connected. 3. Check whether the selected model supports tools. 4. Connect GitHub if repository analysis is required. 5. Avoid secrets, private network URLs, and protected files. 6. Shorten very large prompts or code blocks. 7. Retry after a short wait if you see 429 or 502. 8. Contact an administrator if you see an access block or repeated 403.

Safe Error Report Template

Use this format when reporting a problem:

Page: /dashboard
Action: What you tried to do
Error code: 403
Message shown: Paste the visible error message
Model: Selected model name
Time: Approximate time of the issue
Account: Your KrixIsHere account email or username

Do not include API keys, provider tokens, passwords, .env values, or private repository secrets.