Noodle Seed
Guides

Troubleshooting

How noodle validate reports errors and how to fix the common ones. The self-correcting loop for humans and coding agents.

Noodle Seed is built around a tight repair loop: change server.ts, run noodle validate, read the error, fix it, repeat. Validation is local and needs no account.

The validate loop

noodle validate            # human-readable errors
noodle validate --json     # structured errors (for tooling and agents)
noodle validate --fix-prompt   # emit a prompt you can hand to a coding agent

Fix the specific error reported, then re-run. Do not freeform re-edit around a validation error; resolve the one it cites and validate again.

For coding agents

Prefer noodle validate --json to read errors programmatically, or --fix-prompt to get a ready-to-apply repair prompt. See Build with coding agents.

Common errors

Diagnose the environment

noodle doctor    # checks login, service reachability, project config, and validation

noodle doctor is the fastest way to find a misconfigured project, a missing entrypoint, or a service/login problem before you deploy.

Runtime version

The CLI requires Node.js 24 LTS or newer. If noodle fails to start, check node --version and switch with nvm, fnm, mise, or volta, or run any command through npx @noodleseed/one@latest.

Read the logs

Every hosted deployment has a tenant-safe log surface — redacted, bounded, newest-first:

noodle logs                             # recent records for the linked project
noodle logs --level error               # debug | info | warn | error
noodle logs --search "connector"        # case-insensitive text match (plain text, not a regex)
noodle logs --since 2026-07-05T00:00:00Z --until 2026-07-05T12:00:00Z
noodle logs --follow                    # poll for new records

Logs tell you what your app said while handling requests. For what happened to the requests (volume, errors, latency, per-tool health), use noodle metrics and noodle events — see Analytics & observability.

Deploy issues

  • noodle login first; hosted commands need an authenticated session.
  • A missing secret or variable referenced by your server fails the deploy closed. Set it with noodle secrets set / noodle variables set at the right --scope.
  • Use noodle inspect and noodle smoke to check a hosted deployment without exposing secret material.

See the CLI reference for every command and its flags.

On this page