## Documentation Index

Fetch the complete documentation index at: [https://www.anything.com/docs/llms.txt](https://www.anything.com/docs/llms.txt)

Use this file to discover all available pages before exploring further.

Nearly every issue you may encounter with your project is directly fixable with prompting. Please consider reviewing our [prompting guide](/content/docs/prompting/index.html) for best results

## How to triage

Our tips on how to best troubleshoot your project, review bugs, errors and use discussion mode to get ideal prompts to correct them.

Debug with Dylan: How to triage and prompt your way out of issues

[Debug with Dylan: How to triage and prompt your way out of issues](https://www.loom.com/share/d89db7a65e9c4ab69e0b857310d8b0cf?source=embed_watch_on_loom_cta "Debug with Dylan: How to triage and prompt your way out of issues")

1. Open your application and clearly identify what’s not working. For mobile apps, test on your device using [Expo Go](https://apps.apple.com/us/app/expo-go/id982107779) to reproduce errors accurately. **Focus on one issue at a time for best results.**

2. Copy the error message from your logs (use the copy button at the bottom of error logs) and note the specific behavior or feature that’s broken.

3. Switch to Discussion Mode and paste the error. The AI will analyze the issue and provide you with an ideal prompt to fix it. Copy this prompt for the next step. **Watch the video above for detailed guidance on this process.**

4. Toggle back to Thinking Mode and paste the prompt from Discussion Mode. The AI will execute the fix automatically. Allow time for testing and verification.

5. Refresh your preview after the process completes, then test the previously broken functionality to confirm the fix worked.

## Fixing issues yourself

### Reviewing Error Logs

How to review error logs and provide context to your AI agent to help fix them.

Anything: How to review error logs in development

[Anything: How to review error logs in development](https://www.loom.com/share/e0aee208a2744ef0b897daea6c0edf80?source=embed_watch_on_loom_cta "Anything: How to review error logs in development")

## App Error Detected

When Anything detects a problem with your published or preview app, it shows an **App Error Detected** banner automatically. This is built-in error monitoring. You don’t need to do anything to enable it. Click **Try to Fix** and the AI builder will attempt to diagnose and repair the issue for you. This repair attempt is free — it uses no credits.

## Browser

We recommend [Google Chrome](https://www.google.com/chrome/) for the best experience using Anything. Many display issues, failed previews, and mobile submission errors are caused by outdated or unsupported browsers. [Download Chrome here](https://www.google.com/chrome/).

## Restarting Preview Server

**Preview Server Issues?** We’ve received reports that certain ISPs may be blocking our preview server URLs. **How to identify this issue:**

- Your preview shows a blank page or fails to load
- Mobile app previews get stuck on the “preview loading screen”

## Version History Restore

If you need to revert to a previous version of your project, you can use the Version History feature to restore from an earlier point directly in the chat.

## Status Page

If there is an outage or system wide issue we will report it on our status page available at [status.anything.com](https://status.anything.com/)

## Support

Our primary support channel is over email, [hello@anything.com](mailto:hello@anything.com). Please reach out with questions or to report issues with your build. Please consider including your build URL to help us expedite any investigation. Thank you!

### Sharing Your Build

When asking for help, please include:

1. Your builder URL.
   - **For web users:** Open your project to edit it, then copy the URL from your browser’s address bar (this is your builder url)
   - **For iOS users:**
     1. Open app in question in the iOS App
     2. Open chat/builder overlay via the black button on the left side of the nav screen
     3. Click on the URL icon in the top of the menu

2. Whenever possible include a specific description of what’s not working (e.g., “The function called “RetrieveWeather” returns a 500 error when submitting the form”)

Your build links are private - even if shared publicly, only team members can access them. Anything team members and admins can jump into your build to help you out (with your permission).