Reference and troubleshooting

Troubleshooting

Fix common provider, import, validation, prepared prompt, and export problems.

Who this is for

Anyone blocked by connection errors, malformed output, clone failures, or confusing exports.

Before you start

  • Note the exact error text.
  • Check which kit, provider, model, and import/export path you used.

Step-by-step guide

  1. 1

    Provider connection fails: check credentials, base URL, network access, and provider selection.

  2. 2

    Model not found: choose a known model or enter a custom model ID supported by your provider.

  3. 3

    Malformed JSON: use a model with stronger structured output reliability for Build with AI.

  4. 4

    Unresolved prepared prompt inputs: fill every required input before running.

  5. 5

    Git clone fails: check URL, branch, Git install, credentials, and network access.

  6. 6

    Access denied/private repo: confirm local Git credentials can access the repository.

  7. 7

    Kit validation errors: inspect missing files, manifest fields, and unsupported sections.

  8. 8

    One-file export confusion: use .onefile.md for web assistants, not as a full package replacement.

  9. 9

    Download page release status: v0.1 links stay disabled until release artifacts are uploaded.

Troubleshooting
Forge Current step Inputs Output
1
2
Prompt preview

Fix common provider, import, validation, prepared prompt, and export problems.

3

Tips

  • Start with validation errors before provider errors.
  • Test providers with a small prompt.
  • Use .agentkit.zip when preserving structure matters.

Common mistakes / troubleshooting

  • Retrying without changing the failing setting.
  • Assuming private Git repos use browser login.
  • Expecting unavailable release downloads.