Radial app

Limits & troubleshooting

Here's what Radial deliberately doesn't do yet, and quick fixes for the common setup snags. Stuck on something else? Email support@radial.to.

Troubleshooting

"Node is missing"

Radial needs Node 18 or newer on your machine. Install it with Homebrew, nvm, Volta, or from nodejs.org, then reopen the project. Radial resolves your login shell's PATH, so however you installed Node, it's found, even when Radial is launched from Finder.

"Install Claude Code or Codex to use terminal agents"

Radial launches the agent CLIs you already have. Install Claude Code, Codex, or Cursor and sign in (for Claude Code, run claude once in any terminal, or set an ANTHROPIC_API_KEY environment variable). Settings → Agent shows what's detected and offers the install or sign-in step directly.

A private repo won't clone

Radial uses your machine's existing git auth. If git clone works for that repo in your own terminal, it works in Radial; if it doesn't, set up your git credentials (SSH key or credential helper) first.

Known limits in v1

Page discovery maps routes from source for static HTML, Next.js (app and pages routers), Astro, and TanStack Start (the generated route tree when it exists, else the src/routes conventions: index files, - excluded files, _ pathless layouts, flat dotted names, $param skipped). SvelteKit +page files, Remix flat routes and plain src/routes or pages folders are mapped by convention. When the list is empty the Pages panel names the framework it saw, and radial pages --json carries a reason (unsupported-router, no-source-files). Routes that only exist at runtime are still reachable in the preview and through radial fields and the edit verbs, which work by route rather than by file.